Home Developers Capabilities Conic section

CVP verified calculation capability

Conic section Calculation Capability

Axis-aligned ellipse, parabola, and hyperbola. Discovery /ellipse, /parabola, /hyperbola. Not the circle-only page, not coordinate geometry, not CAS.

Math · Geometry Capability ID math.geometry.conic version 1.1.0 CVP VERIFIED CURRENT Core

Model

Ellipse

Modes: ellipse · oval · parabola · parabolic · hyperbola · hyperbolic

Inputs / Outputs

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

SymbolQuantityUnit policyRole
alengthconsistent length unitinput / output
blengthconsistent length unitinput / output
plengthconsistent length unitinput / output
orientation——input / output
clengthconsistent length unitoutput
escalar ratio—output
areaareasquare of input unitoutput
perimeterlengthsame length unitoutput
focus_xlengthconsistent length unitoutput
focus_ylengthconsistent length unitoutput
directrix——output
asymptote_slopescalar ratio—output
equation——output
circle——output
majorlengthconsistent length unitoutput
minorlengthconsistent length unitoutput
four_plengthconsistent length unitoutput
directrix_valuelengthconsistent length unitoutput
directrix_axis——output
perimeter_method——output
foci——output

Trusted Math contract

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

FieldDeclaration
numeric_domainreal
exactnessfloat64
algorithmscaled axis-aligned conic identities; factored normalized ellipse eccentricity; scaled Ramanujan I perimeter; hypot hyperbola focus
valid_domainstrict decimal number/string input; positive a,b or nonzero signed p; nonzero inputs and reported numeric outputs must be finite normal binary64 (abs >= 2^-1022); exact zero for circular eccentricity/focus coordinates only
singularity_policyVALUE_MUST_BE_POSITIVE for nonpositive semiaxes; INVALID_INPUT for p=0; NUMERIC_UNDERFLOW for textual nonzero converted to zero; NUMERIC_RANGE on nonzero subnormal or overflowing output; rescale units
branch_policynot applicable — real principal value only
tolerancetype: relative; value: 2e-12; note: Against independent high-precision values of the published formula, relative to normalized binary64 inputs; exact zero/discrete fields separately checked. No universal perimeter model-error bound is claimed.
convergencenot applicable — non-iterative
conditioningEllipse c and e near a=b are input-sensitive. Binary64 rounding can make distinct decimal axes equal; circle classification is exact equality after normalization. Eccentricity may round to 1 for very thin ellipses or near-degenerate hyperbolas. Perimeter is Ramanujan I approximation; numeric tolerance measures that formula, not error against exact arclength.
roundingieee754_round_ties_to_even
overflowieee754_nonfinite_or_coded_error
reproducibilitydeterministic algorithm + Capability@Version
independent_oraclecvp:math.geometry.conic O2 Python mpmath high precision / private reference fixtures
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.

ellipse a=5 b=4 → c=3, e=0.6

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 · 4/4 declared partitions (ellipse, parabola, hyperbola, invalid-domain)
Calculation version
1.1.0
Verification
9/10 calculation tests · 3/3 legacy golden · 2/2 legacy boundary · 4/5 legacy property
Production surface contract
5/5
Versions
Calculation 1.1.0 · CVP protocol 1.0.0-proposed · Evidence 2026-10-29.math-uuce-fields-v1
Verification revision
2026-10-29.math-uuce-fields-v1 · 3/3 property · digest e1dc06efeffb
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
185/185 golden · 2/2 CVP boundary · 49/49 invalid · 3/3 property · 4/4 metamorphic · 4/4 cross-interface · 2/2 cross-calculator · 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.1.0 (workspace artifacts agree)
Review-policy tier
Candidate — catalog token candidate; supplemental; not CVP status
This calculator CURRENT · Public schema 1.1.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/conic-section' \
  -H 'Content-Type: application/json' \
  -d '{"inputs":{"mode":"ellipse","a":5,"b":4},"calculation_version":"1.1.0"}'

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

Full REST contract: REST API docs.

Tool id
conic-section
Engine
conic-section
REST
POST /api/v1/calc/conic-section
MCP
execute_calculation with capability_id: "math.geometry.conic"
Agent input schema
Canonical (MCP / Agent)
Output schema
JSON Schema (latest)
Versioned input schema
Immutable pin (1.1.0)
Versioned output schema
Immutable pin (1.1.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.geometry.conic"},"_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.0) when the result must stay reproducible.

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