Flatpack: step 13 of 15

Build verification

Write a spec for each piece of work and turn it into scenarios. Keep some scenarios where the author cannot see them, and stand up twins of outside services. Each run proves its own change, then a separate verifier scores it against the scenarios over several trials, because the same ticket can give a different change on each run.

Brings together

• Spec
• Scenario
• Holdout scenario
• Digital twin
• Self-verification
• Satisfaction
• Non-determinism

Makes

Verification

‹ Step 12: Make the codebase agent-ready · Step 14: Merge by risk ›

An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal