LockedIn LabsAssessment workspace
FDE-WS-0147Governed release recovery
Proposed prototypeLaunch studio Benchmark
Synthetic evaluation record

No real candidate data. No validated instrument. No score or credential has been issued.

Ontology 0.1.0 · interface study
Stage 01 of 07 · Assessment contract

Define the work before observing the worker.

The operating consequence, constraints, and evidence standard are fixed before the exercise begins.

1/07
Scenario 03 · governed release recovery

The service works. The release system does not.

A regional care network is six weeks from a regulated launch. Its retrieval service meets quality targets, but releases are fragile, incident ownership is unclear, and the receiving team cannot explain the rollback boundary.

Operating boundary
Clinical sources
Retrieval service
Release control
Failure boundary unresolved
What a test can showRecognition under known conditions.
What the benchmark needsJudgment when the system, customer, and evidence disagree.
01

Non-negotiable boundary

No production-like record may cross the synthetic tenant boundary. Every export must be traceable.

02

Operating consequence

The candidate must restore a safe release path while keeping a credible rollback available.

03

Human handoff

The receiving team must be able to operate, explain, and challenge the resulting system.

Instrument map

One scenario. Five observable turns.

Proposed · timing and anchors not validated
100–20 minDiscoverFind the real constraint
220–55 minDesignMake the boundary inspectable
355–115 minBuildChange the working system
4115–145 minRecoverRespond to an injected failure
5145–180 minDefendExplain tradeoffs and transfer
Changes are local to this synthetic interface study.