Home Developers Capabilities Laplace transform

CVP verified calculation capability

Laplace transform Calculation Capability

Unilateral Laplace table of causal elementary pairs: exp, sin, cos, step, ramp, t^n, damped sin/cos. Evaluate F(s) or f(t). Discovery /inverse-laplace. Not DFT, not Z, not Bromwich, not CAS.

Math · Transform Capability ID math.transform.laplace version 1.0.0 CVP VERIFIED CURRENT Core

Model

Definition

Modes: laplace · inverse

Inputs / Outputs

Canonical symbols for this capability. Agent schemas remain the contract.

SymbolQuantityUnitRole
f——input / output
s——input / output
t——input / output
a——input / output
omega——input / output
n——input / output
value——output
algorithm——output
roc——output

Trusted Math contract

Inspectable numeric contract for this Capability@Version. Not a rewrite of the engine.

FieldDeclaration
numeric_domaincomplex
exactnessexact
algorithmunilateral table of causal pairs (exp/sin/cos/step/ramp/t^n)
valid_domainpublished causal table; real s in the ROC as documented
singularity_policyINVALID_INPUT / INVALID_MODE off the table (not Bromwich)
branch_policycausal unilateral; not two-sided, not a CAS inverse
tolerancenot applicable — table identity
convergencenot applicable — table lookup
conditioningnot applicable — table
roundingnone — rational / symbolic-table coefficients as published
overflowcoded error off the table
reproducibilitydeterministic table + Capability@Version
independent_oraclecvp:math.transform.laplace O2 / Evidence published cases
golden_vectorsEvidence golden + boundary + property (and published_reference_case when listed)

Assumptions / Validity

Declared scope for this capability. Do not use it outside this domain.

Assumptions

Example

One numerical check. The calculator page holds worked steps and FAQ.

mode=laplace f=exp a=-1 s=1 → 0.5

Open this example in the calculator

Trust

CVP VERIFIED · CVP protocol 1.0.0-proposed · Core assurance · all published modes. Computational verification is defined by CVP. Supplemental domain review (internal) and named expert review are defined by the Review policy and do not by themselves determine CVP conformance.

CVP
CVP VERIFIED · CVP protocol 1.0.0-proposed · Core assurance · all published modes· View Manifest · CVP overview · Specification
Verified scope
all published modes
Assurance
Core
Declared partition coverage
PASS · 3/3 declared partitions (laplace, inverse, invalid-domain)
Calculation version
1.0.0
Verification
10/10 calculation tests · 3/3 legacy golden · 2/2 legacy boundary · 5/5 legacy property
Production surface contract
5/5
Versions
Calculation 1.0.0 · CVP protocol 1.0.0-proposed · Evidence 2026-09-22.special-transform-cvp
Verification revision
2026-09-22.special-transform-cvp · 1/1 property · digest cc9b93cb51b3
Reference
O1 model · O2 expected_values · O2 numerical_behavior
Interfaces
PASS · UI (SSR) / REST / MCP
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.
CVP suite
9/9 golden · 2/2 CVP boundary · 4/4 invalid · 1/1 property · 3/3 cross-interface · 5/5 CVP contract
Supplemental domain review
Not performed
Named expert review
Not performed
Version lock
Supported (409 VERSION_MISMATCH)
Artifact consistency
Build verified · 1.0.0 (workspace artifacts agree)
Review-policy tier
Engine tested — catalog token engine_tested; supplemental; not CVP status
This calculator CURRENT · Public schema 1.0.0 matches · Semantic contract ✓ · Production attested · Public/cache ✓ · Origin ✓

Call this capability

Human page, REST, and MCP share the same engine and calculation_version. Build verified hashes workspace artifacts only. After deploy, attest:production GETs canonical URLs twice — the public/cached view an Agent actually hits, and origin — including every /capabilities/{id} HTML page. Public Capability HTML version must match catalog before production attestation passes. Live Trust rows above fetch /.well-known/calculatorx-production-attestation.json and the output schema const. Build hashes: release integrity. That proves currently published page / engine / schema / evidence / MCP agree — not that a historical version is independently immutable. Reference Calculation Standard — Production surface contract 5/5.

curl -sS -X POST 'https://www.calculatorx.com/api/v1/calc/laplace-transform' \
  -H 'Content-Type: application/json' \
  -d '{"inputs":{"mode":"laplace","f":"exp","a":-1,"s":1},"calculation_version":"1.0.0"}'

POST /api/v1/calc/laplace-transform. This is a POST calculate endpoint — do not GET it.

Full REST contract: REST API docs.

Tool id
laplace-transform
Engine
laplace-transform
REST
POST /api/v1/calc/laplace-transform
MCP
execute_calculation with capability_id: "math.transform.laplace"
Agent input schema
Canonical (MCP / Agent)
Output schema
JSON Schema (latest)
Versioned input schema
Immutable pin (1.0.0)
Versioned output schema
Immutable pin (1.0.0)

References

Human-readable sources plus CVP reference evidence classes.

Sources

Reference evidence classes: O1 model · O2 expected_values · O2 numerical_behavior

Try with an agent

Inspect, then execute. Same engine as REST and the human calculator.

curl -sS -X POST 'https://www.calculatorx.com/mcp' \
  -H 'Content-Type: application/json' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: tools/call' \
  -H 'Mcp-Name: inspect_capability' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"inspect_capability","arguments":{"capability_id":"math.transform.laplace"},"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientInfo":{"name":"calculatorx-docs-example","version":"1.0.0"},"io.modelcontextprotocol/clientCapabilities":{}}}}'

Pin calculation_version (1.0.0) when the result must stay reproducible.

Inspect the trust tier and required assurance level before execution. Full protocol notes: MCP docs.