Home Developers Capabilities Conformity decision rule

CVP verified calculation capability

Conformity decision rule Calculation Capability

Binary ILAC G8-style decision on a measured y: simple acceptance (w=0) or guarded acceptance (LSL+w ≤ y ≤ USL−w). The guard-band zone is fail, not conditional. Not JCGM 106 risk, not TUR, and not GB-only.

Engineering · Conformity Capability ID engineering.conformity.decision_rule version 1.0.1 CVP VERIFIED CURRENT Engineering

Model

Simple

Inputs / Outputs

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

SymbolQuantityUnitRole
yMeasured value—input / output
lslLower specification limit—input / output
uslUpper specification limit—input / output
rulesimple—input / output
wGuard-band width when rule=guarded—input / output
UAlready-expanded U used as w when rule=guarded and w is omitted—input
decision——output
accept_lsl——output
accept_usl——output

Assumptions / Validity

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

Assumptions

Not supported

Example

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

y=6 lsl=0 usl=12 rule=simple → pass

Open this example in the calculator

Trust

CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance · Simple and guarded acceptance of y against lsl and usl, + O3 mpmath tabulated decision limits.. 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 · Simple and guarded acceptance of y against lsl and usl, + O3 mpmath tabulated decision limits.· View Manifest · CVP overview · Specification
Verified scope
Simple and guarded acceptance of y against lsl and usl, + O3 mpmath tabulated decision limits.
Assurance
Engineering
Declared partition coverage
PASS · 7/7 declared partitions (alias, upper, guarded, fail, edge, pass, invalid-domain)
Deferred
Not consumer risk and not an ILAC G8 guard-band width design.
Calculation version
1.0.1
Verification
11/11 calculation tests · 1/1 legacy golden · 6/6 legacy boundary · 4/4 legacy property
Production surface contract
6/6
Versions
Calculation 1.0.1 · CVP protocol 1.0.0-proposed · Evidence 2026-09-25.o2-o3
Verification revision
2026-09-25.o2-o3 · 1/1 property · digest 2681fed0d989
Reference
O1 model · O3 expected_values · O3 numerical_behavior · O2 expected_values · O2 numerical_behavior
Numerical scope
O2: simple and guarded acceptance limits vs a separate-module identity (≤2 ULP). Not consumer risk. ≤2 ULP vs O3 applies only to the published tabulated decision-rule vectors. Not consumer risk.
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
4/4 golden · 6/6 CVP boundary · 5/5 invalid · 1/1 property · 1/1 metamorphic · 8/8 O3 · 2/2 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.0.1 (workspace artifacts agree)
Review-policy tier
Engine tested — catalog token engine_tested; supplemental; not CVP status
This calculator CURRENT · Public schema 1.0.1 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/decision-rule' \
  -H 'Content-Type: application/json' \
  -d '{"inputs":{"y":6,"lsl":0,"usl":12},"calculation_version":"1.0.1"}'

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

Full REST contract: REST API docs.

Tool id
decision-rule
Engine
decision-rule
REST
POST /api/v1/calc/decision-rule
MCP
execute_calculation with capability_id: "engineering.conformity.decision_rule"
Agent input schema
Canonical (MCP / Agent)
Output schema
JSON Schema (latest)
Versioned input schema
Immutable pin (1.0.1)
Versioned output schema
Immutable pin (1.0.1)

References

Human-readable sources plus CVP reference evidence classes.

Sources

Reference evidence classes: O1 model · O3 expected_values · O3 numerical_behavior · 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":"engineering.conformity.decision_rule"},"_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.1) when the result must stay reproducible.

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