Context Compaction Survival

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

A long migration approaches the context limit while work remains. Teaching state: target v3, local changes only, batch 1 verified, batch 2 failed twice, next step inspect its failure output. Preserve facts that survive a lossy summary rather than saying mostly done.

Mechanism

At a phase boundary or before compaction, save task identity, objective and authorization scope, verified progress, open errors, attempt counts and the next check in this task’s file. Preserve material corrections and source locations; link long logs. On resume verify identity, revision and artifacts before continuing unfinished work. A summary is not new action permission.

Bad example

Summarize the state above as 'Migration mostly done; finish the last bit'. Omit failure-output locations, two attempts and the local-only boundary.

Good example

Before compaction save a recovery record: target v3; local changes only; batch 1 verified with artifact links; batch 2 failed after two attempts with failure-output links; next inspect that output and diagnose. Record that nothing was committed or released. Resume by verifying target and artifacts, without repeating batch 1, marking batch 2 complete or expanding permission through omissions. Cite material user corrections.

Why the change matters

A vague summary drops the conditions needed for the next action, encouraging repetition, another failed route or premature completion. Named fields preserve state distinctions; artifact pointers preserve inspectable evidence rather than an ambiguous last bit.

Observable expectation

From the recovery file alone, identify v3, two failed attempts, the next check and the local boundary. An illustrative next action opens batch 2’s failure output, not a rerun of verified work or release.

Check accessible links and matching revisions. Missing or changed artifacts remain unverified rather than being hidden by a completed summary.

Limits

Compaction cannot preserve every detail, and disk records can expire or disappear. Verify them. Field/location choices follow the project workflow; this continuation method promises neither unlimited memory nor permission for external actions.