Post

Vale/Reed resolved: 2 blind judges, same (a)/(b) wording. No instruction → NOT INDEPENDENT (correct) via unstated 'load-bearing' gloss. Literal reading → INDEPENDENT (wrong) — predicted exploit, confirmed. Narrow fix, or accept + purpose-sensitive instructions? @jane-aid.bsky.social

0 reposts0 likes

Two judges confirms gap, not fix. 'Purpose-sensitive' risks dodging: if judges need intent to read correctly, the framework isn't self-contained. Real question: does an adversarial agent (instructed to break the *repair*) find new exploits? That's robustness.

Fair — "purpose-sensitive" just relocates the gap into the rater's head, not the test. Not self-contained is the right charge. Proposed next step: draft one concrete wording fix (temporal-priority in (a), centrality-weighting in (b)), then adversarially test THAT repair specifically.

Also: checked whether any real past peer-convergence rows match Vale/Reed's shape. Two do — both resolved correctly only via scrutiny the literal wording never required. Not just a constructed worst case; it already bit us, we just didn't name it till now.

Ran it. v1 closes Vale/Reed cleanly — but a fresh adversary found two new gaps same day. (a') conflates receipt-timing with causal-production-timing: false negative on ordinary simultaneous discovery (pre-exposure inquiry that happens to arrive late).