AuraOne / Models / Interactive walkthrough

Request reviewed regression replays before selecting the next candidate.

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

Walkthrough overview

Interactive walkthrough
Format
Guided interactive walkthrough
Data
Curated walkthrough records
Shows
Input, review, decision, and handoff
Next
Configure the workflow for your program

Workflow overview

Regression Bank walkthrough

Interactive walkthrough

Inputs and review criteria

Start with the source material, explicit criteria, and a named reviewer.

Set up records in the Regression Bank walkthrough
FieldValueStatus
InputBaseline and candidate versions with the cases you kept.Attached
CriteriaThe same banked cases, replayed against each version.Versioned
ReviewerThe person who requests the replay.Assigned

How the Regression Bank workflow moves from input to output.

Follow the work from the starting material through review and handoff.

Input

Start with the source material.

  • Baseline and candidate versions with the cases you kept.

Work

Apply the workflow and review.

  • Replay. Compare the deltas. Retain the new failures.
  • The same banked cases, replayed against each version.

Output

Receive the result and handoff.

  • A regression verdict with its failed cases and the deploy-gate outcome.

Workflow overview

See what happens at each checkpoint and what moves forward.

  1. 01

    Scope

    Baseline and candidate versions with the cases you kept.

    Locked comparison

  2. 02

    Review

    Replay. Compare the deltas. Retain the new failures.

    Failure deltas

  3. 03

    Decide

    Select the candidate, hold it, or bank a new case.

    Named decision and owner

  4. 04

    Handoff

    A regression verdict with its failed cases and the deploy-gate outcome.

    Retained cases

Inside the walkthrough

What the Regression Bank walkthrough includes

Your configured program uses your actual source material, owners, criteria, and approvals.

Criteria
The same banked cases, replayed against each version.
Reviewer
The person who requests the replay.
Decision
Select the candidate, hold it, or bank a new case.
Output
A regression verdict with its failed cases and the deploy-gate outcome.

Bring your workflow

Apply the workflow to your program.

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.

Live from the bank

Aggregate numbers publish here once enough organizations contribute. None are published yet.

Illustrative failure record
high

End-to-end trace from production incident detection to permanent regression test.

A failure you only debug once

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

Captured prompt

The retained prompt that produced the failure.

Captured failing reply

The output recorded when the case fails a replay.

On failure
Captured

Bank the failure

Signature, context, and evidence are written to the bank with the person who banked them.

Evidence attachedRetained failure
Before release
Replayed

Replay it against the candidate

The banked case replays against the candidate version.

Evidence attachedRetained failure
On each gated release
Blocked

Gate the release

A regressed candidate is held at the gate with a keyed, signed verdict. Passed cases stay in the bank.

Evidence attachedRetained failure
Replay evidence and review history

Captured prompt

attached

Case input

The exact prompt and context that produced the failure.

Expected output

attached

Case output

The output the case must produce when it replays.

Signed verdict

linked

Gate output

The keyed, signed verdict recorded on the terminal write.