OrbitGate
Open sourceDeterministic checks for orbital and satellite claims, with every verdict signed. Sweeping all 14,560 single-bit modifications of a signed certificate, 0 verified afterwards.
What it checks
- Orbital mechanics consistency of the stated state vector
- Manoeuvre feasibility against remaining delta-v and attitude bounds
- Conservation constraints, which a single flipped bit will usually violate
- Fail-closed, so an uncheckable command is refused rather than passed through
What it does not check
- The sweep measures certificate integrity, not spacecraft memory. It cannot prevent a bit flip: single-event upsets are a hardware and shielding problem. What it shows is that a signed verdict cannot be altered afterwards.
- It says nothing about whether the verdict inside the certificate was correct. A signed wrong answer is still signed.
- The repository's claim benchmark is not quoted here. It does not yet agree with its own expected decisions often enough to publish, and a figure we would not stand behind is worse than no figure.
- Demonstration scope. It is not flight-qualified software and carries no space systems assurance.
Where it sits
DEGA
OrbitGate runs inside DEGA
Deterministic Execution Gate Architecture
Is this physical action allowed to happen?
Sits between a decision and anything that moves hardware, machinery or infrastructure, and asks whether the action is permitted. If that check cannot complete, the action does not happen.
permitblockhold for review
Evidence
Every verdict leaves a record
| Property | Behaviour |
|---|---|
| Determinism | The same input produces the same verdict. A result that does not reproduce is treated as a defect. |
| Signing | Verdicts are Ed25519 signed and anchored in a tamper-evident chain. |
| Replay | A sealed pack can be re-run later to detect verification drift. |
| Availability | Fail-closed. If this gate cannot be reached, the result is recorded as unavailable, never as a pass. |
| Independence | A third party can verify a pack without our source code and without contacting us. |
Run it against your own cases
The audit protocol is public. You do not need our permission, our source or our involvement to test a gate and publish what you find.