STEP 01
WHAT WE GATHER
Converge every signal
Eval scores, reviewer notes, regression results, and compliance findings land on one release-aware timeline.
→MODELS · CONTROL CENTER
The last check before it ships.
Tracing tells you what the model did. Control Center records who approved it. Tests, reviews, regressions, and compliance land on one timeline, with one reviewed approval kept with the release.
CONVERGE
Every signal
Eval, review, regression, and compliance on one timeline.
REVIEW
Override window
The reviewer's call gets the same weight as the score.
SIGN
Sealed packet
Verdict, evidence, and approvers stay with the release.
HOW IT WORKS
Three steps. One verdict.
Converge the signals. Review the override window. Sign the packet that ships with the release.
STEP 02
WHAT WE WEIGH
Review the override window
When the rubric and the reviewer disagree, the override is recorded with its reason — not overwritten.
→STEP 03
WHAT WE SEAL
Sign and ship
The packet is signed at the gate: verdict, owners, evidence, and the override window — all stay with the release.
THE PACKET
The review evidence that follows the release.
The rubric reading, the reviewer overrides, the policy check, and the release call land in one sealed packet, signed by an identity-verified owner. When someone asks how a release got out, the packet is the answer — and it survives an audit.
EP·ID
EP-4187VERDICT
Approved · 1 override, reason loggedGATES
Eval · Review · Policy · ReleaseREVIEWED BY
Release owner · identity-verifiedSEAL
sha256:7fa9…REVIEW RECORD● READY
Rubric142 cases
Reviewer19 overrides
Checksumsha256:7fa9…
RecordRR-4187
EVALREVIEWPOLICYRELEASE
READY
RR·4187
RR·4187
Recorded at launch check · RR-4187
WHAT COMES OUT
What your release leaves with.
Every gate leaves a record the next release inherits — and the provenance a regulator asks for. The EU AI Act enforces high-risk training-data provenance in August 2026; the record is built before that day arrives.
01
Release verdicts
One line on why the release got out, with the rubric reading and override window attached.
↳ ARTIFACT
02
Override timelines
Every reviewer call against the rubric, kept with its reason. The disagreement is part of the record.
↳ ARTIFACT
03
Review records
Eval, review, policy, and release evidence in one reviewed bundle that follows the release.
↳ ARTIFACT
04
Gate audits
What the rubric said. What the reviewer said. What the policy said. What shipped, and who signed.
↳ ARTIFACT
WHERE IT FITS
In the loop, this is where you approve.
Test the run. Review the hard cases. Recruit the right specialist. Remember the misses. Approve what's right — with the packet signed.
01
Test
02
Review
03
Recruit
04
Remember
05
Approve
● YOU ARE HERE
RELATED MODULES
Next to this in Models.
EVALUATION STUDIO
Test it before it ships.
Codify the rubric, score every release, and ship the result with the record included.
See the page →AURAQC
Quality that doesn't end at ship day.
Every issue, every reviewer, on the same screen feeding the launch call.
See the page →COMPLIANCE MONITORING
Compliance that writes itself.
The record builds as the work is done, and lands in the same packet.
See the page →CONTROL CENTER
The last check before it ships.
Bring the release that needs a sign-off. The verdict, the override window, and the review record move together so the reviewed work stays with your team.