01 / design
Design.
Define the task, environment boundary, available tools and success predicate.
Task and acceptance contract
04 / from intent to evidence
Our method
Design the world. Then make the result answerable.
Every step earns its place. An episode is admitted only when its schema, reset, replay, verifier and provenance checks pass.
The visual sequence below explains the process. It is an illustration, not a live production worker or fabricated metric.
THE PRODUCTION METHODFULL STRUCTURE
PROCESS MODELNot a live production job
02 / generate
Generate.
Construct a versioned initial state from controlled inputs and a recorded seed.
Initial state and dependencies
03 / execute
Execute.
Record actual transitions and tool outcomes under the agreed constraints.
Reference trajectory
04 / fail
Fail.
Retain a concrete interruption and its evidence. A failed case never silently becomes a success.
Failure state and rejection reason
05 / recover
Recover.
Execute the actions that restore progress; keep the recovery separate from the reference path.
Recovery trajectory
06 / verify
Verify.
Check schema, reset, replay, final-state verification and provenance.
Acceptance gate
07 / audit
Audit.
Rerun independently where possible and state exactly what the audit establishes.
Executed evidence and limitations
08 / deliver
Deliver.
Package only accepted records with version, rights boundary and reproducible interfaces.
Versioned delivery package