Models / Model Launch Check

Know what passed before you release.

Compare the same checks, review blockers and record the evidence for a ship, hold or rollback decision.

Release recordLaunch review
CandidateCandidate model
DestinationProduction
DecisionHold
  1. EvaluationSame rubric and source slice
  2. Regression replayOne failed case needs review
  3. Approval chainSafety signer remains
  4. RollbackOwner and procedure attached
Release gate2 requirements remainClose the failed-case review and collect the required signer.

Input, work, and output

Input

What you provide

  • Named model candidates and versions
  • Locked rubric, thresholds, and measurement version
  • Release policy, approvers, and rollback owner

Work

What happens

  • Run the same evaluation and operating checks
  • Compare deltas and failed examples
  • Request regression replays and expose verified blockers before approval

Output

What you receive

  • Ship, hold, or rollback decision
  • Required checks and completed approvals
  • Release record, rollback path, and retained regressions

Decision flow

The steps from intake to handoff, in order.

  1. 01

    Candidate input

    Confirm candidate versions, owners, and the intended release.

    Candidate manifest

  2. 02

    Same-check comparison

    Lock the rubric and source slice before scores or rank are displayed.

    Comparison matrix and source runs

  3. 03

    Regression replay

    Replay retained failures and keep each failed case visible.

    Regression outcomes and affected versions

  4. 04

    Blockers

    Name every requirement that failed or is missing.

    Blocker owner and recovery

  5. 05

    Approval

    Show who can approve, who has approved, and what remains.

    Approval chain and timestamps

  6. 06

    Release record

    Record the decision, its evidence, and the rollback plan.

    Release decision record

What you receive

Know what passed before you release. deliverables

Scope
One candidate set, one rubric, one release decisionScoped engagement; pricing follows the accepted work
Candidate
Model and version identityProvider, owner, and intended destination
Checks
Evaluation, regression, and safety stateVersioned source runs and evidence
Blockers
Any requirement that failed or is missingNamed owner, consequence, and recovery
Approval
Required signers and completed decisionsRequired role, approver, decision, and time
Release
Decision, evidence, and rollback pathRelease decision record

What the workflow supports

What the workflow supports.
OutcomeWorkWhat you receiveProgram fit
ShipEvery required check passes. Every required signer has approved. A rollback path is in place.Source-linked results, approvals, and a verified regression replay.The release record covers the approved candidate, its checks, and the rollback path.
HoldA required check fails, a signer has not approved, or evidence is missing.The blocking criterion, its owner, and the next action.The hold names what must be fixed. The candidate goes back through the same checks once it is.
Roll backThe decision brief recommends rollback, or a deployed release must be reverted.The recommendation, its evidence, and the rollback deployment record.A rollback recommendation cannot be overridden at the gate. The rollback runs as its own recorded deployment.

Inspectable evidence

Candidate comparison exposes the decision, not a leaderboard.

Release review with descriptive states, named owners, and next actions.

Interactive walkthrough Illustrative

Compare two candidates under one locked launch check.

Select candidates and a launch criterion to see where each release is ready, needs review, or remains blocked.

Same checks
Select a criterion to inspect its source and decision effect.
Required checkCandidate ACandidate B
Review requiredEvidence ready
Blocking issueEvidence ready
Review requiredReview required
Evidence readyEvidence ready

Criterion inspector

Known regressions

Required evidence
Replay of retained failures under the same candidate
Source
Regression Bank replay record
Decision effect
A blocking retained failure holds the candidate.
1 blocking itemCandidate A: Known regressions
Launch review summaryCandidates, checks, sources, blockers, approvals, and rollback
  1. 1

    Same checksCandidates share the same rubric and measurement version.

  2. 2

    Blocking evidenceA failed regression remains visible and source-linked.

  3. 3

    Release effectEvery difference states how it changes the decision.

For teams that buy evaluation data

Your release. Your call.

We supply the evidence: a locked evaluation plan, the cases your model has failed before, and matched comparisons of the candidates you bring. You decide to ship, hold or roll back. We don't train, deploy or control your model.

  1. 01Source rights

    Which use the source allows.

  2. 02Task

    One task, one ID.

  3. 03Eval set

    A named, versioned set.

  4. 04Baseline

    The recorded first attempt.

  5. 05Comparison

    The candidates you bring, on the same checks.

  6. 06Verdict

    What regressed, what held.

  7. 07Your approval

    Ship, hold or roll back.

Training examples are kept out of held-out tests. Sealed tasks are never used to train. Where a scoped release process exists, this record is what Model Launch Check packages.