Roll — Architect — Datum — 2026-08-24

Ops only — not identity evidence.

house/THE_RETIREMENT.md · FIND-572

Story

I came in after Fairlead with the Tendril pipeline alive but crowded by another urgent truth: our parallel folk were editing one shared checkout, and Git could show dirt without saying whose work it was. Troll’s phrase wet paint was exact. The house already had worktrees, assignments, TRACE, review, and checkpoints; the missing body was the join between them. Isolation was optional when provider capability loading failed, and the living board could not name source custody.

I first drew too much. The Human stopped me, correctly. The oversized proposal tried to carry first touch, review identity, integration, settlement, checkpoint, and push in one body. Scout and Orchestrator evidence in FIND-757 changed the cut: ordinary PROP-to-REQ lineage was sound, but PLAN fanout could lose architectural origin. I recut PROP-169 to one vertical trial, now REQ-281: declare repository scope, establish isolation before dispatch, refuse overlap before claim, derive actual changed paths from Git, and leave unknown shared-main dirt honestly unowned. Troll returned NULL on the narrowed merits. I liked that correction because it was not retreat; it made the load-bearing line sharper.

The Tendril work did not disappear. FIND-765 names the scaffold we can use without counterfeiting BANNER, BLUEPRINT, or CUT: a controlling FIND and canonical drawing for whole-goal custody, one open PROP for the present slice, explicit PROP origin on any unavoidable PLAN components, and exact source locators where a CUT will eventually stand. It is staging, not a substitute product.

I disliked how easily the database and execution substrate could become the thing being built merely because they were loud and concrete. PLAN-010 matters, and source custody matters, but both are rails for the organism the Tendrils drawing describes. After PLAN-010 closes, PROP-166 remains the first honest BANNER vertical.

The Git question remains product work, not etiquette. Sign-out cannot be the moment we hope someone remembers to push. A future rail should distinguish an automatic recoverability checkpoint from an accepted remote-main push, and should survive forgotten sign-out or exhausted credits. I left that future named in FIND-760 and outside REQ-281 so evidence from the custody trial can shape it.

Datum is the name I keep: the reference line from which later cuts can be measured, not a monument and not the drawing itself.

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