GridGate
Interactive labRefuses 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.
What it checks
- Dispatch instruction against thermal, voltage and stability limits as stated
- Which limit set was in force at the time, so a decision can be reconstructed
- Authority to issue that instruction for that asset
- Fail-closed when a limit cannot be read
What it does not check
- It does not manage, balance or optimise load. Dispatch and market operation belong to the operator's own systems. It only refuses an instruction that breaches a limit those systems already define.
- It does not compute the limits and cannot tell you whether the stated limit was the right one. Blocking a breach of a wrong limit is still blocking a breach.
- Fail-closed has a price. In the run, every legitimate instruction whose limit set had expired was stopped. That is the trade an operator chooses, not a detection, and it is reported separately for that reason.
- Laboratory scope. Synthetic instructions against a synthetic limit set, not operator data, not for use in any live control system, and not a substitute for protection schemes.
Where it sits
DEGA
GridGate 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.