math.geometry.coordinate

Three distinct suites: educational examples on the calculator page, this legacy regression count (21/21 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.8.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.8.0. CVP 1.0.0-proposed. 309/309 golden · 4/4 CVP boundary · 12/12 invalid · 3/3 property · 12/12 metamorphic · 4/4 cross-interface · 2/2 cross-calculator · 6/6 CVP contract. digest 93ec4c6ee843.

• Golden (oracle-backed) 309 / 309
• CVP boundary 4 / 4
• Invalid input 12 / 12
• Property 3 / 3
• Metamorphic 12 / 12
• Cross-interface 4 / 4
• Cross-calculator 2 / 2
• CVP contract 6 / 6
• 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
• schema rejects incomplete input PASS
• rest success payload validates schema PASS

Fingerprint sha256:d5ca3a00e08a53342cc1ece5de47942a4c14a29ee2f0c848370d343f79915709

Input schema sha256:8a0b05edc90fb1554e40f419f673bda169a974a384d202a6730fe9144b7ff3fb · Output schema sha256:59a9cf25492f0eabea30ab712d6596b164c822688268c474a7552e2e6b9e15c5 · 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

coordinate-geometry

Engine

coordinate-geometry

Engine build

2026-10-29

Evidence core

2026-10-29T08:55:15.563Z

Rendered

2026-10-29T17:04:55.751Z

Last reviewed

—

Assumptions

• Euclidean plane
• Not 3-D / spherical

Limitations

• Cartesian R²; all coordinates use one consistent length unit; angle outputs include radians and degrees.
• Strict decimal inputs; matching x0/px and y0/py aliases; unknown fields reject. Omitted mode defaults distance. Discovery entry URLs lock their documented operation.
• Exact dyadic predicates classify the supplied normalized binary64 values; decimal-to-binary rounding still affects nearly parallel lines and input-sensitive intersections. No absolute geometric epsilon or near-integer snapping.
• Nonzero inputs and published numeric fields must be finite normal binary64; NUMERIC_RANGE requires translation/rescaling. Mathematical zero is retained, never a clamp.
• Coincident defining points reject INVALID_INPUT for slope and all line operations; distance zero and midpoint remain valid. Vertical slope/intercept are null.
• Line coefficients use exact integer gcd only for exact safe integers; otherwise a common power-of-two normalization and canonical sign. Standard equations are floating presentations, not exact symbolic identities.
• Intersections of infinite lines (not segments): parallel distinct => empty, coincident => coincident, each with x/y null; other intersections return one point.
• Undirected principal line angle is atan2(abs cross, abs dot) in [0,90] degrees. Exact predicates determine status; a non-perpendicular angle can round to90 degrees.
• Full binary64 output without near-zero clamping. Typical well-conditioned scalar error budget relative2e-12; ill-conditioned inputs require their own sensitivity analysis. No positional bound is claimed for perturbed inputs.