The measurement
- Published artifacts
- 215
- Schema
- canli.alphac-claim-coverage-map.v1
- With a named guard
- 152
Coverage
Nested beyond what this page renders. Read it in the artifact.
Last run
Reproduce kit
- Command
- /Users/arhancanli/alphaforge/.venv/bin/python3 scripts/reproduce.py
- Cwd
- /Users/arhancanli/alphaforge
- Exit code
- 0
- Outcome
- PASS
- Ran at
- 2026-08-25T11:17:02+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
- Cwd
- /Users/arhancanli/alphaforge
- Exit code
- 0
- Outcome
- PASS
- Ran at
- 2026-08-25T11:17:06+00:00
Command. /Users/arhancanli/alphaforge/.venv/bin/python3 scripts/check_retracted_claims.py
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
- 0
- Outcome
- PASS
- Ran at
- 2026-08-25T11:17:11+00:00
Tail
- corpus: 616029 numbers across 526 artifacts
- every numeral a reader can see traces to a published artifact
- README audit passed: 108 papers, 13 topic hubs, 84 measurements, 234 URLs, 228 packets (226 incomplete); deploy-gate source verified
Unit suite
- Command
- /Users/arhancanli/alphaforge/.venv/bin/python3 -m pytest tests/unit -q --no-cov
- Cwd
- /Users/arhancanli/alphaforge
- Exit code
- 0
- Outcome
- PASS
- Ran at
- 2026-08-25T11:16:00+00:00
Tail
- ........................................................................ [ 96%]
- ........................................................................ [ 98%]
- ................................................... [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-25T11:15:57+00:00
Command. /Users/arhancanli/alphaforge/.venv/bin/python3 scripts/export_lint_debt_contract.py
Tail
- /Users/arhancanli/alphaforge/artifacts/engineering/lint_debt_contract.json
Research export
- Command
- /Users/arhancanli/alphaforge/.venv/bin/python3 scripts/research_export.py
- Cwd
- /Users/arhancanli/alphaforge
- Exit code
- 0
- Outcome
- PASS
- Ran at
- 2026-08-25T11:15:57+00:00
Tail
- wrote /Users/arhancanli/meridian/public/glassbox/research.json (3698965 bytes)
- content_hash: sha256:28c8b30201cb8d4a6ff3c5e249a93c3cbf5ee98d4f4b12769c6012514b438d62
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.