What This Stage Covers
The pilot exits to production. AI Inventory entry created. AI BoM populated (per Chapter 6 canonical structure). AI Use Policy compliance verified. AI Risk Register entry filed against the canonical 9-class taxonomy. Evidence Register operationalised per system × per class. Decision traceability instrumented in production. For Tier 3+ capabilities: Delegation-Authority Register filed; materiality calibration completed.
Exit Gate — Required Evidence
G3
AI Inventory entry created; AI BoM completed; vendor DPA in force; AI Risk Register entry made with canonical class assignment; named system owner; decision traceability operationalised.
Editorial Framing
Deploy is the stage where evidence becomes operational. The AI Inventory becomes the regulator-facing surface. The AI BoM becomes the procurement-facing surface. The Risk Register becomes the watchlist. The Evidence Register becomes the proof corpus. Evidence framework (Defensibility Element 3) is most active here.
Q1 Productivity is the return category most visibly produced at Deploy — the use case starts saving time at production scale. The other three categories continue to accumulate.
Required Artefacts
- AI Inventory entry
- AI BoM
- AI Use Policy compliance verification
- Risk Register entry (canonical class)
- Evidence Register entries (per system × per class)
- Decision traceability instrumentation in production
- Named system owner assignment
- For Tier 3+: Delegation-Authority Register entry + materiality calibration
Common Failure Modes
- AI Inventory entry deferred — the capability operates in production without governance visibility
- AI BoM skipped — procurement evidence incomplete
- Risk Register entry filed without canonical class assignment
- Evidence Register not operationalised — Risk Register exists but no proof corpus
- Decision traceability instrumentation deferred to Operate