Contracts
Step 2 of the T3 executor’s 5-step chain: audit → contract → packet → implement → verify. Each contract states the behavioral guarantee the task will uphold — invariants, I/O shape, non-goals — before any code is written. See CLAUDE.md §6.
Organization
Files are named <task-slug>-contract.md. Every Phase 0 task
(p0-*) plus every R75/R76/R77 round task has a contract artefact
in this folder. Browse the sidebar or search by task slug.
See also
- Executor Contract — the T3 contract that governs the 5-step chain.
- 5-time/task.md — task-level lifecycle.
- Audits — Step 1.
- Packets — Step 3.
- Verifications — Step 5.