AIRLOCK
Control room
requester
loading…
Console
Posture
0 changes on record
0
Refused right now
Proven, and not permitted to proceed
0
Ready to decide
A certificate holds and policy agrees
0
Awaiting a second pair of eyes
One signature short of moving
0
People not written to
Held back by a sealed or rejected change
£0.00
Money not moved
Above ceiling, or otherwise stopped
0
Records not touched
The work the system did by not doing it
Held at the gate
0 waiting

Nothing is holding for a human.

Why the gate is refusing
by reason

Nothing is currently sealed.

Decided
0 applied · 0 rejected

No change has passed through the airlock yet.

Ledger integrity
checking…

Re-hashing the sealed history.

Head

Keep it somewhere we cannot reach. Verify offline with npm run verify:ledger.

Change freezes
Declared
  • Comms blast
    21:00–08:00
  • Infrastructure mutation
    16:00–23:59, 00:00–23:59, 00:00–08:00

Erasure, money and access are never frozen. A freeze that blocks a statutory obligation trades a legal problem for an operational one.

What flows through
0 total

Nothing has been opened yet.

Green classes must prove they can be undone. Amber ones cannot be undone at all, and must prove their exact scope instead.

Break-glass
off

Switched off. Two switches are required — the class must permit it in policy, and the deployment must set AIRLOCK_BREAK_GLASS=1.

Used, all time
0

Break-glass does not open the gate — it cannot mint a grant. It records that a named human went around a sealed door, permanently. People do this anyway; a control plane that pretends otherwise only ensures there is no record of it.