Public evidence
Machine-checked verification for calculation version 1.0.9 · tier engine_tested
CVP status
CVP VERIFIED · CVP protocol 1.0.0-proposed · Core assurance
any finite real x; mathematical principal range (−90°, 90°); binary64 may round to ±90°
Legacy regression suite: 10/10 calculation tests · Production surface contract 6/6
Three distinct suites: educational examples on the calculator page, this legacy regression count (10/10 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-10-16.inverse-trig-discovery-pins-v8. Calculation version 1.0.9. CVP 1.0.0-proposed. 9/9 golden · 3/3 CVP boundary · 3/3 invalid · 8/8 property · 3/3 metamorphic · 4/4 round-trip · 21/21 O3 · 31/31 cross-interface · 4/4 cross-calculator · 4/4 URL→result→graph · 6/6 CVP contract. digest 4fb2a8fe2cc5.
Fingerprint sha256:f4a509fca9e3c44178b7b8a02893b6156f9aef2de65b5802022df58076e59a83
Input schema sha256:2a41a9980f4d9dec9890f9c1211379bb434b0fe9d1a02110527337297ba1fa20 · Output schema sha256:ec1c6707934418696467e28589f6f5b47588c78046d7a9a47e2f9bf58f8a7d16 · 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.