ORBIT · Decisions under link loss

The link drops. The record doesn't.

Autonomous platforms keep deciding when nobody can reach them. ORBIT gives every decision a record: sealed on board and chained with a local sequence, reconciled on the ground when the link returns, and verified later by someone who did not write the code.

Stage 2 · autonomy and quorumSimulation-validated
On boardSeal and chain only
SignersOn the ground
01 The question

What did the machine decide when no human was in contact?

A spacecraft behind the Earth, a rover out of view of every orbiter, an uncrewed vehicle out of range: each keeps acting on its own. When something goes wrong, an inquiry needs to know which model, on which inputs, under which rules and which authority, made each decision, and whether anything was edited afterwards.

Bit-exact replay is not available: modern models are not bit-exact across runs, and keeping raw sensor data is unaffordable. So ORBIT records rather than replays. The record is the evidence: commitments to the model, the inputs and the policy in force, signed in order, with every gap in contact recorded as a fact rather than hidden.

That record is attribution and configuration evidence for the people who need it after the fact: the mission board, the insurer and the investigator.

02 A link-loss window

Connected. Degraded. Lost. Reconnect.

Simulated · link state01 / 04
01 · CONNECTED

Decisions stream to the ground as they happen.

Each decision is recorded in a sealed segment carrying commitments to the model, the inputs, the policy in force and the authority chain. With the link up, segments reach the ground and are receipted within moments.

  • Link state: connected
  • The local sequence increments with every decision
02 · DEGRADED

Some get through. The rest wait, already sealed.

As the link weakens, deliveries fail or stall. The platform does not wait for the ground: each segment is sealed and chained locally, so nothing depends on whether a packet arrived.

03 · LOST

No link. Keep deciding. Keep the chain.

Out of contact, the platform keeps acting. Every decision extends the local chain: each sealed segment points at the previous one and carries the next sequence number. A missing or reordered segment breaks the sequence and shows.

  • On board: hash commitments and sealing only, never a stateful signer.
04 · RECONNECT

Reconcile, cosign, verify.

When contact returns, the buffered chain flows to the ground in one burst. The ground checks the sequence is gap-free, mints the receipts, records the reconciliation with a reference back to the local chain, and has the result cosigned: by an independent party for classified assets, or publicly anchored for civil ones.

03 Four link states

The link state is part of the evidence.

CONNECTED

Live delivery

Segments reach the ground and are receipted as decisions are made; the ground ledger and the local chain agree.

DEGRADED

Partial delivery

Deliveries stall or fail; recorder segments queue locally, already sealed and sequenced.

LOST

Local only

No contact; the chain grows on board and the gap itself is recorded as evidence.

RECONNECT

Reconcile burst

Buffered segments flow down, are checked for gaps, receipted on the ground, reconciled and cosigned.

Gaps are first-class. Absence of evidence is never evidence of absence, so a coverage statement records what was observed, what was not, and the gap intervals.
04 The decision record

Eight things recorded for every decision.

ElementRecordsAnswers
Model commitmentHash of the model, software and configuration identityWhich model decided?
Input commitmentsMerkle roots over the ring-buffered sensor and input segmentsOn what evidence?
Policy in forceThe policy in force at the moment of decisionUnder which rules?
Authority chainWho delegated the authority, down to the platformOn whose authority?
Platform attestationReference to the platform's attestation of its own stateWas the platform what it claimed?
Link stateconnected · degraded · lost · reconnectingCould a human have intervened?
Local sequenceMonotonic counter, chained to the previous recordIs anything missing or reordered?
ReconciliationPointer to the ground reconciliation that absorbed this recordWhen and how did it reach the ground?
05 Anchoring that fits classified work

No public blockchain inside an enclave.

CLASSIFIED / DISCONNECTED

Seal plus deferred cosign

Nothing leaves a classified enclave for a public chain; at most a hash crosses a cross-domain guard. The record is a self-contained seal, cosigned later by an inspector general, a legal officer or an allied node.

UNCLASSIFIED CIVIL

Public anchoring allowed

For civil assets the reconciled root can be anchored publicly, giving a timestamp nobody in the programme can move.

WHO WITNESSES

An organisational choice

The witness set is a negotiation between organisations, not a protocol parameter. The cosigners are named per programme before any deployment.

06 Quorum

Authority, released by a quorum written down before the pass.

Stage 2 adds quorum release: authority to act is released only when enough separate approvers sign, each under their own key. Tiers run from one approver to three plus dual control, with a reject veto.

The same evidence protects against the threat most systems ignore: a compromised or coerced ground operator. The approver chain in every decision record shows exactly who released which authority, and a cosigner outside the chain of command can attest to it later.

ItemState
Quorum receipts under separate approver keysSimulation-validated
Link-loss simulator: connected, degraded, lost, reconnectSimulation-validated
Signed mode changes kept on board (Stage 3 container)Reviewed internally · founder-approved
Use on a real platformPlanning
07 Questions

On autonomous decisions.

Does ORBIT tell the platform what to do?

No. ORBIT builds no targeting or autonomy algorithms and does no weapons work. It records what the system decided, under which model, rules and authority.

Can the operator edit the record after the event?

Sealed on board, receipted on the ground, verified by someone who did not write the code, and cosigned by a party outside the operator's control. An edit breaks the chain or the cosignature and shows.

What does the platform need to run?

Very little: hash commitments over recorder segments and local sealing. Signing and cosigning happen on the ground; no stateful signer goes on board.

Has this run on a real platform?

Not yet. Stage 2 is validated in simulation. The Stage 3 hosted run will carry signed mode changes through a real blackout; it is planned.

Out of contact is not out of the record.

Sealed on board, reconciled on the ground, cosigned by someone outside the chain of command.

Keep it for decadesSpace link trust