Version v0.2.7 Archive ARCHIVE

This Site Provides Two Artifacts

📁 Archive (this page)

Immutable evidence and documentation. Static, versioned, cryptographically checksummed.

⚡ Demo (hosted at /demo/)

Interactive execution of the same version. Produces evidence packs verifiable against this archive.

This archive is immutable. The hosted demo at /demo/ is the live instantiation of this same version.

Field Manual (fm.tex/pdf): obligation ledger used to drive version promotions.

Open Hosted Demo Open Auditor Tool

For Auditors: 3-Step Verification

Run the boundary demo — Open demo, click "Run Boundary Demo", observe VERIFIED/REFUTED/ABSTAINED outcomes
Download evidence pack — Click "Download Evidence Pack" after demo completes
Verify in auditor tool — Open verifier, upload pack, confirm PASS (or tamper and observe FAIL)

Full checklist: 5-minute auditor verification

Ready-to-Verify: Example Evidence Packs (no demo required)

Download pre-built examples to test the auditor tool without running the demo:

📥 Download Examples (PASS + FAIL) Open Auditor Tool

The examples.json file contains both valid (PASS) and tampered (FAIL) packs for testing.

This is the archive for MathLedger version v0.2.7. All artifacts below are static, verifiable, and immutable.

Release Delta: v0.2.7

Changed:

Regenerated verifier from generate_v027_verifier.py with correct domain separation
Added GENERATED_FROM_COMMIT marker in verifier HTML for staleness detection
Added tools/verify_verifier_freshness.py build assertion
Added stage-wise trace scripts for crypto parity debugging

Did not change:

Tier A/B/C invariant counts (10/1/3)
Python attestation code (attestation/dual_root.py)
Hash contract (identical to what v0.2.6 SHOULD have been)
Demo functionality and verification flow

Still not enforced:

FV Mechanical Verification (no Lean/Z3)
Multi-Model Consensus (single partitioner)
RFL Integration (no learning loop)

Archive Contents

Artifact	Description
For Auditors	5-minute verification checklist
Scope Lock	What this version does and does not demonstrate
Explanation	How the demo explains its own behavior
Invariants	Tier A/B/C enforcement status
Hostile Rehearsal	Answers to skeptical questions
Fixtures	Regression test cases with golden outputs
Evidence Pack	Replay verification artifacts
Manifest	Version metadata + file checksums

Local Execution

Local Execution

Run locally instead of using hosted demo

git clone https://github.com/helpfuldolphin/mathledger
git checkout v0.2.7-verifier-parity
uv run python demo/app.py
Open http://localhost:8000

Invariant Details

Tier A: Cryptographically/Structurally Enforced (10)

Canonicalization Determinism (RFC 8785-style)
H_t = SHA256(R_t || U_t)
ADV Excluded from R_t
Content-Derived IDs
Replay Uses Same Code Paths
Double-Commit Returns 409
No Silent Authority
Trust-Class Monotonicity
Abstention Preservation
Audit Surface Version Field

Tier B: Logged, Not Hard-Gated (1)

MV Validator Correctness (edge cases)

Tier C: Documented, Not Enforced (3)

FV Mechanical Verification
Multi-Model Consensus
RFL Integration

Verification

To verify this archive matches the source:

Clone the repository
Checkout commit 5d01b4b1446ee323b10ff43c79a9b49589d68061
Run uv run python scripts/build_static_site.py --version v0.2.7
Compare generated files to this archive

File checksums are in manifest.json.