Home Developers Capabilities Pythagorean theorem

CVP verified calculation capability

Pythagorean theorem Calculation Capability

Right-triangle solve a² + b² = c² for a missing side, plus area and perimeter; verify mode when all three sides given.

Math Capability ID math.pythagorean version 1.1.2 CVP VERIFIED CURRENT Engineering

Model

Theorem

Solve
solve_for = a | b | c
Verify
mode = verify | check

Inputs / Outputs

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

SymbolQuantityUnit policyRole
aleg lengthconsistent length unitinput / output
bleg lengthconsistent length unitinput / output
chypotenuse lengthconsistent length unitinput / output
valuesolved side lengthsame length unitoutput
areaareasquare of input unitoutput
perimeterperimeter lengthsame length unitoutput

Trusted Math contract

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

FieldDeclaration
numeric_domainreal
exactnessfloat64
algorithmc = √(a²+b²) and inverse solves on the same identity
valid_domainpositive side lengths as published
singularity_policyINVALID_INPUT when a triangle inequality / positivity fails
branch_policynot applicable — real principal value only
tolerancenot applicable — closed form; capability Evidence owns comparison, no global default
convergencenot applicable — non-iterative
conditioningnot applicable — not a matrix κ product
roundingieee754_round_ties_to_even
overflowieee754_nonfinite_or_coded_error
reproducibilitydeterministic algorithm + Capability@Version
independent_oracleEvidence 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.

a=3, b=4 → c=5

Open this example in the calculator

Trust

CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance. 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 · Engineering assurance· View Manifest · CVP overview · Specification
Assurance
Engineering
Declared partition coverage
PASS · 5/5 declared partitions (solve-c, solve-b, solve-a, verify, invalid-domain)
Calculation version
1.1.2
Verification
16/16 calculation tests · 6/6 legacy golden · 10/10 legacy boundary
Production surface contract
6/6
Versions
Calculation 1.1.2 · CVP protocol 1.0.0-proposed · Evidence 2026-09-16.sources-no-wolfram
Verification revision
2026-09-16.sources-no-wolfram · 4/4 property · digest 4847c211167f
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.
CVP suite
6/6 golden · 10/10 CVP boundary · 11/11 invalid · 4/4 property · 2/2 metamorphic · 2/2 round-trip · 1/1 cross-interface · 6/6 CVP contract
Supplemental domain review
Not performed
Named expert review
Not performed
Version lock
Supported (409 VERSION_MISMATCH)
Artifact consistency
Build verified · 1.1.2 (workspace artifacts agree)
Review-policy tier
Engine tested — catalog token engine_tested; supplemental; not CVP status
This calculator CURRENT · Public schema 1.1.2 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 6/6.

curl -sS -X POST 'https://www.calculatorx.com/api/v1/calc/pythagorean' \
  -H 'Content-Type: application/json' \
  -d '{"inputs":{"a":3,"b":4,"solve_for":"c"},"calculation_version":"1.1.2"}'

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

Full REST contract: REST API docs.

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

References

Human-readable sources plus CVP reference evidence classes.

Sources

Derived identities

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.pythagorean"},"_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.1.2) when the result must stay reproducible.

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