01 / MEANING

Physical location is only one layer of control

Moving compute into orbit may change exposure to terrestrial power grids, physical access and regional disruption. It does not, by itself, answer who owns the hardware, controls the software, holds the encryption keys, authorises commands, chooses the ground stations, accesses the data or bears legal responsibility.

A sovereign orbital architecture must connect technical controls to an identified legal and operational authority. The system should make clear where data originates, where it is processed, which jurisdictions apply, who may decrypt it, how actions are recorded and how a lawful operator can intervene.

02 / CONTROL MODEL

Seven questions every sovereign workload must answer

01Origin

Which sensor, institution, machine or person created the data, and under what authority?

02Processing

Which code and hardware transform it, and can those components be independently inspected?

03Keys

Who generates, stores, rotates, recovers and revokes encryption and signing keys?

04Jurisdiction

Which entity, spacecraft registry, ground location, customer and destination market create legal obligations?

05Commands

Who may alter workloads, software, routing, retention or safe-mode state?

06Evidence

Can the system prove the source, policy, software state and authorised path behind each result?

07Remedy

How can errors, abuse, unlawful access or compromised components be stopped, investigated and corrected?

03 / AUTONOMY

Autonomy must remain inside policy

Orbital systems cannot depend on continuous human contact. A five-step autonomy pipeline can preserve control during disconnected operation: sense the current state; verify the source and integrity of observations; evaluate policy and mission constraints; execute only an authorised bounded action; and record the decision and evidence for later reconciliation.

Each step requires failure handling. Uncertain observations should reduce authority, not increase it. Expired policy should stop privileged action. Disagreement between sensors should trigger a safe state. Reconnection should produce an auditable comparison between expected and actual behaviour.

SENSE→VERIFY→AUTHORISE→EXECUTE→PROVE
04 / VERIFIABLE PROVENANCE

The Layer-1 records accountability; it does not replace it

The Proof of Pulse Layer-1 is being designed as institutional coordination infrastructure. In an orbital data-centre system, it may record hardware identity, software attestations, authorised policies, data lineage, workload commitments, state transitions and settlement receipts.

A ledger cannot make a false sensor truthful, a compromised key safe or an unlawful policy legitimate. Hardware roots of trust, independent observation, permissioned identity, human governance and jurisdiction-specific controls remain necessary. The ledger’s role is to make authorised state and provenance more difficult to alter silently.

05 / INSTITUTIONAL PROPOSITION

Sovereign compute + sovereign data + verifiable provenance

For a government or regulated institution, the proposition is stronger than “a data centre in space.” It is a controlled architecture in which selected workloads can be processed outside terrestrial facilities while data authority, key ownership, jurisdiction, policy and audit remain explicit.

Proof of Pulse is developing this proposition across an India-led orbital programme and an Estonia-led Layer-1 programme, with the legal-entity separation described in the public group map. Cross-border technical collaboration must be supported by written service, IP, data-processing and operational agreements.

The next proof is not a slogan. It is a reference mission that demonstrates one bounded workload from authenticated origin through policy-controlled orbital processing to a verifiable result, including failure, interruption and recovery evidence.