Files
dotfiles/claude/memory
David F GliddenandClaude Opus 5 69e258116a [HARDENING] PENDING-142: the open/closed criterion verifies an adjacent property
Filed from Task 1 of the 2026-08-17 jurist relay. `governance_state()` computes
openness from one signal — whether a REVIEWED header names the PENDING id — and
never reads the item's `Awaiting:` field, any status field, or the ruling's
`Decision:`. Six items are misclassified in both directions:

- 3 falsely OPEN (78, 81, 82): rulings that name the title, not the id. All
  AUTHORIZED 2026-07-28. REVIEWED-78's own Notes record that it was filed as a
  separate entry precisely to satisfy the closure rule as it then stood; the rule
  later changed, breaking the entries written to comply with it.
- 3 suppressed under a design gate rather than a steward authorization, one of
  which (PENDING-121) is marked HELD OPEN by its own ruling.
- 2 structurally unclosable: no `PENDING-N` in the header, so no ruling can ever
  close them. One is the ICP-19 item gating Observer Problem work.
- 39 suppressed items still carry a live-reading `Awaiting:` line.

Removing the false opens and restoring the false closures leaves 29 — the number
the tool reports. The change proof standing behind the current implementation
measured exactly that count (18 to 19). A count-based control cannot see a
classification wrong in both directions by equal amounts: its subject was the
population size, the claim's subject was each item's disposition.

Addendum 1 flags that the selftest asserts the defect as intended behaviour,
with one of the three hidden items as its fixture.

Nothing patched — the relay scoped this to findings only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Y6t6qx7cpaCu5xGdD36u4
2026-08-17 14:57:48 +02:00
..