math.numerical.interpolate

Three distinct suites: educational examples on the calculator page, this legacy regression count (13/13 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-07.lagrange-ordinate-range. Calculation version 1.1.4. CVP 1.0.0-proposed. 39/39 golden · 8/8 CVP boundary · 14/14 invalid · 1/1 property · 10/10 cross-interface · 1/1 cross-calculator · 6/6 CVP contract. digest 3fa94aacf696.

• Golden (oracle-backed) 39 / 39
• CVP boundary 8 / 8
• Invalid input 14 / 14
• Property 1 / 1
• Cross-interface 10 / 10
• Cross-calculator 1 / 1
• 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 2/2 (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 methods
• 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:01d064109de716a96fe43231a834043e7f3b3075c69a59122aeb53575ae10ba6

Input schema sha256:38b53bcc2ea13aed217c8e844d4253ff38df89aa5fd63269a19129b802cfd989 · Output schema sha256:6bd3aea913b681d04ee0bf03002ff3c2908bacd76a7f611a066c5d0958776e6e · 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

numerical-interpolation

Engine

numerical-interpolation

Engine build

2026-10-14

Evidence core

2026-10-14T02:50:33.742Z

Rendered

2026-10-18T01:58:59.875Z

Last reviewed

—

Assumptions

• The Result Card includes an engine-linked figure of the tabulated nodes and P(x) (query marker is published y; n>16 reads points from inputs, not a REST field). Same lerp / Lagrange / natural cubic spline as REST/MCP. Not Akima / PCHIP / regression / CAS.
• Unique x; sorted internally
• Natural spline ends, not clamped
• Not Akima / PCHIP / regression / CAS

Limitations

• Not Akima, PCHIP, clamped spline, or statistical regression
• Linear/spline x outside the table without extrapolate → VALUE_OUT_OF_RANGE
• Lagrange limited to 9 points (degree ≤ 8); linear/spline table ≤ 100
• Not a second interpolator and not CAS