math.geometry.triangle

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.

STALE · Build schema 1.1.0 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.metric-scope-v3. Calculation version 1.0.1. CVP 1.0.0-proposed. 168/168 golden · 2/2 CVP boundary · 75/75 invalid · 3/3 property · 2/2 metamorphic · 2/2 cross-interface · 1/1 cross-calculator · 5/5 CVP contract. digest f8a41ad5ec9e.

• Golden (oracle-backed) 168 / 168
• CVP boundary 2 / 2
• Invalid input 75 / 75
• Property 3 / 3
• Metamorphic 2 / 2
• 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:92f71490f4337d704ef8f1e8a50fb60b9fa919fd02dcce45ce51413c27adb5c4

Input schema sha256:66dc73bf41d6dfbc2229490f5ca5d4cd76b5780437cdaf463e1e20667a372e55 · Output schema sha256:2c54b6f4f22a12a6b246c17ed7411671f48a9a8b27c5be443638dcbe5dd06f99 · 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.

Tool

triangle-solver

Engine

triangle-solver

Engine build

2026-10-20

Evidence core

2026-10-20T02:41:15.137Z

Rendered

2026-10-29T07:58:56.676Z

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.