Packets
Step 3 of the T3 executor’s 5-step chain: audit → contract → packet → implement → verify. Each packet is the execution plan — files to change, commit sequence, gate commands — that gates Step 4 (implementation). A packet must be approved before any code lands. See CLAUDE.md §6.
Organization
Files are named <task-slug>-packet.md. Every Phase 0 task (p0-*)
plus every R75/R76/R77 round task has a packet 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.
- Contracts — Step 2.
- Verifications — Step 5.