FIRE + VAULT · CP-08

Control AI Systems

Bound what an AI system can reach, and keep a stop that the model cannot argue with.

  • CP-08
  • Path and asset together
Control Blueprint CP-08, Control AI Systems: an isometric diagram of an AI agent whose route to production systems is physically severed, beside a sealed offline vault of model weights
01At a glance

What this Blueprint does.

Agent, model and tooling access with a physical hard stop

What it does

Bound what an AI system can reach, and keep a stop that the model cannot argue with.

Where it fits

Agent, model and tooling access with a physical hard stop

Who uses it

Financial services, Defence, Critical infrastructure, Healthcare, Public sector, Technology

CP-08 topology

How CP-08 controls AI systems.

A FIRE+VAULT pattern. The AI runtime holds no standing route to production data or tooling. Reach exists only as a validated, time-bound window, and a single Execute signal severs it at the physical layer regardless of how the model or its orchestration behaves.

Grounded in the EU AI Act Art. 14-15, NIST AI RMF MANAGE-2.3, ISO/IEC 42001 A.6 and IEC 62443-3-3 SR 5.1.

Z0

AI runtime and agents

Models, orchestration

AI runtime and agents zone

Models, orchestration and autonomous agents acting at machine speed

FV-Firebreak module iconFirebreakFV-Validate module iconValidateFV-Relay module iconRelay

Severed by default. Opens as a validated, time-bound window for a named purpose.

Z1

Tooling and action layer

APIs, automation

Tooling and action layer zone

APIs, automation and the systems an agent is allowed to change

FV-Isolate module iconIsolateFV-Execute module iconExecuteFV-Lock module iconLock

Separated at hardware level. One Execute signal is the hard stop, enforced physically.

Z2

Production data and systems

Records, shares

Production data and systems zone

Records, shares and operational systems the work depends on

OSS

Crown jewels · detail callout

Model and training asset vault

Weights, curated training sets and the record of every window held offline, outside anything an agent or its operator can reach.

Modules & symbols

FV-Firebreak module iconFirebreakPhysical sever
FV-Validate module iconValidateIntegrity check
FV-Relay module iconRelayTime-bound path
FV-Isolate module iconIsolateZone boundary
FV-Execute module iconExecuteApproved action
FV-Lock module iconLockNamed access
ConduitEnforced module path
┄┄┄
Crown jewelsOffline · detail callout
03How it reads end to end

The Blueprint in full.

Firebreak holds the route between the AI system and production systems severed by default, so an agent inherits no standing path. Validate checks each request against identity, purpose and authority before anything opens. Relay grants the reach as a time-bound window rather than a permanent credential. Isolate keeps the model runtime, the data it processes and the tooling it can act on in separate zones. Execute is the hard stop: one signal severs the path at the physical layer, whether or not the software responds. Lock, Archive, Unlink and Transfer hold the models and training material behind identity controls, preserve the record of every window, remove always-on dependencies and govern what data moves in or out.

04Sector relevance

Where CP-08 applies.

Financial servicesDefenceCritical infrastructureHealthcarePublic sectorTechnology
Mark Fermor
David Bailey
Kenny Phipps
Online Now
Concierge

Build control around your environment

Talk to our team about composing this Blueprint for your estate.

Takes about 2 minutes. No account needed.

Free2 minsNo sign-up