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.interpolation-node-identity. Calculation version 1.1.2. CVP 1.0.0-proposed. 24/24 golden · 8/8 CVP boundary · 13/13 invalid · 1/1 property · 8/8 cross-interface · 1/1 cross-calculator · 6/6 CVP contract. digest 0ad8422e1d6d.

• Golden (oracle-backed) 24 / 24
• CVP boundary 8 / 8
• Invalid input 13 / 13
• Property 1 / 1
• Cross-interface 8 / 8
• 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:433b6855c8c95f7cf2fa5b590c33ba6985e1c3795d2c7e51d3098d835e9b4c3a

Input schema sha256:47638a1132ce1e27dbfc3a88f900e6b23d674080e44fd77a46e0ad5776f8e278 · Output schema sha256:b09dffb496fd66004646820713ef422de51de37dfc9ff570b820ce2a7a1e987a · 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-07

Evidence core

2026-10-07T11:14:03.363Z

Rendered

2026-10-07T11:15:58.891Z

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