01 / design
Design.
Define the task, environment boundary, available tools and success predicate.
Task and acceptance contract
04 / from intent to evidence
Verification methodology
An episode is admitted only when its schema, reset, replay, verifier and provenance checks pass. A failed gate remains a failed gate.
The sequence below explains the production method. Executed production evidence and the illustrative process model are identified separately.
01 / design
Define the task, environment boundary, available tools and success predicate.
Task and acceptance contract
02 / generate
Construct a versioned initial state from controlled inputs and a recorded seed.
Initial state and dependencies
03 / execute
Record actual transitions and tool outcomes under the agreed constraints.
Reference trajectory
04 / fail
Retain a concrete interruption and its evidence. A failed case never silently becomes a success.
Failure state and rejection reason
05 / recover
Execute the actions that restore progress; keep the recovery separate from the reference path.
Recovery trajectory
06 / verify
Check schema, reset, replay, final-state verification and provenance.
Acceptance gate
07 / deliver
Package only accepted records with version, rights boundary and reproducible interfaces.
Versioned delivery package
Agree the task, action interface and success predicate.
Version controlled inputs and initial states.
Record actions, transitions, failure and recovery.
Apply schema, reset, replay, verifier and provenance gates.
Release accepted records with their evidence and rights boundary.
Failure and recovery belong inside execution. An outcome is admitted only when the required checks pass.