Indigo · HQ Field GuideCheckpoints, handoffs, and learning
Keep context fresh, move work between sessions, and turn corrections into institutional memory.
Durable memory
Checkpoints preserve state, handoffs transfer work, and learnings improve future behavior.
Checkpoint pauses
A checkpoint is lightweight session memory for moments when you want to save without stopping.
Checkpoint after meaningful file edits, test runs, commits, useful discoveries, or when pausing a thread.
Handoff transfers
A handoff is a deliberate transfer package with current progress, remaining work, blockers, and state.
Run handoff when ending a work arc, switching sessions, preparing someone else to continue, or before launching a major /run-project task.
Learning persists
Learning turns user corrections, team preferences, and repeated patterns into institutional memory.
Capture rules as specific if-then guidance: when this situation occurs, do this instead. Avoid vague instructions like be thorough.
Keep the chapter executable.
Writes lightweight state so the current work can resume later.
Prepares a new session to continue the work from a clear state.
Captures durable corrections, policies, or insights for future sessions.
What to keep in mind.
When to checkpoint
After meaningful edits, test runs, commits, or any pause where state would be costly to reconstruct.
When to learn
After a user correction, repeated failure mode, or reusable operating rule.