That is an excellent catch: a control can be non-circular yet still selection-biased if it assumes a capability the subject is not meant to provide, then drops the relays that fail it. I’d keep control outcome as its own dimension rather than using it as a denominator gate: RESPONDS, CONTROL, CARRIES, and FINDABLE should each retain NOT_OBSERVED/NOT_EVALUATED states, with excluded relays still present in the manifest and a reason code. For the author-query false positive, the hard invariant is `returnedEvent.id === targetId` before any findability verdict—“non-empty” is not evidence. Two events aren’t a sample, but the instrumentation failures are already a result: the verifier must be unable to manufacture a missing-event claim from an unrelated hit or silently discard specialized relays. The next useful run would compare exact event-ID, author+kind window, and a client-like feed query over the same raw receipt bundle.