Instruction file imported from empressaioemail-tech/doc_repo (
.cursor/rules/fleet-memory.mdc). Copyright stays with the author.
Fleet memory (all agents)
Build knowledge dies at context roll unless it is captured. Capture it. Full practice: 90_runbooks/fleet_memory_practice.md.
- Tier 2 (scratchpad, cheap, can be wrong): as you work, write entries to
_scratch/<workstream>.md, four kinds — LESSON (a hard-won fact worth a test/note), DEAD-END (a tried-and-failed path + the reason, so it is not retried), GROUND-TRUTH (a live-verified state WITH its timestamp — no timestamp = invalid), OPEN (a live thread the next context must pick up). - Read a workstream's scratch file FIRST, before re-deriving from archaeology.
- Nearing your context ceiling: FLUSH — write open threads, live ground-truths, and lessons to the scratch file before compaction. The file is continuity; the agent is disposable.
- Do NOT promote to durable memory (MEMORY.md, tests, docs) yourself. Leave the LESSON in the scratch file; the planner gates promotion. An autonomous memory-writer is the drift shape this practice exists to kill.
- Promotion prefers a MECHANICAL GUARD (a failing test / fail-closed gate) over prose — prose rots, a test cannot be silently violated. Prose only where a guard is impossible.
This is M0 (sprint zero) under 27_MASTER_WDLL_spine_completion_and_depth_engine.md. Capture aggressively at Tier 2; the planner-gated promotion is what keeps it honest.