Worked example · not insurance

Promoting an experimental result to a claim

The same method, applied to research. The crossing is a result becoming a claim that others may reuse: instrument → mapping → analysis → interpretation → claim → reuse. Nothing here is priced, covered or underwritten; the class is not offered for underwriting review.

The source

The five examples map an independent reproduction review of a builder’s experiment claims (CODEX_EMPIRICAL_REVIEW_RESUMED_v0.1.0, in the author’s local archive). The experiments tested software-governance behaviour; this is empirical research on software, not a natural-science study. Each example cites the review file it maps, with its SHA-256; a test checks those hashes where the archive is available. The review records its own ceiling: methodological inference not adjudicated. That ceiling is kept here.

Five claims

ClaimOutcomeValue (UV)Structure (US)Source
SCI-001 SURF-14: ablation result independently reproduced (four of five detections lost)EXECUTE KNOWNUNTESTEDSURF_14_ABLATION_REEXECUTION.md
3b45c209af2d01b3…
SCI-002 SURF-10 pair 2: the pre-state was not preserved, so the comparison cannot be rebuilt from bytesHOLD UNAVAILABLEPENDINGUNTESTEDSURF_10_EVIDENCE_SCOPE_REVIEW.md
1e5ee07a57ae692a…
SCI-003 SURF-15c: the detection path compares two hard-coded dictionaries; no authoritative input is ever loadedHOLD INVARIANT_FAILEDKNOWNCHALLENGEDSURF_15C_SURF_03_EMPIRICAL_REVERIFICATION.md
1b1237437e153627…
SCI-004 Package file count: 24 manifested payload files versus 25 files counted recursivelyHOLD UNRESOLVEDDISPUTEDUNTESTEDDISCREPANCY_REGISTER.yaml
ea60069167dce5fa…
SCI-005 The same count restated under an explicit, prospective counting conventionEXECUTE KNOWNUNTESTEDOPERATOR_COUNTING_RESOLUTION.yaml
ab47ee986395a3a2…

What each outcome means

Claim ceiling

Class JSON · Class details and mutation battery · Try it in the inspector