Skip to content
GridNinja
Request Audit

GridNinja evidence

Evidence for safe, usable, auditable capacity

GridNinja evidence pages connect a precise capacity claim to its maturity, environment, measurement window, sample, version, method, uncertainty, negative cases, reproduction steps, and review boundary. The first release is deliberately synthetic and sanitized. It demonstrates the proposed proof contract without implying customer, pilot, production, certification, or independent-validation results.

Publication boundary

Evidence earns visibility

Artifacts are downloadable from stable versioned paths, but the technical pages remain noindex until named ownership, review, release signing, and publication approval are complete. The candidate release contains no customer topology, raw telemetry, identifiers, setpoints, protective thresholds, credentials, network paths, commercial terms, or solver internals.

Resource index

Stable questions, scoped answers, explicit limits

Evidence protocol

Publication gated

Virtual Capacity Proof Test v1.0

The Virtual Capacity Proof Test is a synthetic, methods-first protocol for checking whether a capacity-acceptance system refuses unprovable actions and preserves evidence. It covers stale telemetry, topology mismatch, reserve floors, thermal and water constraints, SLA limits, rebound, and connection loss. Passing a synthetic test demonstrates protocol behavior only; it is not a customer, pilot, or production result.

Inspect resource

Evidence object

Publication gated

Sample runtime-assurance decision trace

A runtime assurance trace records the candidate action, evidence state, constraints checked, binding limit, decision, permitted repair, and rollback posture. This sample uses synthetic data to show the shape of an inspectable allow / repair / reject / no-proof record. It does not represent a customer site, field test, pilot, or production control event.

Inspect resource

Evidence object

Publication gated

Accepted-headroom ledger specification

An accepted-headroom ledger records only the capacity that passed the declared evidence and dispatch-envelope checks for a specific site context and time window. Each entry links the accepted quantity to its request, binding constraint, remaining margin, evidence versions, authority boundary, and expiry conditions. It prevents modeled or claimed headroom from being silently treated as durable sellable MW.

Inspect resource

Evidence specification

Publication gated

Load Passport specification

A Load Passport is a versioned contract describing what an AI workload requires and what flexibility it may safely offer. It expresses power and timing needs, placement constraints, SLA class, thermal or recovery dependencies, permitted actions, evidence requirements, and authority boundaries. It lets capacity decisions evaluate a workload as an operational contract rather than an anonymous demand curve.

Inspect resource

Related operator resources

Continue the proof path

Capacity Audit

Bring the operator question before the capacity claim

A Capacity Audit maps constrained infrastructure to proof-adjusted opportunities, refusal conditions, and a read-only Shadow Mode plan.

Request Capacity Audit