Execution

Layer 5 delivers what Layer 6 chose and Layer 4 permitted. It decides neither.

The boundary most often crossed in practice. A delivery gate becomes an authorization by default.

An initiative passes every stage gate the PMO defined. Requirements were signed off, testing completed, the business declared itself ready. The system goes live. It has no classification record, no named Business Accountable Executive and no Layer 4 deployment authorization, because every gate tested delivery readiness and none tested governance readiness.

Nobody bypassed a control. The controls were all in the other layer, and the gate never asked for them.

This is the Layer 5 seam and it is the most common route by which an ungoverned AI system reaches production. Section 5 addresses it by making Layer 4 evidence a gate entry condition rather than a parallel process.

Output 8 closes the loop that most organizations leave open. Layer 6 funds an initiative against a stated benefit. Unless Layer 5 measures whether the benefit arrived, Layer 6 decides the next investment on the same evidence it used for the last one.

Three allocations carry the weight of this layer.

L5-01 and L5-05 carry the framework’s two enforcement points. Funding and the production gate are the points every initiative must pass through, which makes them where decisions taken elsewhere become enforceable. Three entry conditions sit here for that reason: the traceable strategic outcome and the capability decision record at funding, and the Layer 4 authorization plus the model purpose statement at the gate. Each fixes a decision in another layer whose own trigger is weak.

L5-05 and L5-14 are different decisions and must not collapse. L5-05 asks whether the system works. L5-14 asks whether the organization is ready to use it. Both sit near the same point in a delivery cycle and both produce a readiness record, and where they merge it is adoption readiness that disappears, because the gate carrying a mandatory entry condition survives. The result is a system deployed correctly into a business that cannot use it.

The production readiness gate has a Layer 4 entry condition. This single row is what stops the delivery pipeline from becoming an authorization bypass. The PMO still decides delivery readiness, which is its competence. It cannot decide governance readiness, and it cannot proceed without evidence that someone who could has.

Pilot transition is a named decision, not a drift. Pilots become production systems by usage rather than by decision, and while a system is called a pilot the classification and authorization requirements never trigger. Making the transition a decision with a named owner is what stops indefinite pilot status from functioning as a governance exemption. The threshold that defines it is recorded as an open item.

Work reallocation is a decision with a mandatory consultation, not an efficiency outcome. The Business Owner decides, because it is a business process decision and the process is theirs. The Head of Talent is consulted without exception, because the consequence is a workforce one and the deciding role has no reason to surface it.

The decision is distinct from the autonomous action authorization at Layer 4. That one asks what an agent may do. This one asks what a person will stop doing, which affects a different set of people and carries a different accountability.

Individual reallocations sit here. Where they cross the reallocation materiality threshold published at Layer 4, the cumulative position is assessed at Layer 6. The structure mirrors aggregate exposure: distributed decisions, central assessment of what they amount to.

Workforce AI tooling is authorized, not assumed. Individual adoption of general-purpose AI tools happens whether or not anyone authorizes it. The decision exists so a data boundary is stated somewhere, and so the absence of an authorization is a detectable condition rather than an unexamined one.

Scoping. Organization-level artifacts are required from the stated maturity level. System-level artifacts are required per AI system, model, interface or event according to the condition stated. Artifacts in bold are part of the Level 2 minimum. See the minimum viable set document for what this amounts to at small scale.

EU AI Act Article 4 has applied since February 2025 and is independent of the Annex III deferrals.

The pilot register is the artifact this layer is usually missing. Organizations can list their projects and their production systems. The set between the two, running against real data with real users and no governance trigger, is rarely enumerated anywhere.

Delivery velocity, on-time completion and budget variance are excluded. All three measure whether delivery is working, not whether it is governed, and all three belong in portfolio reporting.

Two gaps this crosswalk exposes. No delivery framework gates on governance readiness. COBIT, PMI and ITIL all specify stage gates and all specify them against delivery criteria: requirements complete, testing passed, business ready. None makes an authorization from a governance function a mandatory entry condition. The provision at section 5 is AI9GM’s, and it is the mechanism that closes the seam described at section 2.

No instrument governs the reallocation of work between humans and AI. Focus area 9 names workforce collaboration and productivity. Every instrument in this list addresses training people to work with AI systems. None addresses who decides that a task moves from a person to a system, on what basis, or who is accountable for the workforce consequence.

AI9GM v0.9 allocates it at section 5: Business Owner decides, Head of Talent is consulted without exception, and the cumulative position is assessed at Layer 6 above the reallocation materiality threshold.

The distance between levels 2 and 3 is dominated by one change that costs nothing and is resisted anyway: naming the Business Accountable Executive before the build rather than at go-live. Naming at go-live means the entire build ran without an accountable person, and the name selected is whoever was available rather than whoever should hold it.