Reproducibility & Code Verification
Every numerical calculation, mathematical formalization batch, and visual telemetry record across the Science of Fabric Reality corpus is designed for complete local and independent reproduction.
┌─────────────────────────────────────────────────────────────────────────────┐
│ REPRODUCIBILITY & VERIFICATION STACK │
├──────────────────────────────┬───────────────────────────┬──────────────────┤
│ Subsystem │ Toolchain / Engine │ Determinism Gate │
├──────────────────────────────┼───────────────────────────┼──────────────────┤
│ Formal Lean 4 Prover │ Lake / Lean v4.3.0 │ 0 Compiler Errors│
│ Numerical Simulation Solvers │ Node.js / C++ / WebAssembly│ Bounded U_NUM │
│ Dual Citation Truth Auditor │ RFC 8785 JSON Canonical. │ 0 Hash Drift │
│ Visual QA Evidence Pipeline │ Chromium / Puppeteer Core │ 0 Theme Drift │
└──────────────────────────────┴───────────────────────────┴──────────────────┘1. Automated Verification Commands
Independent researchers can verify all formal proofs, reader surfaces, and citation records locally from the repository root:
# 1. Verify TypeScript types across the entire application
npm run typecheck
# 2. Execute deterministic reader surface audit (790 files)
node scripts/audit-reader-surface.mjs
# 3. Verify public claim boundaries and epistemic demarcations
node scripts/audit-public-claim-boundaries-v3.mjs
# 4. Audit RFC 8785 JCS canonical metadata hashes and citation sync
node scripts/audit-citations-and-hashes.mjs
# 5. Execute recursive CURRENT reference resolver audit
node scripts/audit-current-resolver.mjs
# 6. Execute full deterministic Fabrica orchestrator verification
npm run fabric:verify
# 7. Compile static documentation bundle
npm run docs:build2. Formal Proof Verification (Lean 4 Status)
All interactive formalization source files reside in [docs/04-mathematics/lean/](file:///c:/gilc.us.mesh.repos/ivanpasev.com/docs/04-mathematics/lean/).
To audit or build the formalization package:
# Build the formal proof registry
node scripts/build-formal-proof-registry.mjs┌─────────────────────────────────────────────────────────────────────────────┐
│ LEAN 4 STATUS LEDGER │
├──────────────────────────────────────────────────────────────┬──────────────┤
│ Metric │ Value │
├──────────────────────────────────────────────────────────────┼──────────────┤
│ Lean Source Files Discovered │ 5 │
│ Lean Files Compiling Syntactically │ 5 │
│ Constitutional Axioms Formalized │ 5 │
│ Formal Definitions Type-Checked │ 3 │
│ Open Theorem Formalization Targets │ 4 │
│ Machine-Verified Theorems Accepted by Lean │ 0 │
│ Lean Build / Compilation Failures │ 0 │
└──────────────────────────────────────────────────────────────┴──────────────┘Epistemic Rule: Compilation vs Proof
Syntactic compilation in Lean 4 verifies type signatures and well-formedness of declarations. It does not constitute completed machine-verified theorem proofs for open targets. Active machine-verified theorem count is strictly 0.
3. Reference Atlas & RFC 8785 Canonical Hashing
To ensure immutable provenance, all 19 external reference anchors are hashed using the RFC 8785 JSON Canonicalization Scheme (JCS):
To recompute and verify all 5 reference atlases:
node scripts/build-reference-registries.mjs
node scripts/audit-citations-and-hashes.mjs4. Visual QA & Screen Telemetry Epochs
Visual evidence is captured in immutable, versioned epochs using Chromium-based headless telemetry.
- Active Epoch:
omega284g-r1b9a(28 page frames PASS, 16 figure frames PASS). - Manifests: Available in
reports/current/visual-qa/epochs/omega284g-r1b9a/.