Verified calculation capability

Battery runtime with temperature Calculation Capability

Constant-load battery runtime with a generic cold-derating temperature capacity factor about 25 °C (extends Battery Runtime base: watts load-side / amps battery-side). Planning model — not chemistry. · Electrical · Battery

Capability ID electrical.battery.runtime_temp · version 1.2.1

Open calculator REST API MCP Evidence Evidence JSON CVP Manifest Review policy

Model

Temperature factor (default cold-only)

Temperature factor (default cold-only): f_T = clamp(1 + k_T·min(T−25, 0), 0.1, 1)
Runtime (watts, load-side): t = (Ah·f_T·V·DoD·η) / P
Runtime (amps, battery-side): t = (Ah·f_T·DoD) / I_battery

Inputs / Outputs

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

Symbol	Quantity	Unit	Role
`t_h`	Estimated runtime (hours) at T_C	—	output
`t_d`	Estimated runtime (days = t_h/24)	—	output
`E_Wh`	Usable energy in Wh after temperature factor. Watts: Ah_eff·V·DoD·η. Amps: Ah_eff·V·DoD.	—	output
`temp_factor`	Temperature capacity factor f_T (same as temperature.capacity_factor)	—	output
`T`	Echo of input temperature (°C)	°C	output
`k_T`	Planning coefficient used (/°C); default 0.006 — not manufacturer validated	—	output
`capacity_Ah_eff`	Ah × f_T after temperature derating	—	output
`temperature`	—	—	output

Assumptions / Validity

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

Assumptions

Default: cold-only linear derating about 25 °C; T≥25 °C → f_T=1 (no high-temp bonus).
Clamp is a numerical safeguard, not an operating-temperature envelope.
Default k_T=0.006 is a planning default (parameter_validated=false).
Constant load; not Peukert / chemistry Arrhenius / manufacturer curve.
Amps mode I_A is battery-side; η does not enter t_h.

Example

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

10 Ah · 12 V · 20 W · T=0 °C · k_T=0.006 → f_T=0.85 · t=5.1 h (−0.9 h vs 25 °C)

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 · 6/6 declared partitions (watts, amps, generic-cold, custom-symmetric, clamped-regime, invalid-domain)
Calculation version: 1.2.1
Verification: 31/31 calculation tests · 5/5 legacy golden · 10/10 legacy boundary · 16/16 legacy property
Production surface contract: 4/4
Versions: Calculation 1.2.1 · CVP protocol 1.0.0-proposed · Evidence 2026-09-11.xcal-meta-derived
Verification revision: 2026-09-11.xcal-meta-derived · 16/16 property · digest 742a9a7e3a3b
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: 4/4 golden · 8/8 CVP boundary · 5/5 invalid · 16/16 property · 3/3 metamorphic · 2/2 cross-interface · 2/2 cross-calculator · 4/4 CVP contract
Supplemental domain review: Internal · Pass · electrical-engineer · CalculatorX electrical review · 2026-08-12
Named expert review: Not performed
Version lock: Supported (409 VERSION_MISMATCH)
Artifact consistency: Build verified · 1.2.1 (workspace artifacts agree)
Review-policy tier: Internally reviewed — catalog token internally_reviewed; supplemental; not CVP status

This calculator CURRENT · Public schema 1.2.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 4/4.

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

Operations

Declared calculation modes for this capability.

watts
amps

References

Human-readable sources plus CVP reference evidence classes.

Sources

Victron Lithium Battery Smart — Operation (capacity vs temperature example) — Capacity vs temperature (product example)
Victron SmartShunt — temperature capacity compensation note — Temperature compensation engineering simplification
Trojan Battery — temperature effects FAQ — Temperature and capacity / life
CalculatorX Battery Runtime capability — Constant-load watts/amps model (1.2+)

Reference evidence classes: O1 model · O2 expected_values · O2 numerical_behavior

Try with an agent

Inspect this capability via same-origin MCP, then call execute_calculation.

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.runtime_temp"}}}'

Inspect the trust tier and required assurance level before execution. Pin calculation_version (1.2.1) when reproducibility matters. Full protocol notes: MCP docs.