math.transform.laplace

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.0.4 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-28.metric-scope-v3. Calculation version 1.0.4. CVP 1.0.0-proposed. 147/147 golden · 2/2 CVP boundary · 38/38 invalid · 1/1 property · 2/2 metamorphic · 22/22 cross-interface · 5/5 CVP contract. digest 776df6d89cd1.

• Golden (oracle-backed) 147 / 147
• CVP boundary 2 / 2
• Invalid input 38 / 38
• Property 1 / 1
• Metamorphic 2 / 2
• Cross-interface 22 / 22
• 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 8/8 (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. Raw HTTP REST/JSON-RPC transport rejection 5/5; raw-number source and conflicting pins are transport-only checks, not engine/SSR input-source parity.
• 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:2eb51e1b61aa6686f27fb67be829bf19ee58abedfcc56b75cd10def0903aa2ff

Input schema sha256:da9feb9b7afcce54aaa977fb47597bc047dd04e5c65644745308ec3aa2a334d1 · Output schema sha256:be3575d712c5da262eb08fbe37415d3d1fa8e4fa321898c87f2765d458971974 · 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

laplace-transform

Engine

laplace-transform

Engine build

2026-10-19

Evidence core

2026-10-19T02:32:43.739Z

Rendered

2026-11-10T05:18:42.131Z

Last reviewed

—

Assumptions

• Unilateral, causal t≥0
• Real s in the ROC
• Table of named pairs, not a CAS
• The Result Card includes an engine-linked figure of F(s) on the real ROC (pole at the ROC boundary) or f(t) for t≥0. Same table as REST/MCP.
• Not DFT / FFT
• Not Z-transform
• Not Bromwich / two-sided
• Not a pole-zero Argand of complex s

Limitations

• Unilateral causal elementary table; eight named pairs, power integer0–8; inverse table evaluation at t≥0, step(0)=1 and0^0=1 convention
• Finite real s strictly inside the conservative stated ROC, even degenerate zero sine; real dimensionless parameters, omega in radians per unit t
• Binary64 approximate evaluation,12 significant digits;2e-11 relative fixture tolerance, no uniform accuracy theorem; conditioned near poles/trig zeros
• Coded input underflow, numerical range/phase/quantization refusal; no fabricated nonzero-to-zero success
• Inputs/method/pair aliases must agree; unknown fields rejected
• DFT, Z and unrestricted symbolic/contour inversion are separate models