{
  "source_sha": "e5a2fed9badcac399e2fb825a1fc035cee981a39",
  "release_sha": "16df0e41be04ca4614a792f7e70e4d1bdec60b24",
  "date": "2026-09-11",
  "population": [
    1,
    2,
    3,
    4,
    5,
    6,
    7,
    8,
    9,
    10,
    11,
    12,
    13,
    14,
    15,
    16,
    17,
    18,
    19,
    20,
    21,
    22,
    23,
    24,
    25,
    26,
    27,
    28,
    29,
    30,
    31,
    32,
    33,
    34,
    35,
    36,
    37,
    38,
    39,
    40,
    41,
    42,
    43,
    44,
    45,
    46,
    47,
    48,
    49,
    50,
    51,
    52,
    53,
    54,
    55,
    56,
    57,
    58,
    59,
    60,
    61,
    62,
    63,
    64,
    65,
    66,
    67,
    68,
    69,
    70,
    71,
    72,
    73,
    74,
    75,
    76,
    77,
    78,
    79,
    80,
    81,
    82,
    83,
    84,
    85,
    86,
    87,
    88,
    89,
    90,
    91,
    92,
    93,
    94,
    95,
    96,
    97
  ],
  "early": {
    "summary": "Exhaustive read-only sweep: 50 assigned entries (IR-1–49 plus IR-54), including headingless IR-31. Strong stale-status findings: IR-1/4 landed and exercised; IR-26 build-side identity is present but claim-side remedy remains missing; IR-29 first face landed but later faces remain; IR-33 sized-stack implementation exists; IR-46 ruled floor tokens are implemented but acceptance receipts remain distinct. No tests, measurements, edits, or board mutations performed.",
    "files": [
      {
        "path": "docs/INFRA-REGISTER.md:180-2725",
        "description": "All assigned bodies read; 49 numbered entries plus IR-54, with IR-31 beginning at the second Status paragraph inside IR-30."
      },
      {
        "path": ".github/workflows/golden.yml",
        "description": "Verified current link probes, toolchain print, START/END/DOCS disk assertions, and traceable-reqs pin still 0.2.0."
      },
      {
        "path": "crates/xtask/src/main.rs",
        "description": "Verified load-bearing patch check, unguarded help-output generation, current pool-claim tree-match guard and unconditional incumbent overwrite."
      },
      {
        "path": "crates/spt-poolguard/src/lib.rs:367-443",
        "description": "Verified anchored lane identity and ancestry-only settled predicate; no patch-id fallback."
      },
      {
        "path": "crates/spt/src/main.rs:72-205",
        "description": "Verified CLI runs on 16 MiB owned thread stack; existing cli_stack_smoke integration evidence source identified."
      },
      {
        "path": "crates/spt-store/src/info.rs:872-876",
        "description": "IR-44 preservation-overclaim remains verbatim."
      },
      {
        "path": ".github/ci/ci-notify.sh:129-130,182-200",
        "description": "IR-40 bare CI verdict wording and IR-47 quiet absent-coauthor branch remain."
      }
    ],
    "architecture": "The register mixes original status headers, later corrections, and independent residual mechanisms. Treat implementation, exercised acceptance, historical specimens, and current release receipts as separate evidence objects. Pool enforcement executes in the arriving tree; claim writes remain a separate path. Disk tokens are instantaneous observations, not sustained headroom.",
    "report": "## Scope and decision vocabulary\nExactly 50 rows: IR-1 through IR-49, plus IR-54. IR-50 begins at line 2726 and is excluded. IR-31 is the headingless second Status paragraph after IR-30's Linux-face resolution, through line 2068. Trigger means the entry's stated ripeness event, including a historically documented firing; UNKNOWN never means disproved. CLOSE for already-built/retired entries means preserve their established disposition, not a new claim based on v0.69.0 green. Source reads below were not executions.\n\n| IR | Current entry status | Trigger | Recommended disposition and evidence |\n|---|---|---|---|\n| 1 | Open / lane unlanded | FIRED | CLOSE stale header: reconciliation at 2878–2906 explicitly identifies landed commits; register 169–171 records first golden exercise; current golden.yml 1096/1264 invokes both link probes. Original 4–7 ms negative is not a universal network acquittal. |\n| 2 | RETIRED; incremental remains ON | UNKNOWN for reopen threshold | CARRY retired decision, flag returned disk pressure. New 14.3 vs 32 GiB red weakens historical ample-disk rationale but does not by itself establish the required recurring floor-red threshold or causal ON/OFF timing. No automatic flip or new causal claim. |\n| 3 | Open | UNKNOWN | CARRY: release facts do not demonstrate endpoint-churn wakeup instrumentation or the specific lifecycle trigger. No retirement from battery/build success. |\n| 4 | Open / lane unlanded | FIRED | CLOSE stale header: same landed reconciliation as IR-1; xtask main.rs 47–49 executes patch-pin check; 1047+ implementation; GOLDEN-CI 99–109 carries targeted update/block+edge/toolchain procedure; golden 276/304 prints toolchain. Register first-exercise receipt covers golden steps. |\n| 5 | Open / conditional | UNKNOWN now; NOT FIRED on original rider | COMPOSE next count-consuming rig task. Foot reconciliation 2920–2928 explicitly says original condition NOT MET, contradicting header's unreported condition. 121/3167 counts are receipts, not proof a summary parser was needed or built. |\n| 6 | Open / conditional | FIRED historically; latest extent UNKNOWN | COMPOSE gate-output work; original rider condition NOT MET, with only its new LINK rows voluntarily compliant. Current count receipts do not prove estate-wide membership enumeration. |\n| 7 | Open / hertz fixup linked | FIRED (queued lane) | CARRY linked daemon-leak lane; hertz offline/unacknowledged brief is not a landing. No source/acceptance proof of in-job launch replacement in supplied release facts. |\n| 8 | BUILT | FIRED / satisfied | CLOSE unchanged: established two-platform unreadable-path UNPROVEN verdict and Linux kill-failure evidence stand. |\n| 9 | Pin landed / BUILT | FIRED / satisfied | CLOSE unchanged: 35968156 pin plus documented runner-account/version-print and tested-cut evidence stand. |\n| 10 | Open | FIRED historically | COMPOSE runbook/checklist follow-through. Runbook work demonstrably occurred (IR-54/28); no verified consumer-population checklist fulfilment here. |\n| 11 | Open | UNKNOWN for implementation wave | COMPOSE next rig-tooling rider; cleanup is a use of holder discipline, not evidence --headless became a column. |\n| 12 | BUILT narrowed blind arm; kin note retired | FIRED / satisfied | CLOSE: preserve existing missing-assets fix plus 2026-09-06 stale-binary mutation result. Original rig cause remains unproven; prebuild rule survives independently. |\n| 13 | BUILT | FIRED / satisfied | CLOSE unchanged on documented mutation-specific fulfilment, not latest green. |\n| 14 | Open; 08-30 audit/rule completed | FIRED (operator cleanup) | CARRY structural residue, annotate new cleanup. 38 clean merged trees removed without removing dirty/unmerged/retained evidence; separate checkout/orphan hygiene from target-byte reclaim. Old count tables are dated specimens, not current inventory. |\n| 15 | BUILT | FIRED / satisfied | CLOSE unchanged: authenticated death oracle and both repins documented. Original specimen remains cause-unidentified; green rerun did not identify it. |\n| 16 | BUILT | FIRED / satisfied | CLOSE unchanged on checked returns/named loss/loud refusal fulfilment; keep already-exited Windows exception and dropped rename reasoning. |\n| 17 | Open; Windows population remains | FIRED historically; new matching sighting UNKNOWN | CARRY linked hardening/instrumented family. Known sync-cell red and unavailable earlier PR logs are not identified resident-service/grandchild sightings. Preserve Linux member's separately named closure and remaining Windows uncertainty. |\n| 18 | BUILT; deferred (b) work embedded | FIRED / satisfied for named lane | CLOSE existing authenticated-teardown disposition only; do not silently erase deferred shared breadcrumb-read/cleanliness-consolidation work. Record explicitly whether parent retains/re-homes those residuals; original specimen's killer remains unidentified. |\n| 19 | RETIRED intentional main-push policy | FIRED / satisfied | CLOSE unchanged. Full main-push unit execution is expected; 3167-pass receipt does not revive classifier defect. |\n| 20 | Open / hertz fixup linked | FIRED (hardening lane queued) | CARRY: stop stderr discrimination and load-bearing perch-pid caution remain; scoped greens do not prove explicit stop did anything. |\n| 21 | BUILT | FIRED / satisfied | CLOSE unchanged: explicit cross-package prebuilds, binedge check and shared missing-fixture precondition documented. Keep same-package/cross-package distinction. |\n| 22 | Open | FIRED historically (hygiene wave) | COMPOSE diagnostic-set remedy with test hygiene; no all-markers diagnostic proof supplied. Generic env scrubbing does not satisfy the diagnostic half. |\n| 23 | BUILT | FIRED / satisfied | CLOSE unchanged: TempDir staging plus declared parallel bare-cargo exercise recorded. |\n| 24 | BUILT | FIRED / satisfied | CLOSE unchanged on named TerminateJobObject loss and ordinary-exited TerminateProcess discrimination. Historical wrong path already corrected in status. |\n| 25 | Open | FIRED historically (CI/rig waves) | CARRY fragility; compose rig rule/hardening. Sanctioned nextest avoids in-process interference but does not retire marginal tests. Do not attribute latest unknown PR red to this family. |\n| 26 | Open / built but uncommitted (stale) | FIRED; cleanup shrank old-reader population | CARRY with status replacement. Body already says committed 8ce40d9/98cfafe; current poolguard has anchored git identity and precedence. However xtask 3134 writes owner directly after constructing claim: no incumbent lane adjudication or displaced record. Latest 38-tree removal mitigates old enforcers, not current claim-path loss. |\n| 27 | Open | FIRED (cleanup/audit slot) | CARRY post-teardown trigger gap. Existing pool-sweep detection was already shipped; new reclaim does not prove automatic post-removal sweep or link+pool lifecycle coupling. Distinguish real target dirs from junction pairs; no blanket claim latest cleanup exercised both shapes. |\n| 28 | BUILT | FIRED / satisfied | CLOSE unchanged: mechanical commit-range/changelog accounting required by PR #176. Latest release success alone is not the evidence. |\n| 29 | Open / first fix authored-unlanded (stale) | FIRED (many twohost windows) | CARRY residual faces with corrected status. IR-30 explicitly records 17bbbd8 landed v0.54.0. Later terminal-cadence seal face and emitted-token requirement must not disappear under first-face closure. Six-draw margin series remains closed/unrecoverable. |\n| 30 | Open for family sightings only | UNKNOWN whether latest red matches family | CARRY. Instruments already landed; classify known sync red only from its own frame. Earlier PR red lacks logs and remains unclassified. 121 battery / 3167 units / release build cannot close intermittent family. |\n| 31 | Open; headingless | FIRED (disk-floor recurrence/rig work) | COMPOSE aggregate lane-disk accounting with existing floor work; CARRY structural capacity debt. Root target 62.32 GiB + CI debug 59.70 GiB reclamation addresses bytes; later net 4.22 GiB cleanup is separate. No observation proves aggregate-aware admission/reservation or finished-lane disposal automation. |\n| 32 | Open | FIRED (docs/xtask wave) | COMPOSE generator refusal; source confirms still open: help_for 100–108 ignores child exit and accepts empty stdout; cli_reference inserts it; gen_one writes unconditionally. Stack mitigation does not repair producer self-agreement. |\n| 33 | Open; old 3-arg ceiling | FIRED historically | CARRY only acceptance/status reconciliation, not stale remedy proposal: main.rs 72–205 implements 16 MiB CLI thread; cli_stack_smoke.rs has real binary help/version/nonzero-return contracts. Source presence establishes changed mechanism, not current named debug execution receipt or measured new margin. Mark implementation present; require existing lane/acceptance receipt before declaring full closure. |\n| 34 | Open / hertz fixup linked | FIRED (nextest-config waves) | CARRY linked fixture/config disposition. A single non-leaky run carries no closure information; no delivered lane proof. |\n| 35 | Open rate home | FIRED historically; remeasure-after-landing UNKNOWN | CARRY. Need operator rate ruling plus landed package and correctly deduped new rate. 3167 unit passes is one population, not replacement for historical execution series; no new ratio derived. |\n| 36 | BUILT | FIRED / satisfied | CLOSE unchanged on existing owning/tree-killing helper and diagnostic/death proof. Preserve documented clone-count distinction rather than recounting. |\n| 37 | Upstream released; consume outstanding | FIRED (upstream release) | COMPOSE consume lane, do not close: current golden.yml 1413 pins WANT=0.2.0, not required 0.4.0. Upstream release is not downstream adoption; placement config/acceptance still owed. |\n| 38 | BUILT | FIRED / satisfied | CLOSE existing test-leak fix; cleanup corroborates importance of independent CWD-holder population, not a new all-holders closure. |\n| 39 | BUILT | FIRED / satisfied | CLOSE unchanged on shared missing-fixture refusal and package-correct recipe evidence. |\n| 40 | Open, resume recency + notify scope | FIRED for workflow window; arm-A implementation UNKNOWN | CARRY / COMPOSE scope-wording rider. ci-notify.sh 130 still prints bare CI $verdict. Latest 3167 passes followed by 14.3 GiB floor red is decisive receipt-scope example: workload success != job/run success. SHIP at known-red a9e786b2 is authorization, not green; release build success is another object. Brief delivered to offline hertz != acknowledged/accepted. |\n| 41 | Open; documentation corrected | FIRED (CI/runbook work) | CARRY policy decision; docs acceptance already complete, concurrency-key change is not required without ruling. No supplied evidence latest missing PR logs resulted from queued supersession; do not manufacture that explanation. |\n| 42 | BUILT documentation correction | FIRED / satisfied historically | CLOSE existing incumbent-enforcement clarification but flag wording drift: current pool_claim can refuse wrong-tree/unreadable-tree claims (main.rs 3075–3110). 'Never refuses' is now too broad; it still does not adjudicate incumbent lane ownership, so preserve that precise distinction. |\n| 43 | Open observation; mechanism unmeasured | UNKNOWN | CARRY transport-bound question. Latest sync red not identified as NoReply 60/30-second specimen; no attribution by timing overlap. |\n| 44 | Open | UNKNOWN for specific info.rs touch | COMPOSE next info.rs touch; exact false-preservation sentence still at 873–875. Serialization is not preservation; no proof remedy landed. |\n| 45 | RETIRED | FIRED / satisfied | CLOSE unchanged: temp-root path chain answered disk hermeticity only; third-node runtime ingress is not exonerated by it. |\n| 46 | Open; ruled/composed WEBSERVE rider | FIRED | CARRY acceptance reconciliation, mark source implementation present. golden START/END/DOCS raw-byte tokens exist; END always() before teardown, sample=INSTANT, 32 GiB unchanged. Latest unit-pass then disk-floor-red is honest workload-versus-resource separation, not product failure. Need per-job actual START/END and relevant golden/DOCS receipts before full ruled-remedy close; neither cleanup nor release-build green substitutes. |\n| 47 | Open; patch stashed | FIRED (golden/workflow rider window) | COMPOSE notification warning: ci-notify.sh 197–200 still merges absent/unparseable and doyle-only into quiet info. Source is enough to reject closure; no need to recover stash just to carry. |\n| 48 | Open preventive control | UNKNOWN for exact parity-cell touch | CARRY / COMPOSE next parity change. main.rs 3012 uses checked-in config; inspected parity test region supplies no LF/CRLF fixture-pair control. Current CRLF tolerance is not its own regression proof. |\n| 49 | Open ancestry-only takeover defect | FIRED (shared cleanup audit slot); takeover request UNKNOWN | CARRY; current git_lane_state 424–438 remains ancestry-only, no patch-id fallback. Removing clean merged worktrees/pools may remove affected claims/readers but does not fix future cherry-picked member takeover. Manual cleanup classification is not guard semantics. |\n| 54 | BUILT | FIRED / satisfied | CLOSE unchanged on PR #176's intake/never-executed-cells/lock-property changes. Release counter105/tag16df0e41 and known-red candidate remain explicit distinct receipts; do not flatten into tested==released green. |\n\n## Load-bearing deltas for parent edits\n1. Correct stale state, not merely append another contradictory note: IR-1/4 unlanded headers contradicted by their own landed reconciliation and first-exercise record; IR-5/6 original conditional answer is explicitly NO, not unknown. IR-26 is no longer uncommitted, IR-29's original fix no longer unlanded, IR-33's old stack mechanism has shipped source, and IR-46's ruled source exists.\n2. Operator cleanup: IR-14/26/27/49 should receive one consistently scoped event, not four closures. Removing 38 clean merged worktrees shrinks the stale-arriving-enforcer population and reconciles checkout residue. It does not establish a durable teardown trigger, incumbent guard at claim time, patch-id settled predicate, or future pool safety. No dirty/unmerged/retained evidence was removed. 62.32 GiB root target and 59.70 GiB CI debug reclamation are cache-byte mitigations; net 4.22 GiB later cleanup is a distinct event/meter. Do not add unlike values into a claimed single net-free reading.\n3. IR-40/46: preserve receipt types. 121 scoped battery pass; push-CI Windows 3167 unit pass followed by 14.3/32 GiB resource red; earlier PR unit-red logs unavailable/unclassified; golden known sync cell red under explicit SHIP; release build succeeded; v0.69.0 counter105 published at16df0e41. None logically substitutes for another. Cleanup does not establish cause of the earlier PR red, and passing workload before end-floor RED is not proof disk caused that workload or the prior red.\n4. IR-37 has a concrete unfulfilled downstream obligation: current golden installer still requests traceable-reqs 0.2.0. Upstream closed-through-release wording must not become spt-core closed.\n5. IR-32 remains a source-demonstrable hole despite stack and recursive-doc improvements. IR-42's old universal 'claim never refuses' sentence is now false because a different, tree-match refusal was added; incumbent ownership enforcement is still absent. Keep these distinctions visible.\n6. No new family membership, rate, cause, or acceptance execution was inferred from source presence, temporal overlap, unavailable logs, or green receipts. Existing built/retired verdicts above stand on their recorded evidence; no validation suite was run."
  },
  "late": {
    "summary": "Read all 47 assigned entries (IR-50–97 excluding earlier IR-54), including every long amendment. Strongest corrections: IR-66 is eligible for closure; IR-73's eight reorders and docs-floor rereads are already implemented; IR-69/83/89 carry stale lifecycle wording. Keep the disk, quiet-window, slowdown, and diagnostic debts open. No edits or runtime checks performed.",
    "files": [
      {
        "path": "docs/INFRA-REGISTER.md:2726-5781",
        "description": "Complete assigned population and historical evidence; 47 entries, physical order includes IR-53 before IR-52."
      },
      {
        "path": ".github/workflows/ci.yml",
        "description": "All five IR-73 sites now follow checkout (IR-73 comments at 28, 98, 113, 184, 232); Windows start floor remains 32 GiB."
      },
      {
        "path": ".github/workflows/release.yml",
        "description": "All three IR-73 sites now follow checkout (comments at 54, 69, 169)."
      },
      {
        "path": ".github/workflows/golden.yml",
        "description": "Docs-floor rereads at 599/622; Windows start still 32 GiB at 229; docs steps retain implicit preceding-success coupling."
      },
      {
        "path": "crates/spt-daemon/tests/attach.rs",
        "description": "IR-66 remedies present: delayed TICK39 on Unix/Windows at 531/539, delayed ALT_VIEWPORT_MARKER at 656."
      },
      {
        "path": "WEBSERVE-272-JIT.md:111-119",
        "description": "IR-66 explicitly ruled satisfied; workflow floor rider and driver adoption tracked separately."
      },
      {
        "path": ".github/ci/reap-census.ps1",
        "description": "Family-only process predicate remains at 70–73/123; does not implement IR-76's compiler-load predicate."
      },
      {
        "path": "docs/GOLDEN-CI.md:26-51",
        "description": "Existing quiet-window contract includes CI occupancy, local build processes, and parent-chain attribution; reuse instead of introducing another definition."
      },
      {
        "path": "crates/spt-store/src/proc.rs:46-49,430-433",
        "description": "kill_pid and kill_pid_tree still accept bare numeric PIDs; IR-81 primitive-level remedy not present."
      },
      {
        "path": "crates/spt-daemon/src/daemon.rs:475-476",
        "description": "Pidfile still overwritten directly; IR-82 predecessor preservation not implemented."
      },
      {
        "path": "crates/xtask/src/brainread.rs:194-203,295-320",
        "description": "IR-94 name-shape predicate and three-file enumeration remain."
      },
      {
        "path": "crates/xtask/src/main.rs:69-70",
        "description": "pick-audit and disk-floor verbs exist, contradicting stale future-build wording in IR-57/59."
      }
    ],
    "architecture": "Separate structural enforcement, procedural adoption, box mitigations, and incident diagnosis. Workflow floor placement is distinct from capacity sizing; process custody is distinct from performance attribution; publication ordering is distinct from inject coverage. Release SHIP authority and passing batteries do not discharge unresolved mechanism claims.",
    "report": "## Scope and reading key\n47 assigned entries: IR-50–97, excluding IR-54 (starts earlier). IR-49's preceding body and the CI-RIDER historical section were seen but not assigned as new IR entries. IR-31 is outside this range and remains the earlier-range owner's embedded-entry responsibility.\n\nTrigger = an entry's remedy/intake trigger, not proof its failure recurred. FIRED may be historically established; UNKNOWN means the supplied release facts and inspected material do not establish a qualifying new touch/event. Existing BUILT/CLOSED states stand without gratuitous re-verification. Actions are recommendations for the parent's ruling, not board mutations.\n\n## Exhaustive disposition table\n| IR | Current entry state | Trigger | Recommendation and evidence |\n|---|---|---|---|\n| 50 | CLOSED / BUILT, landed v0.59.0 | FIRED historically | CARRY closed. Census/adoption completion and explicit engine-room exclusion already evidenced; release facts supply no reopening. |\n| 51 | OPEN | UNKNOWN for #199 causal attribution; historical hermeticity pass available | CARRY. Ephemeral advisory ports do not disable peer pump/discovery or establish network causality. Preserve sequencing prohibition against net-off-as-green. |\n| 52 | BUILT | FIRED historically, generator touch SIGNET | CARRY built. Full recursive command-tree rendering and previously omitted leaves recorded; do not reopen from old third-instance pre-build prose. |\n| 53 | BUILT / landed v0.59.0 | FIRED historically | CARRY built. Cold-boot arm explicitly names unproved property; three narrower clock-aging siblings remain touch-triggered, not newly diagnosed by release success. |\n| 55 | OPEN, ARMED-FOR-CAPTURE, hertz | FIRED (standing unfiltered-battery trigger) | CARRY armed, owner unavailable rather than executing. Nextest containment and prior 5×663 green settle sweep are not leak closure; no fresh wedge reported. Keep capture-before-kill protocol. |\n| 56 | BUILT | FIRED historically | CARRY built. Cross-worktree refusal and explicit foreign-pool takeover measured in entry; IR-42 admission boundary intentionally remains. |\n| 57 | OPEN, living gater procedure | FIRED (assembly/release arc) | CARRY procedure; correct stale proposed-tool wording: pick-audit already exists (xtask main:69) and caught real LOSS. Release build success proves compilation, not per-pick fidelity or repaired-file behavior. |\n| 58 | OPEN, unowned; original claim retracted | FIRED (brainread/xtask work this milestone) | COMPOSE cargo-enumerated duplicate-bin check at next tooling intake; no closure evidence. Never resurrect withdrawn nonexistent-bin/prose correction. |\n| 59 | OPEN, arithmetic/discipline | FIRED, including latest post-push disk-floor red | COMPOSE residual driver adoption/capacity work, carry discipline. Workflow start/end and docs-floor logging now exist; xtask disk-floor exists. Root target 62.32 GiB + CI debug 59.70 GiB and later 4.22 GiB cleanup are mitigations, not bounded accumulation. Do not call 14.3 GiB an explanation for unavailable earlier unit logs. |\n| 60 | OPEN, script discipline | FIRED (diagnostic/gate reporting) | COMPOSE into next shared driver touch, carry open. Preserve leg verdict separately from wrapper completion; 3167 unit pass then floor red must be reported as distinct outcomes, not flattened to all-green or all-unit-red. Missing exit also requires reading raw Summary (IR-79), not inventing completion. |\n| 61 | OPEN, accepted with mitigation | UNKNOWN substantive scanner touch | CARRY. No supplied fact establishes literal-tracker unification; unrelated xtask work alone is not this specific trigger. |\n| 62 | BUILT docs-collision remedy; residual caveat | FIRED historically | CARRY built scoped to docs listener. Other bind surfaces remain conditional residuals; do not imply whole network hermeticity. |\n| 63 | OPEN, mitigated, historical queued hertz lane | FIRED historically/rig work | COMPOSE with teardown/IR-79/97 adoption, keep open. Path-safe reaps are mitigation; no complete producer-side teardown proof. Update queued-owner language to pending acknowledgement, not active execution. Historical rotating victims do not classify the new sync/convoy red. |\n| 64 | OPEN, operator reservoir | FIRED historically by IR-86 in-job floor failure; latest disk red reinforces relevance | COMPOSE operator capacity/accept-tax decision, carry open. Current cleanup does not move operator-owned bulk or prove permanent headroom. Do not recite historical 845 GB as a freshly measured current census. |\n| 65 | REMEDIATED-AT-BOX, OPEN recheck record | UNKNOWN snap/auditd update or reimage | CARRY recheck record; no box commands needed this sweep. Release green is not evidence that effective audit configuration survived a named reset event. |\n| 66 | BUILT; explicitly due to leave at WEBSERVE close | FIRED, close overdue | CLOSE eligible now. JIT:111–116 already rules satisfied; current attach.rs:531/539/656 retains both delayed needles. Remove stale next-intake two-edit rider from sweep summary; this is source-backed closure, not green-alone retirement. |\n| 67 | BUILT, battery-template remedy | FIRED historically/intake | CARRY built. Scoped 121-pass battery is only its named scope; do not use --bins as integration coverage or promote it to full golden acceptance. |\n| 68 | OPEN investigation | UNKNOWN new PSYCHE_INGEST_FAIL/probe slot | CARRY. Existing nonempty-lock experiment refuted the proposed cause; unrelated release facts cannot reinstate index.lock attribution. |\n| 69 | OPEN; header says parked pre-assembly | FIRED historically close-out recensus | COMPOSE #243 residual plus separately tracked anchored-consumer rider; correct stale header. Body already records landed ec6da9b0 and 338 cli + 2 main residuals. Need residual conversion, generator fix, and SHA-pinned zero recensus before closure. Delivery.rs post-cut sites already converted; no new lane owed there. |\n| 70 | OPEN, recurrence remedy unscheduled | UNKNOWN construction/API/sink touch | CARRY. Shipped default_bus site correction is not enforced assembly-point closure. IR-92 funnel work may make this a useful next construction-seam rider, but do not assert its trigger from publication work alone. |\n| 71 | OPEN observability | UNKNOWN qualifying controller-lifecycle/breadcrumb touch | CARRY, eligible next lifecycle instrument rider. Existing info.json polling barrier proves convergence separately; no new persisted-release breadcrumb evidenced. |\n| 72 | OPEN observability | UNKNOWN qualifying read-model/holder-inspection touch | CARRY. Cleanup process-table custody is not a supported named-seat read verb. |\n| 73 | OPEN, title/body claim eight pre-checkout sites still owed | FIRED; implementation already present | CLOSE eligible for the entry's original two halves, with implementation evidence explicitly stated. All 5 ci and 3 release sites are after checkout with IR-73 comments; golden docs rereads exist and IR-86 records their live catch. Current header is stale. Capacity derivation and docs dependency coupling remain IR-86, not reasons to re-build IR-73. |\n| 74 | OPEN /tmp population | FIRED as between-milestone audit opportunity; current Linux touch unknown | COMPOSE bounded /tmp lifecycle at box-audit intake, not a fresh numeric census. Windows cleanup says nothing about kitsubito's 21,643 historical homes. |\n| 75 | OPEN Linux treqs 127 | UNKNOWN new Linux-driver touch; audit opportunity remains | COMPOSE install-or-explicit-platform-independent-coverage decision with Linux box audit. No proof here of current installation or driver removal; retain stale-state verification obligation, never infer it from overall green. |\n| 76 | OPEN quiet-window/measurement | FIRED driver/workflow/runbook arc | COMPOSE outstanding enforcement and compiler-load census. Existing GOLDEN-CI:26–51 already supplies a better occupancy/parent-chain contract; reap-census still selects only SPT family. IR-87 proves queue interference, not cause of sync expiry. Historical headline 'manufactured' is stronger than overlap alone; new sweep must not repeat it as a diagnosis. |\n| 77 | OPEN boot interval visibility | UNKNOWN exact boot/ready-stamp touch | CARRY, compose if next daemon-boot instrumentation lane opens. No timestamped child-entry→ready proof surfaced; full test duration is not boot interval. |\n| 78 | OPEN silent docs-port override | UNKNOWN new docshost touch; historical belief incident already witnessed | CARRY tiny next-docshost rider. No release fact proves notice implemented; precedence need not be redesigned. |\n| 79 | OPEN panic/timeout teardown exposure | UNKNOWN new common-module touch; exposure continues | COMPOSE first-wave guard adoption with IR-63/97; pending owner acknowledgement. Preserve panic-vs-hard-kill boundary: Rust Drop alone does not guarantee cleanup on process termination/SIGKILL. Entry's blanket timeout coverage claim needs qualification, not adoption as a guarantee. |\n| 80 | OPEN; initial product-candidate headline superseded by amendments | FIRED historical investigation opportunity | CARRY residual class, reconcile stale opening. Body identifies brainproc shell-wrapper fixture mechanism and direct production spawn; does not classify all 12 union members. LEAK-count reduction or passing Windows unit set cannot close this. No owner is executing by implication. |\n| 81 | OPEN primitive + gate; adapter arm CLOSED | FIRED historical proc/xtask work | COMPOSE remaining primitive and script-gate obligations. Current kill_pid(pid) and kill_pid_tree(root) remain bare-PID APIs (proc.rs:46/430); KH7.51 records a broker-site birth-safe correction but one site does not close primitive enforceability. Adapter closure stands, incident cause remains separate. |\n| 82 | RULED, remedy historically linked #285 | FIRED historical lifecycle/#285 lane opportunity | COMPOSE unbuilt predecessor record independently of #285's site repair. daemon.rs:476 still direct-writes pidfile; no predecessor retention at this path. Header 'main ends at IR-78' is historical/stale. Do not call linked lane completion IR-82 completion. |\n| 83 | OPEN, operator-rule blocked historical prose | FIRED; superseded box evidence in IR-89 | CARRY direction-witness enforcement residual, reconcile obsolete blocker/LAN-only prescription. IR-89 records actual tailnet ACL+firewall grants and successful tailnet probes, refuting a universal 'never tailnet' necessity. Need parent ruling to replace obsolete remediation with layer-specific admission + permanent reverse witness, not infer full closure from a one-box green. |\n| 84 | OPEN, first instrument half landed with filing | FIRED historically | CARRY unresolved stall arithmetic/enforcement residual; acknowledge clocked emitter half as built. Timestamp instrumentation does not explain the extra ~27–34 s, shorten behavior, or prove every future arm stamped. |\n| 85 | OPEN, caps mitigation only | FIRED arm 1; operator arms UNKNOWN | COMPOSE redesigned discriminator after guard/occupancy prerequisites, keep open. Old-sha slowdown establishes head growth not necessary, not environment apportionment. Alternate AB/BA, bank per-leg conditions/output; cap 80/40 remains mitigation. No Defender/torrent/disk causal allocation from concurrency or reclaim recovery. Hertz offline: brief delivered, unacknowledged. |\n| 86 | OPEN, capacity derivation + docs coupling | FIRED golden/workflow arc | COMPOSE workflow sizing/independent docs dependency rider. golden.yml still 32 GiB start (229), docs floor (626), and OS-only success-coupled conditions (600/617/623). Historical 67.4 GiB footprint motivates re-derivation, not universal guaranteed peak. Latest 14.3<32 post-unit red is additional capacity evidence, not a new product failure. |\n| 87 | OPEN independent job clocks | FIRED; exact recurrence banked at a9e786b2 | COMPOSE scheduling/rendezvous rider. Entry timeline proves B ended before A began, caused by golden head's own PR runner occupancy; include self-PR, not merely other lanes. Keep raw GitHub conclusions alongside VOID scoring. 900s panel alone cannot separate this from firewall. |\n| 88 | OPEN pool-release vehicle | FIRED historical teardown; runbook adoption due | COMPOSE permanent release-before-delete/prebuilt recipe; carry open until adoption documented. Positive control already proves cargo-run regrowth vs prebuilt non-regrowth; current cleanup alone doesn't show recipe institutionalized. Prefer existing proven sequence, not an in-verb refusal that can only run after cargo already rebuilt it. |\n| 89 | BOX applied; WORKFLOW built, landed-pending-golden | FIRED: multiple subsequent goldens | CARRY built pending exact step evidence; flag 'until next golden' stale immediately. No full probe-step outcomes were supplied/read here; next golden occurred but that alone is not exercise proof (steps can skip/partners desynchronize). Read retained step logs to replace pending wording with precise exercised/skipped/failed result; do not reapply operator rules or blame IR-87's 900s red on firewall. |\n| 90 | OPEN disk refusal/context | FIRED, ripe now | COMPOSE rig-root/target-volume start refusal + current free-space failure context, prerequisite for IR-85 rerun. Reclaims mitigate only. Latest known 3167 unit pass followed by disk floor red is classified at its observed step; unavailable earlier PR logs remain unclassified. |\n| 91 | CLOSED by filing lane | FIRED historically | CARRY closed. Preserve cited tracked artifacts and scratch manifests; parent cleanup retained evidence, so no reopening shown. |\n| 92 | OPEN, says fix unassigned | FIRED inject/IO-funnel remedy; parent reports core215/217 merged | PARENT DECISION. Mark header stale but do not close here. Source/contract verification must distinguish inject success publication from relay ordering and per-msg-id exact-once; parent owns substantive reconciliation. |\n| 93 | OPEN production symbols | UNKNOWN new packaging touch; release build alone is not a source touch | COMPOSE next packaging intake decision, keep open. Successful release build is not PDB availability, symbol matching, installation, or usable frame evidence. Preserve size/profile/operator trade rather than assuming approval. |\n| 94 | OPEN scanner reach | FIRED at newly added brainread gate; mandatory before bounded serve_sync migration | COMPOSE fail-on-unclassified stream-server census. Current brainread.rs:199 and 306–320 retain name shape/three-file registry. Independent gate defect, not cause of golden sync red. |\n| 95 | OPEN, measured/censused, diagnostic-only instrumentation | FIRED comparison already ran | COMPOSE prioritized observability + separately versioned exchange-correlated producer trace; retain open. 317/321 is classifier estimate with membership slop, 15 unclassified, not repo-wide floor/rate; no blanket 304-site editing. Diagnostic patch is unlanded, not release behavior. Preserve censored expiry, filtered final snapshot, no stream-between-polls claim, and no inferred budget fix. |\n| 96 | OPEN cause-unclassified | NOT FIRED for named new qualifying event on supplied facts; cheap discriminator still unrun | CARRY with explicit next-intake investigation, not resolved/non-defect. 0/1 candidate CI vs 3/3 diagnostic HEAVY is confounded tree/workload/box, plus IR-97. Brief delivered to offline hertz is pending acknowledgement, not executing. |\n| 97 | OPEN protocol deviation | FIRED repeated-run experiment | COMPOSE mandatory between-run identity census/accounting before any repeated IR-85/95/96 work. 0/6/12 carried residues are counts, not measured load or sync cause; 18 seen vs 15 killed does not prove three self-exits. Cleanups do not cure harness enforcement. |\n\n## Load-bearing deltas for the parent's edit\n1. **Retire duplicate work, not residual mechanisms:** close IR-66; IR-73's source contract is implemented at all eight sites and both docs rereads. Amend their stale top-of-register riders. Keep IR-86 capacity/docs dependency debt separate. IR-57 pick-audit and IR-59 disk-floor are already tools, not future tooling proposals.\n2. **Lifecycle wording needs reconciliation:** IR-69's parked header contradicts its own landed/residual addendum; IR-83's rule-blocked/LAN-only prose conflicts with IR-89's applied tailnet and firewall proof; IR-89's next-golden trigger fired but exact step proof is still needed; IR-92's unassigned header conflicts with parent's merged core215/217 fact. IR-80's product-candidate opening must be read through later scoped fixture findings. IR-82's #285 lane linkage did not deliver its pidfile retention.\n3. **No causal laundering at release close:** v0.69.0 c105 at 16df0e41 shipped under explicit operator SHIP with known candidate a9e786b2 sync red. 121 scoped passes, release build success, and 3167 Windows unit passes prove exactly those observations. The later floor failure at 14.3 vs 32 GiB is not a unit-test failure; unavailable earlier PR unit logs are still unclassified. No disk/load attribution for sync/convoy from overlap or pass-after-reclaim.\n4. **Cleanup accounting remains mitigation:** retain separate 62.32 GiB root-target and 59.70 GiB CI-debug measurements; later 38 clean merged worktrees/obsolete clone etc yielded net 4.22 GiB. Do not conflate file-length totals with free-space deltas, or report a structural capacity fix. Parent confirms no dirty/unmerged/retained evidence removed.\n5. **Coherent next-intake packages:** (A) workflow/driver resource contract: IR-59/60/76/86/87/90/97, preserving separate conditions and budgets; (B) pool teardown adoption: IR-88 with earlier-range pool audit, IR-64 operator decision separate; (C) test lifetime work: IR-63/79/80 plus Linux IR-74/75, without collapsing fixture vs product identity debt IR-81/82; (D) diagnostic continuation: IR-85/95/96 only after occupancy/disk/between-run prerequisites, with no budget widening; (E) small seam-triggered items: IR-94 gate reach and IR-93 symbol packaging. All hertz-shaped work is proposed/pending acknowledgement while offline, not dispatched-and-executing.\n\n## Verification limits\nRead-only tools only; no tests, builds, formatters, linters, probes, re-runs, board writes, or file edits. Closure recommendations use existing recorded proof plus targeted current-source reads, not new runtime verification. Some touch triggers are honestly UNKNOWN because exhaustive change-history traversal was neither supplied nor necessary for a carry ruling."
  },
  "parent_rulings": {
    "ir92": "Core PR215 docs-only; product inject publisher remains absent. Deployah corrected source comment 5628532753 and confirmed readback in delivery16. IR92 stays open.",
    "closure": [
      1,
      4,
      66,
      73
    ],
    "others": "Existing built/retired dispositions preserved; residuals carry or compose as recorded in tracked sweep. UNKNOWN triggers are not disproved; source reads are not new executions."
  }
}