Operator documentation
Review a completed coding mission
Inspect changes, tests and execution evidence before accepting a returned Operator artifact.
Compare with the brief
Read the requested scope next to the result. Identify extra files, omitted behavior and assumptions that changed during execution. A detailed report can still describe an incomplete outcome.
Use behavioral evidence
Look for tests that exercise the requested behavior and relevant failure cases. Then reproduce a small acceptance flow in the intended environment. Keep tests, packaging and live behavior as separate evidence.
- Inspect the diff.
- Review required checks and failures.
- Replay the requested behavior.
Keep a usable handoff
Retain the mission brief, artifacts and SHA-256 receipt together. Record unresolved limitations so the next person does not mistake a partial result for a deployed repair.
Continue
Reviewed September 17, 2026. Current product terms and availability are listed on the product site.