Home Developers Evidence math.geometry.triangle

Public evidence

math.geometry.triangle

Machine-checked verification for calculation version 1.1.0 · tier engine_tested

CVP status

CVP VERIFIED · CVP protocol 1.0.0-proposed · Core assurance · all published modes

All5 Euclidean triangle modes, full ordered SSA candidates; exact dyadic SSS inequalities/Kahan area, stable SAS and SSA quadratic roots. Normal binary64 positive inputs/outputs; explicit conditioning guards and no absolute zero clamps. Independent mpmath750 reference; no spherical triangles.

Declared partition coverage
PASS · 6/6 declared partitions (sss, sas, asa, aas, ssa, invalid-domain)
Versions
Calculation 1.1.0 · CVP protocol 1.0.0-proposed · Evidence 2026-10-29.math-uuce-fields-v1
Verification revision
2026-10-29.math-uuce-fields-v1 · 3/3 property · digest 0c4df55e9ff8

Verification

Legacy regression suite: 10/10 calculation tests · Production surface contract 5/5

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.

    This calculator CURRENT · Public schema 1.1.0 matches · Semantic contract ✓ · Production attested · Public/cache ✓ · Origin ✓

CVP verification suite

Protocol checks from the Evidence Manifest. Distinct from the legacy regression suite above. Verification revision 2026-10-29.math-uuce-fields-v1. Calculation version 1.1.0. CVP 1.0.0-proposed. 168/168 golden · 2/2 CVP boundary · 75/75 invalid · 3/3 property · 4/4 metamorphic · 2/2 cross-interface · 1/1 cross-calculator · 5/5 CVP contract. digest 0c4df55e9ff8.

  • Golden (oracle-backed) 168 / 168
  • CVP boundary 2 / 2
  • Invalid input 75 / 75
  • Property 3 / 3
  • Metamorphic 4 / 4
  • Cross-interface 2 / 2
  • Cross-calculator 1 / 1
  • CVP contract 5 / 5
  • Interfaces PASS · UI (SSR) / REST / MCP
  • Interface claim ui-ssr is query-result HTML, not a live browser session. Error-path engine·REST·MCP 1/1 (status, code, calculation_version). SSR compared on URL-canonical requested calculations; empty query is idle (not an error) and JSON-typed object/array inputs are REST/MCP-only.
  • Verified scope all published modes
  • Assurance Core
  • release artifacts aligned PASS
  • schema output required declared PASS
  • schema valid input executes PASS
  • engine success output validates schema PASS
  • rest success payload validates schema PASS

Fingerprint sha256:0b3576e210148c8f1f92d41b017b6c8242c6e176afe5be57fcfe3c4d64b312be

Input schema sha256:97971021efedaa4afb209527dac6588001297cc275dab4ba4455835f12f88d22 · Output schema sha256:e5ccf52f5c11af738d12bc43526a84c9ccc03979e7207b6b020f69b02bf9d291 · 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
triangle-solver
Engine
triangle-solver
Engine build
2026-10-29
Evidence core
2026-10-29T08:55:15.563Z
Rendered
2026-10-29T17:04:55.748Z
Last reviewed
—

Assumptions

  • Euclidean plane
  • Not spherical trigonometry
  • Not Pythagorean-only

Limitations

  • One consistent length unit, area in its square; angles in degrees. a/b/c opposite A/B/C. Euclidean only.
  • Strict decimal inputs normalize to binary64. SSS inequality classification uses exact dyadic predicates; no fixed absolute length epsilon.
  • SSA no solution -> INVALID_INPUT; one/two solutions retain complete ordered solutions array, acute B before supplementary B. Primary top-level fields mirror solutions[0].
  • Nonzero inputs and reported positive values must be finite normal binary64; rescale on NUMERIC_RANGE. Degree-to-radian values must also remain normal.
  • NUMERIC_CONDITION rejects unresolved triangles: for non-exact SSA sine, abs(a^2-h^2)/(a^2+h^2)<=1e-8 with h=b*sin(A); exact degree30/90/150 sine identities bypass that guard.
  • For derived sides (SAS/ASA/AAS/SSA), each rounded triangle-inequality gap must exceed64*Number.EPSILON times the shortest side. SSS raw-side classification uses exact dyadic inequalities without that guard.
  • Near flat/SSA tangent cases are sensitive to input rounding. Relative5e-10 arithmetic verification against independent high precision is not an input perturbation or universal geometric accuracy guarantee.
  • Browser interaction local; shared URLs and REST/MCP send parameters to the server.

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.