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

The Final Playbook

~27 min · playbook, rules, summary

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

The rules that survive the quest

  • Context is a budget, not a warehouse.
  • Capacity is not uniform quality; attention drifts.
  • Do not drive to the wall; keep safety margin.
  • Compaction is useful but lossy; checkpoint first.
  • The human collaborator owns meaning, priority, and authority.
  • Use the library strategy: index, load, work, evict.
  • Cache stable prefixes; put volatility in the tail.
  • Audit the model with evidence; allow it to admit gaps.
  • Recover from rot by capture, reset, reload — not more reminders.
  • Current source beats stale notes.

The working mantra

The right amount of the right context, in the right order, with the right human steering, beats the biggest possible blob. That is the whole spell. Annoyingly simple. Difficult enough to be worth a quest.

The winner is not the largest context. The winner is the cleanest operating loop.

Code

Context operator loop·yaml
context_operator_loop:
  1_index_sources:           "know what exists"
  2_load_active_working_set: "only what this turn needs"
  3_reserve_safety_margin:   "output, reasoning, buffer first"
  4_place_authority_at_edges: "front spine, tail current state"
  5_work_and_log:            "telemetry per turn"
  6_checkpoint_before_drift: "preempt, do not react"
  7_human_confirms_live_truth: "steering > reminding"
  8_commit_or_handoff:       "explicit paths, durable handoff"
Personal rule card·markdown
# My Context Operator Card
- Budget, not warehouse.
- Edges hold authority.
- Stable prefix, variable tail.
- Checkpoint before 75%.
- Steering, not reminding.
- One next action at a time.
- Source beats notes.

External links

Exercise

Turn the final playbook into a personal rule card for your own AI work. Keep it under 12 lines. Place it where the next AI session will read it.

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.