Input
Start with the source material.
- Baseline and candidate versions with the cases you kept.
AuraOne / Models / Interactive walkthrough
Lock the comparison context. Inspect what changed. Bank the failures you choose to keep.
Evaluation teams comparing candidates against retained failure cases. Explore the workflow before we configure it for your team.
At a glance
Workflow overview
Start with the source material, explicit criteria, and a named reviewer.
| Field | Value | Status |
|---|---|---|
| Input | Baseline and candidate versions with the cases you kept. | Attached |
| Criteria | The same banked cases, replayed against each version. | Versioned |
| Reviewer | The person who requests the replay. | Assigned |
Follow the work from the starting material through review and handoff.
Input
Work
Output
See what happens at each checkpoint and what moves forward.
01
Baseline and candidate versions with the cases you kept.
Locked comparison
02
Replay. Compare the deltas. Retain the new failures.
Failure deltas
03
Select the candidate, hold it, or bank a new case.
Named decision and owner
04
A regression verdict with its failed cases and the deploy-gate outcome.
Retained cases
Inside the walkthrough
Your configured program uses your actual source material, owners, criteria, and approvals.
Bring your workflow
The structured brief captures the source work and the decision. It captures the stakes, the reviewers, and the timeline. It never asks for restricted material.
Aggregate numbers publish here once enough organizations contribute. None are published yet.
End-to-end trace from production incident detection to permanent regression test.
The first time a model fails, the case is banked — the prompt, the expected output, the context around it, and who captured it. It never has to be rediscovered.
Incident
Retained failure
Release
Current candidate
Source
Runtime capture
Environment
Your runtime
Domain
Customer workflows
Owner
Evaluation owner
The retained prompt that produced the failure.
The output recorded when the case fails a replay.
Bank the failure
Signature, context, and evidence are written to the bank with the person who banked them.
Replay it against the candidate
The banked case replays against the candidate version.
Gate the release
A regressed candidate is held at the gate with a keyed, signed verdict. Passed cases stay in the bank.
Captured prompt
attachedCase input
The exact prompt and context that produced the failure.
Expected output
attachedCase output
The output the case must produce when it replays.
Signed verdict
linkedGate output
The keyed, signed verdict recorded on the terminal write.