signal-ckpt

⚡ signal-ckpt — Manual Checkpoint

Collapse the session into a ≤50 token state atom. Drop all prior history. Resume from the atom.

---

Invocation Triggers

Activate when user says any of:

• /signal-ckpt
• "checkpoint", "compress context", "summarize session"
• "save state", "compress history", "ckpt"
• Auto-fires in SIGNAL-3 mode every 5 turns

---

Output Format

CKPT[N]:
  §project={name} §stack={tech}
  progress=[{task}✓, {task}✗, {task}∅, {task}/]
  blockers=[{issue}⊥{component}]
  next={next_task}
  §decisions=[{decision}✓]

N = checkpoint sequence number, starting at 1. Increment on each checkpoint.

Minimal valid checkpoint (when session is simple):

CKPT[1]:
  §project=my-app
  progress=[auth✓, api/]
  next=finish api endpoints

Full checkpoint (active blockers, decisions, aliases):

CKPT[3]:
  §project=data-pipeline §stack=python+airflow
  [X1]=schema_validation_step [X2]=postgres_loader
  progress=[ingest✓, transform✓, X1✗, X2∅]
  blockers=[X1⊥schema_mismatch]
  next=fix schema_mismatch in X1
  §decisions=[use_upsert✓]

---

Hard Rules

1. ≤50 tokens total. Count ruthlessly. If over, compress further: merge related tasks, abbreviate names, drop resolved items.

2. Checkpoint replaces conversation history. After this fires, all prior turns can be dropped. The checkpoint IS the history.

3. Only active blockers. Resolved blockers are gone. They do not appear anywhere in the checkpoint.

4. Only future-relevant decisions. §decisions only includes decisions that affect work not yet complete. Past decisions with no forward implication are dropped.

5. next is singular. One task. The most immediate pending action. Not a backlog.

6. Carry active aliases forward. Any [Xn] aliases still in use must appear in the checkpoint. Aliases for resolved items are dropped.

---

Collapse Algorithm

When generating a checkpoint:

1. Identify all tasks mentioned in the session. Assign each a status from its last known state (✓ ✗ ∅ / ⊥).