Repository navigation
Closes a growth defect seen downstream: the framework tells the Archivist to update pipeline_status.md at every close, but no rule ever rolled anything off — so the entrance card, read on the hottest paths (boot, every statusline render, SessionStart, the PreToolUse gates), grows without bound. A production adopter's card had reached ~96,000 characters (~43k tokens) of mission history duplicated verbatim from its CHANGELOG lane; applying this contract cut it −94% with zero information loss.
What's new
📇 Entrance-card retention contract (ADR 103) — the Retention Policy in GOVERNANCE.md now manages pipeline_status.md itself. The card holds current state only: bounded cells behind a leading legal [STATE] token, at most 3 one-line pointers under ## 📜 Recent Missions, and a ## 🧭 Navigation routing table naming a home for every information class the card no longer carries. Budget: ≤ 12,000 chars hard, > 10,000 warn (counted after CRLF normalization). Mission history lives where it always belonged — the CHANGELOG lane the Archivist already writes.
✂️ Verify-then-trim (Archivist Hard Rule 8) — deletion gets a sanctioned, provable moment. At every mission close the Archivist first verifies the CHANGELOG already holds the closing mission's narrative (append-first refusal: trim only history the CHANGELOG lane already carries), then writes the new current-state cells, demotes the prior mission to one pointer line, and drops pointers beyond 3.
🛡 A validator with teeth — new scripts/check-entrance-card.mjs: 8 hard rules on the shared entrance-card parser (single parsing truth — the validator can never disagree with the hooks), wired as pre-commit gate 3 with an 18-test suite on the zero-dep node:test runner. Alongside it: a > 10k warn lane in the pipeline-status narrative check and a SessionStart over-budget banner, so drift is announced at boot long before the hard gate bites. The new gate validated its own landing commit.
🔧 Statusline fix at the source — the template card's Active Persona cell is now the bare persona name (the emoji is presentation, applied by the statusline). The decorated idiom had silently rendered the status chip "⚙️ Unknown" since it shipped.
Stays out of your way
The starter template already conforms — a fresh project sees no new burden, and the Day-0 welcome block stays. Existing adopters: run npm run check:entrance-card. If your card is over budget, follow the verify-then-trim procedure in lfe-archivist/SKILL.md — append any mission narrative your CHANGELOG lane is missing first, then trim; the pre-trim card stays one git show away.
Under the hood
- Test suite: 1179 passing / 0 failing (+29 for the validator and the two hook lanes).
- Budgets ship as framework defaults with the GOVERNANCE "project tunability" override idiom — projects re-bound them in their own
LLM_AGENT_GUIDE.md. - Recorded as ADR 103 in
.docs/architecture/framework-decisions.md— the contract was proven on a downstream production repo first, then ported here generic.