C.W.K.
Stream
Lesson 03 of 05 · published

Recovering from Context Rot

~25 min · recovery, fresh-session, rot

Level 0Window Watcher
0 XP0/50 lessons0/13 achievements
0/100 XP to next level100 XP to go0% complete

Sometimes the session is polluted

If the model keeps violating the same rule after correction, the session may be losing the attention battle. More reminders can make the window larger without improving behavior. The recovery pattern is capture, reset, reload, continue.

Capture before reset

Before clearing or restarting, write the live truth into a durable note: live rules with source, current state, and any failed-attempts that explain a real gotcha. The reset deletes session memory; the captured note becomes the seed for the new session.

Do not preserve poison out of sentiment

Old failed attempts are useful if they explain the bug. They are poison if they merely repeat the wrong instruction. Keep evidence, not noise. The temptation to 'preserve everything in case it helps' is exactly what makes the next session also rot.

When a session is polluted, more prompting can be the problem, not the cure.

Code

Context-rot recovery plan·yaml
recovery_plan:
  capture:
    - live rules with source
    - current state
    - failed attempts that explain a real gotcha (NOT random noise)
  reset:
    - fresh session OR explicit compaction with audit
  reload:
    - durable note
    - current source files
    - latest test result / git status
  continue:
    - exactly one next safe action
Capture skeleton·markdown
# Recovery capture @ <timestamp>
Live rules:  ...
Current state: ...
Forbidden:   ...
Gotchas worth keeping:
  - <attempt that failed for a real reason, with source>
Discard:
  - earlier reminders that no longer help
Next: <one specific action>

External links

Exercise

Describe a re-prompting spiral and write the recovery plan that should replace it. Practice the capture step: what survives, what gets discarded, what is the one next action?
Hint
Look for repeated agreement followed by repeated violation. That is the spiral signature.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.