CVP verified calculation capability

Linear Battery Aging Calculation Capability

Linear capacity fade from independent cycle and calendar aging. Default k_cycle=0.0002/cycle and k_cal=0.02/year are illustrative.

Electrical · Battery Capability ID electrical.battery.aging version 1.0.2 CVP VERIFIED CURRENT Engineering

Model

State of health

State of health: SOH = max(0, 1 − k_cycle·N − k_cal·t)
Remaining capacity: C = C0·SOH

Inputs / Outputs

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

Symbol	Quantity	Unit	Role
`C0_Ah`	Beginning-of-life capacity in Ah	—	input
`N_cycles`	Cycle count matching the calibration of k_cycle	—	input
`years`	Calendar aging time in years	—	input
`k_cycle`	Illustrative cycle fade coefficient	—	input
`k_cal`	Illustrative calendar fade coefficient	—	input
`capacity_Ah`	Remaining capacity C = C0·SOH	—	output
`SOH`	SOH = max	—	output
`fade_frac`	Unclamped linear fade exposure k_cycle·N + k_cal·t	—	output

Assumptions / Validity

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

Assumptions

Independent linear cycle + calendar fade
Default k_cycle=0.0002/cycle and k_cal=0.02/year are illustrative
N should match the cycle definition used to calibrate k_cycle; EFC recommended
Not temperature, SOC, DoD, C-rate, or chemistry aware

Not supported

Temperature
SOC
DoD
C-rate
chemistry
Arrhenius fits
√t calendar aging
SEI growth PDE
knee detection

Example

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

3Ah · 500 cycles · 1y · k_cycle=0.0002 · k_cal=0.02 → 2.64Ah, SOH=88%

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 · 4/4 declared partitions (cycle-calendar, cycle-dominant, zero-aging, invalid-domain)
Calculation version: 1.0.2
Verification: 14/14 calculation tests · 3/3 legacy golden · 6/6 legacy boundary · 5/5 legacy property
Production surface contract: 6/6
Versions: Calculation 1.0.2 · CVP protocol 1.0.0-proposed
CVP identity: 5/5 property · digest a53cfab6ba6b
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: 3/3 golden · 6/6 CVP boundary · 5/5 invalid · 5/5 property · 1/1 cross-interface · 4/4 CVP contract
Supplemental domain review: Internal · Pass · electrical-engineer
Named expert review: Not performed
Version lock: Supported (409 VERSION_MISMATCH)
Artifact consistency: Build verified · 1.0.2 (workspace artifacts agree)
Review-policy tier: Internal engineering review — catalog token expert_verified; supplemental; not CVP status

This calculator CURRENT · Public schema 1.0.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/battery-aging' \
  -H 'Content-Type: application/json' \
  -d '{"inputs":{"C0_Ah":3,"N_cycles":500,"years":1},"calculation_version":"1.0.2"}'

{
  "inputs": {
    "C0_Ah": 3,
    "N_cycles": 500,
    "years": 1
  },
  "calculation_version": "1.0.2"
}

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

Full REST contract: REST API docs.

Tool id: battery-aging
Engine: battery-aging
REST: POST /api/v1/calc/battery-aging
MCP: execute_calculation with capability_id: "electrical.battery.aging"
Agent input schema: Canonical (MCP / Agent)
Output schema: JSON Schema (latest)
Versioned input schema: Immutable pin (1.0.2)
Versioned output schema: Immutable pin (1.0.2)

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":"electrical.battery.aging"},"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientInfo":{"name":"calculatorx-docs-example","version":"1.0.0"},"io.modelcontextprotocol/clientCapabilities":{}}}}'

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: execute_calculation' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"execute_calculation","arguments":{"capability_id":"electrical.battery.aging","inputs":{"C0_Ah":3,"N_cycles":500,"years":1},"calculation_version":"1.0.2"},"_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.2) when the result must stay reproducible.

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