Capacity accounting
Proof-adjusted capacity starts where nominal headroom stops
Proof-adjusted data center capacity is the portion of modeled headroom that survives evidence, constraint, and authority checks for a defined operating window. It discounts capacity that depends on stale telemetry, unverified topology, missing reserves, unsupported recovery assumptions, or unapproved control authority. The result is a smaller but defensible quantity for operations, commercial planning, and SLA protection.
Definition
What it is
Proof adjustment is a capacity-accounting method: begin with a physical or modeled ceiling, subtract committed load and policy reserves, then exclude any residual headroom whose dependencies cannot be demonstrated at decision time.
Category boundary
What it is not
It is not a generic derating factor, a single utilization target, or a guaranteed commercial yield. It is a scoped acceptance result whose evidence must travel with the number.
Operational significance
Why operators care
Commercial teams can distinguish forecastable capacity from capacity that facilities teams can actually defend. Operators gain a ledger showing what was accepted, which constraint bound it, what margin remained, and when the evidence expires.
Mechanism
How the decision path works
- Step 01
Establish the physical, contractual, and policy ceilings for the requested window.
- Step 02
Reconcile current commitments and cross-domain reserves.
- Step 03
Test telemetry freshness, topology agreement, recovery behavior, and authority.
- Step 04
Record accepted headroom with its proof dependencies and expiry conditions.
Textual diagram equivalent
Decision flow
Physical ceiling − committed load − policy reserves = modeled headroom; modeled headroom − unproven dependencies = proof-adjusted accepted headroom.
Synthetic waterfall
Visibly scoped example
Synthetic illustrative scenario—not a customer or production result. Modeled headroom is reduced by thermal reserve, storage state-of-charge protection, and an unproven rebound assumption. Only the surviving quantity is entered in the accepted-headroom ledger.
Failure and no-proof cases
- The accounting mixes nameplate, contractual, and dispatchable capacity.
- Reserve deductions are hidden or applied after a commercial claim is made.
- A changing operating window is presented as persistent capacity.
Limitations
- The result is not transferable across sites or operating windows without re-evaluation.
- Capacity remains subject to physical asset availability and operator authority.
- Commercial treatment requires separate contractual and regulatory review.
Evidence and sources
Inspect the basis, not just the answer
Local evidence objects show the GridNinja proof contract. Primary sources provide external standards and risk-management context; they do not validate GridNinja performance.
Related operator resources
Continue the proof path
- Quantify proof-adjusted capacity before you promise flexible MWRequest a Capacity Audit to quantify proof-adjusted safe MW, time-to-power, constraints, evidence gaps, and potential commercial value.
- Review the proof objects before a live reviewInspect the proof artifacts that make virtual capacity reviewable: constraints, decisions, accepted headroom, provenance, replay, and rollback evidence.
- Before you trust another megawatt, ask what proves it.Compare GridNinja's inside-the-fence capacity-acceptance role with DCIM, digital twins, AIOps, and grid flexibility platforms using scoped public sources.
Proof before autonomy
Test the evidence boundary against your capacity question
Start with a Capacity Audit or read-only Shadow Mode discussion. GridNinja does not require control authority to identify where a capacity claim remains unproven.