01Origin
Identify data source, owner, purpose and permitted use before ingress.
→02Classify
Apply sensitivity, residency, retention and mission policy.
→03Place
Select terrestrial, edge or orbital execution by policy and workload.
→04Control
Bind jurisdiction, key ownership and operator permissions.
→05Prove
Record authorised state transitions and provenance on PoP L1.
→06Egress
Release only approved results through controlled, auditable paths.
CONTROL PLANE
INSTITUTIONAL QUESTION
POP DESIGN RESPONSE
JURISDICTION
Which law controls the payload, operator and data at each stage?
Policy-bound placement, deployment profiles and recorded jurisdiction state.
KEY OWNERSHIP
Who can decrypt, authorise or revoke access?
Customer-controlled keys, hardware roots of trust and separation of duties.
PROVENANCE
Can origin, transformation and custody be independently verified?
Signed events and deterministic settlement receipts anchored to PoP L1.
AUDIT & REMEDY
Can an institution reconstruct events and enforce policy after failure?
Immutable receipts, selective disclosure, revocation and evidence export.
HOSTED PAYLOAD PATHLower first-flight dependence
A staged path from hosted payloads to dedicated orbital nodes is intended to reduce early spacecraft and launch dependence. Economics remain modelled until quoted and tested.
PHYSICAL AIR-GAP PATHCustody designed into hardware
Space vault tiers explore physical isolation, customer-owned encryption and controlled downlink—not a generic cloud region moved to orbit.
L1 PROVENANCE PATHInfrastructure coordinates infrastructure
The ledger is positioned as the trust and settlement plane for custody events, resource allocation and machine-to-machine commitments.
SOVEREIGN DEPLOYMENT PATHPolicy is part of the product
Jurisdiction, identity, permissions and operational control become deployable architecture—not a compliance appendix added later.