Gate

What it does

The gate is applied to the receiving team before any system is chosen. It treats deployment as multiplicative rather than additive: a capable system landing in a team that cannot absorb it multiplies harm instead of adding capability. Ten checks are observable on the floor without new software; four red lines stop the deployment outright.

When it is used

First. Everything else in the sequence assumes the gate has been passed.

The record that supplies it

• 12
  Before the Machine

  Stage 1 · GateApplied series 0, the paper numbered zero because it comes first. Every other document says how to deploy well; this one says when not to deploy at all. The Readiness Gate.

  2026-07-19 · Record 12 · doi:10.5281/zenodo.21445040

The worksheet itself, lifted intact from that record, is stage 1 of The Instrument Deck.

Papers that bear on it

• The Cultural Safety Case: Why a licence to deploy is a licence to amplify — Every regime assesses the capability of the system; none assesses the culture of the organisation deploying it. Deployment risk is their product, and four organisational predictions are registered.
• What the Signature Certifies: Four asks for the revision of DCB0129 and DCB0160 — NHS England is revising DCB0129 and DCB0160 for the first time since 2018. Four asks for that revision, accepting the review's own findings on AI governance, monitoring and compliance.
• The Tenant's Record: Who the system serves when the system is not yours — Who the system serves when the system is not yours. Adult social care went from paper to platform in four years; the record of a person's care is now held by a tenant of somebody else's software.
• The 24-Hour Team — Core paper 1 of 3. Managing round-the-clock care as two teams joined by a handover produces a family of predictable failures; the unit is one organism, and its vitals can be read.