How it works
How an EU AI Act release gate works
Register the AI system, classify risk, run promotion, eval, and contract checks, then take PASS, REVIEW, or BLOCKED with a sealed evidence pack.
From registration to release decision
- 1
Register the system
Add the AI system with owner, purpose, deployment context, and data sources. This is the register the rest of the gate reads from.
- 2
Classify risk & attach evidence
Record prohibited, high, limited, or minimal risk and why. Attach DPIAs, model cards, vendor docs, and the human-oversight record high-risk systems need.
- 3
Run Evgraph, evals, and contracts
Evgraph checks promotion timestamps and dataset licenses. Eval scores and open data-contract breaches feed the same decision. Missing files do not pass.
- 4
Get a release decision
Take PASS, REVIEW, or BLOCKED with the controls behind it. Export a sealed evidence pack (JSON + PDF hash) that includes the Evgraph artifacts.
What PASS, REVIEW, and BLOCKED mean
One decision per system, with the controls behind it. Not a traffic light on a slide.
PASS
Evidence, evals, contracts, and promotion checks all clear the configured bar. The sealed pack can be exported.
REVIEW
Something is incomplete or under the review threshold. Owner, compliance, or legal still have to act.
BLOCKED
A hard stop: open contract breach, prohibited class, missing high-risk oversight, or a promotion file that does not pass.
What the sealed pack includes
JSON plus a hashed PDF you can hand to an auditor. It is a work product, not a legal Annex IV filing.
- Release decision and the controls behind it
- Cited evidence snapshot and eval run
- Contract status and open drift
- Approvals and human-oversight records
- Evgraph promotion and dataset artifacts
- Annex IV-shaped checklist — not a legal instrument
Ready to see your release gate?
Request a demo for one named AI system. We follow up with a written quote. This is not a legal certificate.