repo-task-proof-loop

An auditable repo-local proof loop is automated by initializing durable task artifacts that route through a strict freeze, build, evidence, verify, and fix sequence. This ensures every acceptance criterion passes with concrete evidence.

A frozen spec workflow locks requirements before implementation begins, routing them through fresh verification until acceptance criteria pass. You need it for refactors or migrations requiring auditable progress and explicit non-goals across multiple files.

To set up resumable coding progress, initialize a durable task state inside the .agent/tasks directory. This routes work through scoped subagents and stores workflow outputs locally so progress remains auditable across sessions.

Yes, you need git and python3 installed in your environment to run the repo-local proof loop. These dependencies initialize the durable task artifacts and execute the bounded subagent scripts required for fresh verification.

Fresh verification works by repeatedly testing built code against frozen specs within the loop, using Codex subagents for scoped implementation. If verification fails, a fixer role resolves issues until all acceptance criteria pass.

The best way to maintain a verifiable PASS/FAIL trail is enforcing a strict route, freeze, build, evidence, and verify sequence. This confines workflow outputs to a local task directory and captures concrete evidence for every acceptance criterion.