Home Developers Evidence math.pythagorean

Public evidence

math.pythagorean

Machine-checked verification for calculation version 1.1.6 · tier engine_tested

CVP status

CVP VERIFIED · production STALE · CVP protocol 1.0.0-proposed · Engineering assurance

Positive sides; solve a|b|c or verify

Declared partition coverage
PASS · 5/5 declared partitions (solve-c, solve-b, solve-a, verify, invalid-domain)
Versions
Calculation 1.1.6 · CVP protocol 1.0.0-proposed · Evidence 2026-10-28.meta-metrics-v2
Verification revision
2026-10-28.meta-metrics-v2 · 2/2 property · digest 4e661f033102

Verification

Legacy regression suite: 16/16 calculation tests · Production surface contract 6/6

Three distinct suites: educational examples on the calculator page, this legacy regression count (16/16 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.

    STALE · Build schema 1.1.6 matches page · production binding STALE · Semantic contract ✓ · Last attestation PASS · current evidence changed · re-attestation required · CVP STALE · attestation STALE — Production CURRENT withheld · Public/cache ✓ · Origin ✓

CVP verification suite

Protocol checks from the Evidence Manifest. Distinct from the legacy regression suite above. Verification revision 2026-10-28.meta-metrics-v2. Calculation version 1.1.6. CVP 1.0.0-proposed. 93/93 golden · 10/10 CVP boundary · 12/12 invalid · 2/2 property · 2/2 metamorphic · 4/4 cross-interface · 6/6 CVP contract. digest 4e661f033102. 93 independent full result packs across4operations and extreme scales; no exhaustive-domain claim

  • Golden (oracle-backed) 93 / 93
  • CVP boundary 10 / 10
  • Invalid input 12 / 12
  • Property 2 / 2
  • Metamorphic 2 / 2
  • Cross-interface 4 / 4
  • CVP contract 6 / 6
  • Interfaces PASS · UI (SSR) / REST / MCP
  • Interface claim ui-ssr is query-result HTML, not a live browser session.
  • Assurance Engineering
  • release artifacts aligned PASS
  • schema output required declared PASS
  • schema valid input executes PASS
  • engine success output validates schema PASS
  • schema rejects incomplete input PASS
  • rest success payload validates schema PASS

Fingerprint sha256:ebc6b64dfeb7389ca51eef536e76905f275a46b7b8894f1b6e90fccd64ea2c63

Input schema sha256:7cd74f1a22f5cd13ec9daa7c016ce506d8ecf41b0eecb2aca71974a67f92df77 · Output schema sha256:bd9cbc7a0e80c9c2e4de2d19211a3686597a4e6d83a082faac7ad654eefe3c93 · 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.

Build & scope

Engine identity and declared limitations.

Tool
pythagorean
Engine
pythagorean
Engine build
2026-10-26
Evidence core
2026-10-26T04:58:17.015Z
Rendered
2026-10-28T03:01:57.871Z
Last reviewed
—

Assumptions

  • Right triangle; positive side lengths.
  • c > a and c > b when solving for a leg.
  • Exactly two fields are inputs when solving. Explicit solve_for selects the output. If all three are supplied without solve_for, they are verified rather than overwritten.
  • Interactive evaluation, shared URLs, and REST use the same engine, solve_for contract, and error codes.
  • Share URL is canonical: solve_for=a|b|c forces solve even if a leftover third side is present; mode=verify is required to stay in Verify after a tab change.

Limitations

  • Positive finite binary64 side lengths in consistent units. Decimal text at most512characters,strict types and matching aliases. Nonzero-to-zero conversion rejects.
  • Four operations:c,a,b,verify. solve_for selects the output;all supplied side tokens still validate. All three without solve_for verify;mode=verify conflicts with solve_for.
  • Verification checks nondegenerate geometry and squared relative residual |a²+b²-c²|/c²<=1e-6 with scaled squares. Approximate binary64 diagnostics may differ by2e-15 near the threshold; no exact-equality proof.
  • Solved sides must fit positive finite binary64. Unrepresentable positive area/perimeter are null with explicit range status;invalid verify has no right-angle area. Values display12significant digits. Exact radical only for exactly representable safe-integer radicands.
  • Diagram is schematic,not to scale;no right-angle diagram for failed verification. Browser calculations run locally;shared URLs and REST/MCP transmit inputs and may enter logs.

Sources

Standards and references supporting this tool specification. Methods are listed separately — they are algorithms, not bibliographic sources.

Verification disclosure

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.