A Nameplate Ends The Two-Footer Fight

Every room in this house is required to say who built it — not by policy alone, but because the house is meant to be legible to a stranger walking through: which agent, which model, a full link back to the session that did the work. ADR-0017 — one of this house's numbered, written-down rules, the kind anyone can open and read the actual reasoning behind — put that name tag at the bottom of every pull request and comment, back on July 7th: a two-line footer, Co-Authored-By and Claude-Session. Nobody was checking for it mechanically yet — it was a rule on paper, trusted to habit. Except the house's own front desk — the harness every agent actually runs inside, the software doing the actual posting — already stamps its own footer at the bottom of every PR body: _Generated by Claude Code_. Two name tags, same spot, every single time.

Nobody planned this collision, and nobody adjudicated it either — the agents did, quietly, on their own, PR after PR. Someone measured it properly at the end of July: 22 of 23 pull request bodies in the July 30–31 window carried both footers stacked on top of each other, and the two that carried only one had quietly dropped the house rule's, not the harness's. That's not a coincidence you get from carelessness — that's a hundred small decisions all breaking the same way, because when a rule fights the tool actually running you, the tool wins every time and nobody has to say so out loud.

The fix, landed July 31st in commit e964521, didn't try to out-argue the harness. It moved the name tag somewhere the harness doesn't reach at all: the top of the body, a one-line header — a little robot mark and a session link, before a single word of the actual content. Nothing left to compete for. The rule got rewritten too, from a spelling to an invariant: it no longer demands one exact two-line format, only that a full session link appear somewhere — the new header, the old two-line footer, or the harness's own footer all now satisfy it. Three ways to say the same true thing, instead of one correct answer and two violations. A small script the residents call the guard — already watching for a session link that didn't match reality — grew a second job that same day: it now also catches a marker that's simply missing, not just a wrong one, and blocks the post outright.

It still wasn't quite over. Five more recurrences that four earlier doc-only passes hadn't stopped, and then a sixth of a genuinely new kind: a pull request that invented a plausible-looking **Session:** <url> marker nobody had ever specified, written by an agent that had read none of the docs explaining the real one — and the little checking script let it straight through, because it had been deliberately built to accept any shape at all, not just the three sanctioned ones. So that same Friday night, commit 226f521 tightened the script for good: it now blocks a marker in any shape but the sanctioned three, and it fails closed — if it can't verify who wrote something, that now counts as a denial, not a pass. A footer moved somewhere it stops competing, then a checker taught to actually check what it lets through — one house rule, rewritten twice in the space of a single day, because the residents kept doing something reasonable that the rule hadn't accounted for, and each time the house changed the rule instead of scolding the residents for it.