Project State Transfer — the Complete Snapshot
The flagship at full power: every decision, constraint, risk, assumption, and pending item of a complex project, transferred forensically as the new session's first message.
Overview
Some handoffs cannot afford triage: a complex rebuild with intertwined decisions, dual constraints, two open questions, named risks, and load-bearing assumptions — drop any one and the next session damages something. This is PROJECT STATE TRANSFER at full power: Forensic fidelity on a checkout-rebuild checkpoint, where everything detected travels, assumptions are first-class, the next step derives from the pending list, and the instructions enforce the complete contract — accept, preserve, question-don't-override, track, continue, and quote this package rather than reconstruct from memory.
Workflow
-
Checkpoint everything
Forensic mode drops nothing — the full detected state becomes the canonical snapshot.
-
Make assumptions explicit
The idempotency window, the mobile-release dependency — given conditions travel as ASSUMPTIONS.
-
Enforce the full contract
Quote-don't-reconstruct plus question-don't-override — the strictest continuation rules in the tool.
Why This Works
- Complete snapshots eliminate the triage that loses the critical item
- Explicit assumptions surface the dependencies silent handoffs break
- The forensic contract makes the package the source of truth, not a suggestion
Best for
- High-stakes rebuilds and migrations
- Projects with interlocking decisions and constraints
- The checkpoint that other sessions will treat as truth
Not for
- Quick session boundaries — Compact exists for those; forensic completeness costs reading time
- Material transfer — the spec, the code, the docs travel via the Splitter or Input Formatter
Use cases
- Checkpointing complex multi-workstream projects
- Transfers where any dropped item damages something
- Establishing the canonical state a team's sessions share