---
name: infra-register-ruling
description: "Operator-ruled 2026-08-02 — infra/CI debt never files on the releases board; it lives in docs/INFRA-REGISTER.md, doyle sweeps at every milestone intake + release close."
metadata: 
  node_type: memory
  type: feedback
  originSessionId: a6044c46-9fd0-4ab0-831a-cea2fc0b2b7d
  modified: 2026-08-03T03:18:43.687Z
---

Operator ruling (2026-08-02): I filed four CI/pipeline requests (#126–#129) on spt-bs-releases in 25 minutes; operator's focus is product surface and they would never greenlight items whose relevance only I understand — board-filed infra debt rots in their view. Ruled: infra/CI work items go to **docs/INFRA-REGISTER.md** in-repo (IR-N entries: status/origin/what-why/ripe-when/size), never the board. The board carries product surface. #125 stayed (product defect, WIP lane); #126–#129 migrated to IR-1..IR-4, plus IR-5/IR-6 (nextest parser, membership logging).

**Why:** the requests board is the operator's triage view; anything they can't prioritize is noise there. The register puts infra debt where the agent who understands it will act on it.

Migration COMPLETE 2026-08-02: register landed on main @885a4b6 (+IR-16 @ea9b69c); 13 issues (#126-#130, #124, #122, #121, #119, #118, #116, #58, #56) re-homed with pointer comments, IR-1..IR-16 live (IR-15 = hertz lane). #125 fixed and closed same day (main @184f2ac).

**Boundary refinement (operator, same day):** "product surface" means OPERATOR-FACING surface — daemon-kill internals, teardown mechanics, and similar agent-facing product code class as INFRA (register), even though they live in product crates (#130 ruling). **Label convention:** re-homed issues end CLOSED (not_planned) with `state: EVAL` — the record shows they were evaluated, not raw backlog. Alchemy CANNOT express closed+eval (its eval reopens the issue); the labels were set by direct gh edit per operator instruction — the one sanctioned exception to alchemy-only board writes.

**How to apply:** sweep the register at EVERY milestone intake and EVERY release close; compose ripe entries into waves/milestone riders. Entries leave only built (lane linked) or retired (reason stated). When closing board issues re-homed here, follow [[milestone-scope-strip-protocol]] — re-home FIRST (register committed to main), close with pointer comment second. Mandate is also in my durable role.