Product evidence
Version, provenance, support, lifecycle, security, dependencies, performance, and license.
Partners / Technology
Qualify components inside a declared configuration
Technology partners can contribute compute, network, security, data, AI, observability, and developer components. Partnership does not make every product eligible for every region or mission.
Partner pathway
Partner pathwaycurrent lifecycle
Region-specificfuture availability
Evidencebefore commitment
Capability set
Capability scope
Deployment
Cloud, sovereign region, dedicated, enclave, edge, and disconnected operating modes.
Integration
Identity, policy, telemetry, data, keys, upgrades, recovery, and evidence interfaces.
Qualification
Test plan, findings, remediation, approved configuration, region eligibility, and revalidation.
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.