Claim coverage map
Claim coverage map is one of 28 measurements this engine publishes in full. It is regenerated from a real run rather than transcribed, and it is shown here with its own claim boundary so the number and its limits arrive together.
The measurement
- Published artifacts
- 68
- Schema
- canli.alphac-claim-coverage-map.v1
- With a named guard
- 48
Coverage
Nested beyond what this page renders. Read it in the artifact.
Guarded only by the host mirror
- earnings_narrative_change_result.json
- pre_fomc_announcement_drift_feasibility.json
- spin_off_document_schema.json
- spin_off_lineage.json
- treasury_auction_concession_feasibility.json
- treasury_calendar_revision_audit.json
- treasury_wayback_pdf_schedule_audit.json
- treasury_wayback_schedule_audit.json
Last run
Reproduce kit
- Command
- /Users/arhancanli/alphaforge/.venv/bin/python scripts/reproduce.py
- Cwd
- /Users/arhancanli/alphaforge
- Exit code
- 0
- Outcome
- PASS
- Ran at
- 2026-08-22T05:20:10+00:00
Tail
- L2 signatures : 2 verified, 0 failed
- L3 golden master : PASS
- ALL CHECKS REPRODUCED. The published numbers match their hashes/signatures, and the engine is byte-deterministic.
Retracted claim gate
- Command
- /Users/arhancanli/alphaforge/.venv/bin/python scripts/check_retracted_claims.py
- Cwd
- /Users/arhancanli/alphaforge
- Exit code
- 0
- Outcome
- PASS
- Ran at
- 2026-08-22T05:20:27+00:00
Tail
- retracted-claims check: 12 rules over 2 root(s)
- PASS — no withdrawn claim is asserted anywhere in the publish set
Site verifiers
- Command
- npm run --silent verify
- Cwd
- /Users/arhancanli/meridian
- Exit code
- 1
- Outcome
- FAIL
- Ran at
- 2026-08-22T05:20:28+00:00
Tail
- - 59573 on /research/options-execution-foundation
- - 24.6 on /research/prereg-earnings-narrative-change
- FAILED: 8 untraceable numeral(s) on unsourced pages
Unit suite
- Command
- /Users/arhancanli/alphaforge/.venv/bin/python -m pytest tests/unit -q --no-cov
- Cwd
- /Users/arhancanli/alphaforge
- Exit code
- 0
- Outcome
- PASS
- Ran at
- 2026-08-22T05:18:00+00:00
Tail
- ........................................................................ [ 97%]
- ........................................................................ [ 99%]
- ................. [100%]
Mechanisms
- NAMED GUARD
- a test or verifier that mentions this artifact specifically
- RENDERED PAGE
- rendered as a measurement page and checked for a claim boundary
- SIGNATURE
- Ed25519 over the payload
CONTENT HASH. recomputed by the published reproduce kit; proves it was not edited after publication and nothing about whether it is right
HOST MIRROR. both hosts receive the identical file — the weakest, because it says two copies agree and nothing about what they say
Rebuilt before observing
Lint debt contract
- Cwd
- /Users/arhancanli/alphaforge
- Exit code
- 0
- Outcome
- PASS
- Ran at
- 2026-08-22T05:17:59+00:00
Command. /Users/arhancanli/alphaforge/.venv/bin/python scripts/export_lint_debt_contract.py
Tail
- /Users/arhancanli/alphaforge/artifacts/engineering/lint_debt_contract.json
Research export
- Command
- /Users/arhancanli/alphaforge/.venv/bin/python scripts/research_export.py
- Cwd
- /Users/arhancanli/alphaforge
- Exit code
- 0
- Outcome
- PASS
- Ran at
- 2026-08-22T05:17:59+00:00
Tail
- wrote /Users/arhancanli/meridian/public/glassbox/research.json (1058677 bytes)
- content_hash: sha256:cea00a82f9b34b989325e4b8ebbbc9cb2897bf8b122d940020ba44e9e5b17465
What mirror only means. We verify both hosts received the identical file, and nothing verifies the file. No test names it, it carries no content hash, it renders on no page. If its contents went stale or wrong, both hosts would publish the same wrong thing and every check would pass.
Why. Split coverage reads as coverage. Every guard here reports on itself and none reported on the set, so an artifact with no guard looked exactly like one with three.
Why rebuild first. The publish path rebuilds the derived contracts before anything checks them, so a suite observed before that rebuild reports a failure the publish never ships. The first run of this map did exactly that.
Check it yourself
Every figure above is read from /glassbox/claim_coverage_map.json, the
artifact the engine wrote. Nothing on this page is typed by hand: the page is generated from that
file, so a figure that moves in the artifact moves here and a figure that is not in the artifact
cannot appear here at all.