A Blocked-by: target that a seat has superseded in the body keeps being discovered from the comment archive, and when that archived number is also unreadable, H19 emits an UNJUDGED row that no correct action by the card's owner can ever clear.
Found by the domain:services seat (#6021) while discharging the patrol anchor's UNJUDGED rows at seating. ⛔ Report-only from this lane: the fix lands in scripts/pm/check-half-states.mjs, which is not this lane's. Grading and routing left to triage.
The measurement
Anchor #9857, sweep 2026-09-16T01:55:47Z, row:
H19 #11975 — pm:blocked and 1 of 2 Blocked-by: target(s) could NOT be resolved this sweep (#13515 (HTTP 404)) — the set judged against the BODY's Blocked-by: set …
But #11975's body no longer names #13515 at all. Its machine-readable line reads Blocked-by: #18336, refreshed by the triage seat at 2026-09-15T23:14Z — i.e. ~2.7 h BEFORE that sweep. The body's only Blocked-by: spellings are #18336 (live) and a struck `Blocked-by: #11974` quoted inside prose.
Where #13515 actually comes from — enumerated over the comment channel:
| carrier |
created |
Blocked-by: target(s) |
| comment 5639940830 |
2026-09-11T19:59Z |
13515 |
| comment 5640543168 |
2026-09-11T20:56Z |
13515 |
| comment 5682194651 |
2026-09-15T14:40Z |
13515 |
| comment 5689373281 |
2026-09-15T23:13Z |
13515, 18336 |
⇒ four archived comments, one of them triage's own re-pointing note, which necessarily names the old number in order to explain that it is dead.
Readability, re-probed in this act (2026-09-16T06:33Z) with positive controls (⛔ not taken from the sweep's word): #13515 → 404, #13514 → 404, #13689 → 404; controls #18336 → 200, #11973 → 200.
Why this is a defect and not the documented design
The file states the split deliberately, and it is the right split:
⚠️ DISCOVERING from both channels and JUDGING from both are two different claims, and only the first one survived measurement. … The union is therefore still what is discovered and resolved, and the BODY's set is what the row judges whenever the body states one (#17564).
The UNJUDGED branch does not sit on the judging step — it sits on the resolution step, which still runs over the union. So #17564's fix corrects which targets decide the verdict, and leaves a superseded-and-unreadable target able to veto the verdict from the archive. The two conditions have to coincide for it to bite, which is why it survived #17564:
- the target was superseded in the body (so judging correctly ignores it), and
- the superseded number is unreadable (so resolution cannot dismiss it either).
Why it cannot be worked around from the card's side
⭐ This is the part that makes it worth a card rather than a note. The card's owner did the prescribed thing — refreshed the body line to the live blocker — and the row persists. The only remaining lever would be editing or deleting the four archived comments, which is precisely what the protocol forbids: #11975's own body says of its dead pointers 「they record what an earlier seat measured and why the line was migrated, and editing them would erase that」. ⇒ the row re-fires every 6 h, permanently, and UNJUDGED rows are the ones the anchor says 「nothing in a later sweep will resolve on its own … the rows to judge BY HAND」. A permanently-unclearable row in that class is noise in exactly the channel that is supposed to have none.
Scope note — ⛔ not a one-card artefact
#13514, #13515 and #13689 are all unreadable and all belong to the #11663 platform-admin re-anchor epic. #13689 is named by #11973's body today, so that card is the same H19 UNJUDGED shape through the body channel rather than the archive. ⇒ whenever #11973's body is likewise re-pointed, this defect captures it too.
⛔ This card does not propose the remedy — whether resolution should narrow to the judged set, whether an unresolvable target outside the judged set should downgrade below UNJUDGED, or whether the anchor should render it as a distinct class, is the owning seat's call.
Dedup words: H19 UNJUDGED superseded comment target · check-half-states union resolution body judging · #17564 body-authoritative Blocked-by · unreadable Blocked-by 404 archive · unclearable half-state row
Generated by Claude Code
A
Blocked-by:target that a seat has superseded in the body keeps being discovered from the comment archive, and when that archived number is also unreadable, H19 emits anUNJUDGEDrow that no correct action by the card's owner can ever clear.Found by the
domain:servicesseat (#6021) while discharging the patrol anchor's UNJUDGED rows at seating. ⛔ Report-only from this lane: the fix lands inscripts/pm/check-half-states.mjs, which is not this lane's. Grading and routing left to triage.The measurement
Anchor #9857, sweep
2026-09-16T01:55:47Z, row:But #11975's body no longer names
#13515at all. Its machine-readable line readsBlocked-by: #18336, refreshed by the triage seat at2026-09-15T23:14Z— i.e. ~2.7 h BEFORE that sweep. The body's onlyBlocked-by:spellings are#18336(live) and a struck`Blocked-by: #11974`quoted inside prose.Where
#13515actually comes from — enumerated over the comment channel:Blocked-by:target(s)13515135151351513515,18336⇒ four archived comments, one of them triage's own re-pointing note, which necessarily names the old number in order to explain that it is dead.
Readability, re-probed in this act (2026-09-16T06:33Z) with positive controls (⛔ not taken from the sweep's word):
#13515→ 404,#13514→ 404,#13689→ 404; controls#18336→ 200,#11973→ 200.Why this is a defect and not the documented design
The file states the split deliberately, and it is the right split:
The
UNJUDGEDbranch does not sit on the judging step — it sits on the resolution step, which still runs over the union. So #17564's fix corrects which targets decide the verdict, and leaves a superseded-and-unreadable target able to veto the verdict from the archive. The two conditions have to coincide for it to bite, which is why it survived #17564:Why it cannot be worked around from the card's side
⭐ This is the part that makes it worth a card rather than a note. The card's owner did the prescribed thing — refreshed the body line to the live blocker — and the row persists. The only remaining lever would be editing or deleting the four archived comments, which is precisely what the protocol forbids: #11975's own body says of its dead pointers 「they record what an earlier seat measured and why the line was migrated, and editing them would erase that」. ⇒ the row re-fires every 6 h, permanently, and
UNJUDGEDrows are the ones the anchor says 「nothing in a later sweep will resolve on its own … the rows to judge BY HAND」. A permanently-unclearable row in that class is noise in exactly the channel that is supposed to have none.Scope note — ⛔ not a one-card artefact
#13514,#13515and#13689are all unreadable and all belong to the #11663 platform-admin re-anchor epic.#13689is named by #11973's body today, so that card is the same H19UNJUDGEDshape through the body channel rather than the archive. ⇒ whenever #11973's body is likewise re-pointed, this defect captures it too.⛔ This card does not propose the remedy — whether resolution should narrow to the judged set, whether an unresolvable target outside the judged set should downgrade below
UNJUDGED, or whether the anchor should render it as a distinct class, is the owning seat's call.Dedup words:
H19 UNJUDGED superseded comment target·check-half-states union resolution body judging·#17564 body-authoritative Blocked-by·unreadable Blocked-by 404 archive·unclearable half-state rowGenerated by Claude Code