Reachability through independently powered POPs and external paths.
Defined workload classes, destinations, state requirements, and recovery objectives.
Power boundaries, run-time assumptions, failover tests, and measured recovery.
Begin diligence ↗ Resilience architecture
WHEN THE CAMPUS LOSES POWER, THE COMPUTE MODEL HAS TO KEEP MOVING.
Private Fiber is engineering the physical paths, powered POPs, interconnection, and distributed capacity required to give qualified workloads somewhere credible to go.
01 DIFFERENT FAILURE DOMAINS
CONTINUITY STARTS OUTSIDE THE CAMPUS FENCE.
Backup generation protects a facility only while fuel, switching, cooling, and internal systems remain available. Our model adds independently located POPs, physically diverse glass, regional exits, and distributed compute beyond that same power and civil domain.
This is not a claim that every workload is portable. It is an engineered option for the services that can be prioritized, replicated, redirected, or re-created elsewhere.
FAILURE DOMAINNETWORK CONTROLCOMPUTE CONTROLDILIGENCE EVIDENCE
Physically separated entrances, rings, splice plans, and route ownership.
Alternate destination remains reachable without the failed corridor.
GIS alignment, shared-risk review, OTDR records, and route acceptance.
ROADM strategy, span budgets, amplification, protection, and telemetry.
Placement responds to available path and capacity—not an abstract cloud region.
Loss budgets, margins, latency, convergence, and restoration behavior.
Onward paths to distinct markets and interconnection environments.
Priority services redirect beyond the affected geography.
Destination diversity, measured paths, capacity reservation, and exercises.
02 ACTIVE CONTINUITY POINTS
THE POP BECOMES PART OF THE COMPUTE SYSTEM.
Traditional carrier architecture ends at a demarcation. This model continues through interconnection and into distributed accelerated capacity. A POP can support local aggregation, telemetry, policy enforcement, service continuity, and a direct optical path toward the Tea Kettle core.
The differentiation is operational: network state and compute availability can be evaluated together. The fabric is designed around the real-world location of power, paths, machines, and failure—not only logical regions.
ACAMPUSPrimary capacity
⇄BPOWERED POPSOutside failure domain
⇄CLOCAL COMPUTEQualified services
⇄DTEA KETTLERegional accelerated core
03 PUBLIC ARCHITECTURE VIEWS
RESILIENCE MUST BE PHYSICAL.
These views communicate topology and intent. Exact alignments, capacities, controls, and customer configurations remain in controlled diligence.
01 / PATH · Concentric diversityANIMATED · SCHEMATIC
No shared corridor disguised as redundancy.
Separate arcs are designed to land in distinct failure domains.
02 / CORE · Optical coreANIMATED · SCHEMATIC
Control the path through the optical layer.
ROADM and amplification strategy are engineered against actual distance and loss.
03 / REGION · Regional fabricANIMATED · SCHEMATIC
Extend continuity beyond one metro.
The full-build view connects campus, POP, distributed capacity, and core markets.
Deployed neighborhood fiber and current construction activity establish field capability. The fully funded POC is validating the integrated continuity and compute model. The regional view represents the system being built, not a claim of statewide production operation today.
CONTROLLED DILIGENCETEST THE MODEL AGAINST
Open continuity diligence ↗