DCII Project
GridNinja's DCII project would validate safe, usable, auditable virtual capacity inside AI data centers without asking operators to trust hidden actuation or black-box autonomy.
Read-only first. Public claims stay measured; site evidence stays protected.
Project summary
The project starts in Shadow Mode, maps site telemetry and topology into declared policy, runs candidate capacity actions through deterministic checks and runtime assurance, and exports proof artifacts that operators, utilities, partners, and reviewers can inspect.
Deployment validation funding
GridNinja is seeking deployment validation funding to support a read-only proof project inside constrained AI data center environments. Funding would support site scoping, telemetry integration, proof artifact development, scenario validation, stakeholder evidence packets, and commercial readiness work.
Funding ask
$500k to $5M per project
Aligned to current public Elemental DCII program language for deployment projects that can be integrated into data center environments. The final scope should be calibrated to site access, integration depth, and stakeholder review needs.
Use of funds
The project scope is organized around reviewer-ready artifacts, read-only integration, and conservative validation outputs.
Site scoping and security review
Read-only boundary, stakeholder map, data-access plan, and no-write deployment posture.
Read-only telemetry integration
Connector manifest across power, cooling, workload, reserve, bridge-power, and topology sources.
Capacity Waterfall and Load Passport
Proof-adjusted virtual capacity artifacts with binding constraints and no-proof gaps visible.
Runtime assurance and replay validation
Allow / repair / reject / no-proof traces, proof roots, and repeatable scenario replay package.
Utility / EMC evidence packet
Planning-facing dispatch envelope, ramp limits, caveats, and exception table.
Operator review package
CISO/operator review notes, evidence tables, and commercial readiness summary.
Authority boundary
GridNinja can propose and verify candidate actions, but live authority stays inside declared site policy, deterministic checks, runtime assurance, and operator review.
Before / after proof
Illustrative sample. The right side is not a guarantee; it shows the evidence shape after constraints, policy, and no-proof gaps are applied.
Before proof
18.4 MW claimed
capacity_basis
nominal headroom
constraint_status
unknown active limits
evidence
no accepted proof root
risk
static buffers and no-proof gaps hidden
After proof
5.8 MW proof-adjusted
capacity_basis
accepted-headroom ledger
constraint_status
known binding constraints
evidence
proof_root 8f4c...91a
risk
no-proof gaps visible and owner-assigned
58% proof-adjusted evidence view, 42% claimed headroom context.
AI Data Center Load Passport
The Load Passport binds proof-adjusted capacity, ramp limits, reserve floors, telemetry trust, no-proof gaps, and accepted-headroom evidence into one inspectable record.
Evidence outputs
These are the proof objects the DCII project should validate in read-only Shadow Mode before any deeper control or dispatch posture is considered.
Technical data
Telemetry completeness, constraint map, replay traces, RTA outcomes.
Operational data
Operator review time, no-proof gaps, policy exceptions, workload and cooling constraints.
Commercial data
Proof-adjusted MW, accepted-headroom ledger, design-partner conversion criteria.
Impact data
Grid-readiness posture, dispatch envelope, local reliability support potential.
Operators, hyperscalers, investors
A site-specific capacity identity that summarizes proof-adjusted virtual capacity, binding constraints, freshness posture, and declared operating policy.
Illustrative sample · evidence chain completeExecutives, operators, reviewers
A transparent reduction from nominal headroom to safe, usable, auditable capacity after electrical, reserve, thermal, workload, and telemetry checks.
Illustrative sample · evidence chain completeOperators, auditors, fleet teams
A time-indexed record of accepted capacity states, rejected actions, no-proof intervals, and the proof root behind each decision.
Illustrative sample · evidence chain completeFacilities, BESS/UPS partners
A resilience-first view of UPS, BESS, and bridge-power margins so flexibility does not spend emergency posture silently.
Operators, CISOs, program owners
A remediation list for missing telemetry, incomplete topology, stale policy, or weak evidence that prevents safe approval.
Utilities, EMCs, partners
A planning-facing summary of flexible MW, ramp limits, reconnection envelope, confidence posture, and exceptions.
Reviewer fit
GridNinja's DCII posture is to produce auditable proof around power, cooling, water, and local reliability constraints before any deeper control conversation.
GridNinja ties virtual capacity to reserve floors, bridge power, UPS/BESS posture, and ramp envelopes so software proof supports infrastructure deployment rather than replacing it.
Cooling and water intervals are treated as binding constraints inside the Capacity Waterfall, not as sustainability claims or generic optimization wins.
The project produces the evidence layer needed before operators, utilities, or infrastructure partners trust flexible MW from constrained AI sites.
Local and community benefits
Public
Project scope, read-only boundary, artifact types, source notes, methodology summary, and non-confidential findings.
Private / gated
Site topology, security-sensitive telemetry, customer data, exact operating limits, and reviewer-specific evidence packets.
Milestones
Each milestone is designed to produce technical, operational, commercial, or stakeholder evidence without hiding authority transfer inside the project.
Security and site scoping
Months 1-2
Read-only boundary, telemetry map, role model, and proof schema.
Shadow integration
Months 2-4
Topology model, baseline telemetry confidence, and first constraint map.
Proof artifact v1
Months 4-7
Capacity Waterfall, Load Passport, reserve-floor report, and no-proof trace.
Scenario validation
Months 7-10
Electrical, reserve, cooling, workload, and telemetry-confidence replay results.
Stakeholder evidence packets
Months 10-13
Operator review package, utility packet, and partner validation summary.
Commercial readiness
Months 13-18
Deployment learnings, risk register, design-partner criteria, and final memo.
Deployment ladder
The DCII path is a validation program: Shadow Mode first, advisory review next, and bounded autonomy only after the evidence chain supports it.
Generate recommendations, safety outcomes, and proof artifacts without write credentials or actuation.
unlock: read-only tape
Operators review action bundles, no-proof gaps, and Load Passport outputs with real decision context.
unlock: operator review
Enable a narrow actuator set only inside declared dispatch envelopes and runtime assurance checks.
unlock: dispatch envelope
Add coordinated multi-asset control as evidence and confidence accumulate.
unlock: evidence gate
Risk register
The page should show reviewers that GridNinja understands operator trust, infrastructure fit, and impact-claim discipline.
Lead with read-only Shadow Mode, no write credentials, no command VLAN, and explicit authority boundaries.
Tie outputs to reserve floors, bridge power, cooling constraints, ramp envelopes, and utility evidence packets.
Publish measured scenarios and methodology only; do not guarantee emissions, water, or avoided-overbuild outcomes.
Label sample data clearly and show artifact structures that match what a live Capacity Audit would produce.
Source notes
Current public DCII program context and funding range.
Market context for data center electricity demand growth.
Reliability context for large computational loads.
Large-load flexibility framework context.
Market signal for data center demand-response participation, not a GridNinja partnership claim.
Related operator resources
Capacity Audit
Request the memo to discuss scope, evidence outputs, deployment boundary, and stakeholder review path.
