ExecutionGate
Open sourceFail-closed permission boundary for downstream use. The reference implementation of the DAX layer.
What it checks
- Permission before execution
- Fail-closed on unavailable checks
- Recorded basis for every permit or block
What it does not check
- It is not a safety-instrumented system and does not carry a safety integrity level.
Where it sits
DAX
ExecutionGate runs inside DAX
Deterministic Action Execution
Is this physical action allowed to happen?
DAX places a permission boundary between a decision and an action that affects hardware, machinery, infrastructure or another physical system. It is fail-closed: if the check cannot complete, the action does not proceed.
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.