Extend
Monitor condition, maintain, repair, replace modules, upgrade, and retain spares.
Energy & Materials / Circularity
Design repair and end-of-life before deployment
A resilient compute region needs component and battery maintenance, repair, upgrade, reuse, recycling, hazardous-material handling, data sanitization, and closure pathways tied to accountable partners.
Lifecycle design
Lifecycle designcurrent lifecycle
Region-specificfuture availability
Evidencebefore commitment
Capability set
Capability scope
Reuse
Requalify equipment for lower-demand or edge roles only after security, safety, and performance review.
Recover
Use documented recycling and material-recovery channels with custody and downstream evidence.
Close
Plan sanitization, removal, remediation, community obligations, records, and financial responsibility.
Evidence matrix
What must be true before deployment
| Decision | Required record |
|---|---|
| Eligibility | Customer, mission, workload, data, jurisdiction, identity, device, and export conditions |
| Availability | Region, environment, service, configuration, quantity, delivery window, support, and exceptions |
| Control | Operator, network, keys, access, data movement, change, incident, recovery, and customer duties |
| Evidence | Owner, source, test or assessment, findings, limitations, approval, issue date, expiry, and revalidation |
Next decision
Convert the requirement into a bounded brief
Define the mission, jurisdiction, workload, sensitivity, environment, capacity, connectivity, continuity, timing, and evidence priorities without submitting restricted information.