05-delta · 2–6 h · 5 min
Re-audit: what moved after the fixes.
You already have a journal and a QA. You patched. The question is no longer “are there holes”: it is “which are still open”. Delta compares to the snapshot. It does not open a second folder to fake a new audit.
- When to open it
- A pass 2, 3 or 4 already produced a journal
- After a wave of fixes, or “what moved?”
- Same project, same folder
- Agents
- 00, 01, delta-reaudit specialist, 10, 11
- Outside this mode
- No prior finding means this is not a delta
- Any class absent from the baseline stays out of scope
The move
Before any new collection: dated snapshot. Then targeted collection on the same classes. Re-check open findings. Rescore. QA on the delta. delta-compare deliverable.
Launch phrase
Delta on the already-open project. Snapshot first. Re-read open findings.
Before you launch
- First audit?
- Then it is not a Delta. Express, Full Web, Full SaaS or MCP, depending on the product.
The kit, not the guide.
Open source, MIT. Clone it, open it in Claude, Codex, Cursor or Hermes. A held report — or QA’s silence.