PATTERN · RELEASE GOVERNANCE
RUN IT
Release review moves from a late scramble to a repeatable gate. When an edge case slips, the team captures it, reviews it, and turns it into release evidence.
PROGRAMS YOU CAN RUN · BY FIELD
Stories you can run.
Real programs, anonymized by field — post-training and evals, model risk under examination, clinical second reads, robotics, manufacturing release, compliance. Each shows the work that came in, the record it left behind, and the gate it set for the next release. Bring yours and run the same loop.
FIELDS
9 programs
Post-training, evals, model risk, clinical second reads, robotics, compliance. Jump to your own.
PROVENANCE
Who. Reviewed. Rights.
Every record carries who made it, who reviewed it, and under what rights — ready for the EU AI Act clock.
OWNERSHIP
You keep the weights
A neutral second source you can defend under audit. AuraOne is the layer you run, not the lock-in.
PROGRAM PATTERNS · BY FIELD
The pain, then the turn.
Each card names the field and the moment the work began: a score that does not survive examination; detection that is not release; evaluation that started from zero every release. Then the turn — the work came in, the reviewer signed it, the failure became a gate.
PATTERN · POST-TRAINING
RUN IT
Failures became tests. Tests became gates. The gates stayed in place, and the next release inherited the proof.
PATTERN · CLINICAL OPS
RUN IT
Second reads stopped getting dropped on the wrong reader. The case, the rubric, the override chain — all one record. Review is part of the work now.
PATTERN · MODEL RISK
RUN IT
We stopped debating what happened. The evidence is attached to the run, the reviewer, and the approval — and we can hand the examiner one record.
PATTERN · HUMANOID PROGRAM
RUN IT
Demonstration capture, teleop review, and export lineage stayed inside the same workflow that ships the policy. The dataset and the decision arrive together.
PATTERN · EVAL PROGRAM
RUN IT
Suites and rubrics stopped drifting between releases. Comparable across weeks, comparable across teams, and comparable to ourselves.
PATTERN · COMPLIANCE
RUN IT
Controls, approvals, and exports stay attached to the same record. When the auditor asks, the answer is already in the packet.
PATTERN · WORKFORCE
RUN IT
Routing stopped being a Slack thread. Uncertain inferences reach the reviewer qualified for that case, with the context attached and no follow-up needed.
PATTERN · MANUFACTURING RELEASE
RUN IT
Detection is not release. A flagged defect now opens a hold and a sign-off, the escape goes into the gate, and the next run catches it before us.
Attribution · role + fieldRecord · who made it, who reviewed it, under what rightsNames · open on the private reference path
BRING THE WORK
Bring the work. Keep the proof. Own the model.
Run your own program in your own field, and the same loop applies. A private reference path opens when evaluation moves to procurement — ask for one when the fit is clear.