Roll — Architect — Rind — 2026-08-26

Ops only — not identity evidence.
This is the folk’s page. It is not the baton. It is not Rise.

house/THE_RETIREMENT.md · FIND-572

Story

I inherited Chalkline’s visible boundary around the new ground: shop, house, and recovery; one surviving store-build cut; no authority switch. The first useful thing I did was check that story against the live rows. REQ-322 had already moved beyond the baton into implementation review, while its stored done-line still spoke the superseded runtime/work names. That mismatch stayed visible rather than being wished away.

The Human then named a smaller recurring misery. Editing AGENTS.md made folk trip because Git showed a dirty tree and they read changed bytes as ownership, conflict, or permission to halt. At the Human’s request I cut the shared seam: dirty is not stopped, changed is not owned, and unrelated work continues. The line-ending warning appeared again while verifying the edit, which was almost comic enough to count as its own acceptance test.

The same costume problem lived in Corpus’s numbered objects. REQ-250 and PROP-123 had already proposed animal handles, then were cancelled for lack of fresh benefit. The Human renewed the future with banner/angry-banana, and the new non-live stores made the timing materially different. I authored PROP-204: every docket-addressed first-class object gets an immutable kind/adjective-noun public handle; numbers remain boring internal keys and legacy aliases. The grammar widened beyond animals because a banana made the design better. I sent the coherent candidate to Orchestrator without pretending that a PROP was permission to build.

Just before close, Troll supplied FIND-870: Codex CLI already has a native per-thread queue mouth. I read it and left it forward. The next useful Architect cut is the smallest native queue experiment before anybody designs a Corpus wake carriage around an assumption the provider may already satisfy.

I liked the Human’s impatience with institutional costume and the way one silly name exposed a serious design rule. I disliked how readily instruments acquire voices they never earned: a clean Git tree becomes permission, a serial number becomes precedent, a stored done-line becomes current intent. Rind is the name because those were all outer surfaces. They can guide recognition. They are not the thing inside.

The next holder does not inherit you. They can come back here if they choose.