Platform  /  DEGA

DEGA

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.

Deterministic Execution Gate Architecture · AU provisional 2026905506

What it returns

permitblockhold for review

Categorical, not probabilistic. Where a lane cannot decide, it says so explicitly rather than returning a low-confidence answer that reads like a decision.

What it does

  • Interposes a permission decision before execution, not after it.
  • Fails closed. An unavailable check is recorded as unavailable, never as a pass.
  • Records the permission decision and its basis before the action runs.
  • Supports a human authorisation step where automation is inappropriate.

What it does not do

  • It is not a safety-instrumented system and does not replace one.
  • It does not certify that an action is physically safe.
  • It governs permission, not the engineering of the system it protects.
Enterprise concerns

The questions this layer gets asked in procurement

ConcernWhy it decides the deployment
Fail-closed behaviourThe single most important property. Verified explicitly.
Authorisation modelWho may override, and what record that leaves.
Latency budgetA permission boundary in a control path has a hard ceiling.
Blast radiusWhat happens to in-flight actions when the boundary is unavailable.
Implementations

What runs inside DEGA

Each of these is a real implementation with code behind it. Status is labelled honestly, and nothing is listed as coming soon.

ExecutionGate

Open source

Fail-closed permission boundary for downstream use. The reference implementation of the DEGA layer.

OrbitGate

Open source

Deterministic checks for orbital and satellite claims, with every verdict signed. Sweeping all 14,560 single-bit modifications of a signed certificate, 0 verified afterwards.

FlightGate

Research

Early work on refusing a commanded control action whose stated preconditions do not hold: outside the declared envelope, or contradicted by the sensor state the command cites to justify itself. Scoped, not built.

GridGate

Interactive lab

Refuses a dispatch instruction that breaches a stated limit. Across 20,000 synthetic instructions it blocked 4,947 of 4,947 breaches and refused 0 of 14,059 valid instructions, while stopping 994 legitimate instructions whose limit set had expired.

See it against your own workflow

A pilot runs in shadow mode. It controls no production decision, and the acceptance criteria are agreed before it starts.

Next · See it work Eco Control Tower