Live evidence case / CML-PDRE-001
800V DC: Live Evidence Case A living evidence chain tracking whether 800V DC and SST are becoming operational power architectures for MW-scale AI infrastructure.
Evidence boundary: a single deployment can change the field-evidence assessment. It cannot establish industry adoption or full PDRE validation.
Current evidence state
What the approved records establish now. States separate architecture, validation, field operation, and adoption. No confidence percentage is inferred.
Architecture possibility SUPPORTED
System validation SUPPORTED Source-reported demonstrations; performance claims remain attributed.
Named field deployment OBSERVED — SINGLE INSTANCE
Long operating history UNKNOWN
Multi-entity replication UNKNOWN
Independent third-party validation UNKNOWN
Repeat procurement UNKNOWN
Industry-scale adoption NOT ESTABLISHED
PDRE full validation NO
Decision transition
What changed our assessment? Authorization is separate from execution. Evidence acceptance is separate from canonical readiness.
Before R5_FIELD_DEPLOYED_NOT_ESTABLISHED
Research gap identified Dated, attributable field-operation evidence needed
Human authorization 1 narrow L1 verification authorized No general 800V research authorized.
Bounded verification 4 queries · 9 sources · 1 deep review
Qualifying evidence Named operator · named campus · 10kV AC → SST → 800VDC · commercial operation
Human review Evidence accepted
After R5_ARCHITECTURE_FIELD_DEPLOYMENT_EVIDENCE_ACCEPTED_SINGLE_INSTANCE Canonical readiness remains unchanged pending existing governance.
Still unknown 5 unresolved dimensions preserved
Source provenance
Approved qualifying evidence record. The source is an attributable operator publication, not an independent third-party audit. Performance and efficiency figures were not independently verified.
L1-EV-CML-PDRE-001-FIELD-DEPLOYMENT-001
Chindata Commences Commercial Operation of an SST-Based DC Power System for Hyperscale Data Centers HUMAN REVIEW ACCEPTED · SINGLE INSTANCE
PUBLICATION DATE 2026-07-02
EVENT DATE 2026-07-02
KNOWLEDGE DATE 2026-09-20T10:46:47Z
OPERATIONAL ENVIRONMENT Chindata Sangyuan Cloud Computing Campus near Beijing
ARCHITECTURE 10kV utility AC to 800VDC using an SST-based intelligent DC power system
WHAT IT SUPPORTS One named operator reported commercial operation at one named campus for a materially relevant SST-to-800VDC architecture.
WHAT IT DOES NOT SUPPORT Independent performance validation, operating history, multi-entity replication, application qualification, repeat procurement, industry adoption, or full PDRE validation. Counter-evidence
Non-qualifying records remain visible. Future commercialization or planned deployment bounds the assessment; it is not silently discarded after one qualifying source is found.
PLANNED DEPLOYMENT Vertiv / practical path to 800 VDC Commercialization, customer pilots, and deployment ramp were described as future activity. Rejected as field-operation evidence for this question.
UNDER DEVELOPMENT Siemens + Reinhausen / DC power solutions The record described technology under development for future deployment. Rejected as field-operation evidence for this question.
BOUNDARY What these records mean One observed architecture does not establish that related product paths, supplier systems, or industry adoption are field deployed.
Dependency transfer
The bottleneck moves; it does not disappear. The alternative path can reduce selected rack-level constraints while creating or elevating new engineering and qualification dependencies.
Old path
MV/LV AC → Transformer → UPS → Rectification → Rack PSU → Low-voltage distribution
Alternative path
MV → SST → 800VDC → Rack / sidecar / conversion layer → Compute
Candidate dependency release
Lower current Copper pressure Distribution density constraint Dependency transfer — not all solved
DC protection Fault isolation Insulation / partial discharge Connectors / busbars SiC / GaN HF magnetics Qualification Thermal integration
Subsystem watch
Readiness is subsystem-specific. Repository-supported states only. UNKNOWN is an intentional result when the approved packet contains no qualifying evidence.
Commercially actionable unknowns
What is still missing? Each link starts scope definition only. It does not automatically authorize research.
UNKNOWN
Operating history Why it matters Initial operation does not establish duration or reliability.
Minimum resolving evidence Dated attributable operating-history and reliability record for the named system.
Verify this gap UNKNOWN
Multi-entity replication Why it matters One operator cannot establish repeatability across entities.
Minimum resolving evidence Attributable field-operation records from additional independent operators.
Verify this gap UNKNOWN
Independent validation Why it matters Operator statements are not third-party performance audits.
Minimum resolving evidence Independent validation against defined performance and safety requirements.
Verify this gap UNKNOWN
Repeat procurement Why it matters A first project does not establish repeated buying behavior.
Minimum resolving evidence Dated attributable repeat order or additional commissioned procurement.
Verify this gap NOT ESTABLISHED
Industry-scale adoption Why it matters Single deployment and standards activity are not broad adoption.
Minimum resolving evidence Multi-entity field evidence with repeat deployment across a defined market boundary.
Verify this gap Customer application
Does this evidence apply to your system? Public evidence can establish a market boundary. Your architecture, qualification requirements, suppliers, and decision deadline determine applicability.
Keep the distinctions visible
FACT ≠ CLAIM ≠ EVIDENCE ≠ DECISION
AUTHORIZATION ≠ EXECUTION
SINGLE DEPLOYMENT ≠ INDUSTRY ADOPTION