Public evidence
Machine-checked verification for calculation version 1.0.0 · tier engine_tested
CVP status
CVP VERIFIED · production STALE · CVP protocol 1.0.0-proposed · Engineering assurance · offset point + end moment at station (sum); + O3 mpmath tabulated δ.
O3 tabulated vectors only.
Legacy regression suite: 3/3 calculation tests · Production surface contract 6/6
Three distinct suites: educational examples on the calculator page, this legacy regression count (3/3 golden + boundary), and the CVP verification suite below. They are not the same number. Property, metamorphic, round-trip, O3, and interface statuses/checks are recorded in the CVP Manifest . SKIP (0/0) means that suite has no published vectors.
Protocol checks from the Evidence Manifest. Distinct from the legacy regression suite above. Verification revision 2026-09-27.o2-o3. Calculation version 1.0.0. CVP 1.0.0-proposed. 4/4 golden · 1/1 CVP boundary · 3/3 invalid · 1/1 property · 1/1 metamorphic · 8/8 O3 · 2/2 cross-interface · 6/6 CVP contract. digest 72fa27415cb0. O2: delta vs a separate-module identity (≤2 ULP). Not tip-only under either component alone. ≤2 ULP vs O3 applies only to the published tabulated offset-moment-at vectors.
Fingerprint sha256:0d74f6d71e18c3f8a0b2fe7f7f2d3a32ea8f786a3481552826785a56a67a92b7
Input schema sha256:8e4ffc824b7c00be96afebc92ba0e72cf37360736b2ac6640afb39eee577aba1 · Output schema sha256:d049216cfdd1a2ed11524da2844ec094d4cff76c268b22ea3d717eca66c55e89 · Build-time SHA-256 digests prove published artifacts agree with each other (release_integrity.scope=workspace). Production attestation GETs canonical URLs twice (public/cached view and origin), including Capability HTML, via npm run attest:production --write
(published at /.well-known/calculatorx-production-attestation.json) and fails if the public Capability page advertises a different calculation_version. This is artifact consistency, not an independent immutable release log.
Engine identity and declared limitations.
Standards and references supporting this tool specification. Methods are listed separately — they are algorithms, not bibliographic sources.
Aggregate outcomes, scope and artifact commitments are public. Complete test inputs, expected values, execution records and oracle infrastructure are retained privately. This summary does not independently reproduce the full verification run.