Did it run?
PASS · FAIL · BLOCKED · NOT_APPLICABLE
Evidence Lab · TV002
Verification without
category errors.
Four computational engines answer different questions. Every result keeps execution, proposition fidelity, claim outcome, and scientific support separate.
Chapter evidence pendingClaim-level applicability
Infrastructure evidence is not chapter evidence
The last banked bootstrap run passed Python, native Sage, Lean, and LaTeX, while the required Mathematica layer reported INFRA_BLOCKED. Owner configuration is recorded but NOT_YET_EXECUTED. No FC claim record is published from that run.
Chapter evidence map
What exists today.
This matrix reports public claim-record availability by chapter and engine. It does not collapse scientific support into a single badge.
| Ch. | Research obligation | Workflow | Lean | Python | Sage | Mathematica | Evidence |
|---|
The governing rule
A green run is not a green theory.
A program can execute correctly, test the exact frozen proposition, and faithfully refute it. That is a successful verification process with an adverse scientific result—not a software failure to hide.
Likewise, four matching outputs cannot repair circular premises, hidden inputs, weak proposition mapping, or an absent physical bridge.
Four result axes
Every evidence record answers four questions.
Did it test the exact claim?
EXACT · WEAKER · MISMATCH · NOT_MAPPED
What happened?
CONFIRMED · REFUTED · INDETERMINATE · NOT_APPLICABLE
What follows scientifically?
SUPPORTED_WITHIN_SCOPE · ADVERSE · BLOCKED · NOT_APPLICABLE
Lean
Typed implication from explicit hypotheses, with exported declarations and complete axiom closure.
Not a physical-interpretation oracle.Python
Portable reference calculation, assertion orchestration, tolerances, and readable hostile controls.
Passing code remains evidence about its implementation.Native Sage
Independent exact mathematics using Sage objects and algorithms—not a Python/SymPy fallback.
Shared lineage must be disclosed.Mathematica
Independent symbolic route with a pinned Wolfram kernel, transcript, and hard license gate.
Missing credentials are infrastructure-blocked.Applicability is claim-specific
Not every claim belongs in every engine. Applicable requires a reason, implementation, lineage, and hostile controls. Not applicable requires a substantive reason and contributes no fabricated concordance.
Promotion path
Four banked stops—not one progress bar.
Recovery freeze
Source custody, provenance, exact questions, and no inherited authority.
Exposition freeze
Undergraduate-readable argument, typed definitions, claims, limits, and figures.
Verification freeze
Claim-bound implementations, hostile controls, evidence, and concordance.
Promotion review
Independent council, owner approval, protected workflow, and exact commit.
Current promotion-path posture
PROMOTION-PATH-001 blocks the first real CP4 authorization. Repository bootstrap banking and successful smoke or infrastructure runs do not promote a scientific chapter; the protected two-phase workflow must bind completed exact-candidate CI, council review, authenticated owner approval, and the exact promoted commit.