orchestrator-routelisted

# /orchestrator-route `ORCHESTRATOR.md` is a **router**: current state plus pointers. It is not a store and not a log. When it is over cap it is because durable facts landed in it instead of in the file that owns them. The fix is routing, not pruning. **When Sean invokes this by name, that is the trigger — run it**, even under the size/staleness threshold. The "NOT for merely untidy" language in the description governs unprompted, autonomous firing only. Everything below is a boundary. The procedure is obvious and you already know it; these are the six things that get it wrong. ## ⛔ Gate 1 — Never evict by recency **This is the one that destroys files.** The instinct is "keep the N newest." That rule inverts value: a trap from two months ago is still true, and a status line from yesterday expires next week. Measured in seansmithdesign.com's 112K file: ~94 lines carry permanently-true traps, ~13 were dead the moment they were written. Deleting every worthless line moves 112,472 → ~103,000. **Deletion is not the lever.** Age is not the signal. Sort by lifespan, never by date: | Would a fresh thread do something wrong without this line? | Destination | |---|---| | No — and it can't even be evaluated now (`PID 86955`, "MCP was down this session") | **delete outright** | | No — it is what happened | `ORCHESTRATOR-log.md` | | Yes — permanently true about the project | the owning memory file (Gate 2) | | Yes — and it is about right now | stays in `ORCHESTRATOR.md` | ## ⛔ Ga