The E2 instrument ran, and reported a null
The full E2 measurement path — schema-conforming rows, the shared-item rule, one frozen reduction, the excess-joint-failure estimand, and the pre-registered negative controls — was exercised against three toy mechanisms. Sixty-six rows passed the real E2 validator with zero violations; the observed dependence was indistinguishable from independence at twenty-two items, and the controls behaved exactly. It is not E2, and it says so on its face; what moved is that the instrument is proven and the cost of the real study is now a number.
E2 — the shared-item measurement contract
CC-Framework's first empirical rung was frozen before any dataset was inspected, and no conforming dataset has been collected. On 2026-08-23 the measurement pipeline was rehearsed end to end on three synthetic mechanisms — a documented dry run, not E2 — which validated the instrument and put a number on what real E2 costs: about 1,097 shared items run through every guardrail to estimate the rates to within five points. That is the bar the next artifact must clear. E2 stays frozen and untested until it does.
Incidence, not existence — the receipt-kernel gap
Ghost-Ark's collision claim stands in contracted form: possible, not observed (a sample of 64 real payloads carried zero pathology classes). The gap its thesis names after that result: incidence, not existence — does any real consumer population currently depend on a distinction some deployed canonicalizer destroys? (Separately, its falsifier ledger keeps F3 — that the consumer set is stable in practice — open and, in its own words, the most under-attacked of the five.)
The observatory redesign — v0.4
This site became the Evidence Observatory: a six-module question grammar, the claim observatory view, an interactive feasible-worlds instrument, and geometry assertions that make a figure that lies about probability fail the build. Registry at thirteen claims; one stale binding found and re-pinned in the process — the log has the details.
Module 004 — the attestation boundary
What can enclave attestation prove about a file's life before the enclave first touched it? The standing conjecture: nothing, by itself. The page exists, says PLANNED on its face, and carries no evidence because there is none to carry.
This page is hand-written and owner-attested; it carries no evidence markers and borrows none. When it goes stale, it is replaced, not accreted — the previous state survives in git history, which is where history belongs.