Home Developers Capabilities Euclidean remainder / modular inverse

CVP verified calculation capability

Euclidean remainder / modular inverse Calculation Capability

Integer remainder a = q·m + r with 0 ≤ r < |m|, plus modular inverse via extended Euclidean. Not JavaScript truncated %. Not GCF.

Math Capability ID math.modulo version 1.1.1 CVP VERIFIED STALE Core

Model

Identity

Modes: remainder · inverse

Inputs / Outputs

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

SymbolQuantityUnitRole
aDividend / residue—input / output
modulusNon-zero modulus—input / output
remainder——output
quotient——output
identity——output
convention——output
algorithm——output
inverse——output
gcd——output

Trusted Math contract

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

FieldDeclaration
numeric_domaininteger
exactnessexact
algorithmEuclidean remainder; inverse via extended Euclidean
valid_domainintegers; modulus ≠ 0; inverse needs gcd(a,m)=1 and |m|≥2
singularity_policyDIVISION_BY_ZERO when modulus = 0; NOT_INVERTIBLE when gcd ≠ 1
branch_policynot applicable — integer domain
tolerancenot applicable — exact integer identity
convergencenot applicable — non-iterative Euclidean / combinatorial
conditioningnot applicable — not a floating matrix
roundingnone — BigInt / exact integer
overflowcoded error or stringified BigInt when exceeding JSON number
reproducibilitydeterministic exact integer + Capability@Version
independent_oraclecvp:math.modulo 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.

a=-17 modulus=5 → remainder=3

Open this example in the calculator

Trust

CVP VERIFIED · production STALE · 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 · production STALE · 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 (remainder, inverse, invalid-domain)
Calculation version
1.1.1
Verification
13/13 calculation tests · 3/3 legacy golden · 4/4 legacy boundary · 6/6 legacy property
Production surface contract
6/6
Versions
Calculation 1.1.1 · CVP protocol 1.0.0-proposed · Evidence 2026-10-07.signed-bigint-publication
Verification revision
2026-10-07.signed-bigint-publication · 2/2 property · digest b805f6620fef
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
8/8 golden · 5/5 CVP boundary · 8/8 invalid · 2/2 property · 4/4 cross-interface · 1/1 cross-calculator · 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.1 (workspace artifacts agree)
Review-policy tier
Engine tested — catalog token engine_tested; supplemental; not CVP status
STALE · Build schema 1.1.1 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 ✓

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/modulo' \
  -H 'Content-Type: application/json' \
  -d '{"inputs":{"a":17,"modulus":5},"calculation_version":"1.1.1"}'

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

Full REST contract: REST API docs.

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

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

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