Standard operating procedure · EN6A · Engineering

Production Release

Transactional procedure owned by Release & Deployment in Engineering. 7 numbered steps, 1 of them a person deciding and 6 of them agent work … more

Engineering manual Service view

Procedure code

EN6A

Transactional

Rule versions in force

v3.3 · v3.1 · v4.6 · v1.4

4 governing rules stacked over it

In force since

2025-02-13

Earliest effective date across those rules

Last reviewed

2026-08-08

Latest review date across those rules

Rules approved by

Director, Release Engineering

Rule health

3/4

0 under review · 1 superseded

There is no document register behind this header. The version, the dates and the approver names are read off the governing rules this procedure runs inside, which is the closest thing the estate holds to a document control record. Nobody wrote these procedures. There is no document library behind this page and no Word file anywhere in the estate. Every procedure below is generated from rows this platform already holds: the line and its ordered stations, the owning team and the person accountable for it, the policy items bound to that team, and the governance gates seeded against the function. The steps, the owners, the gates, the approvers, the dwell times and the volumes are read straight off those rows. The sentences that join them together are generated. Read a procedure as the estate describing itself, not as a document somebody signed.

Purpose and scope

What this procedure is for and where it stops

To run production release to one repeatable standard inside Release & Deployment, part of Engineering. more

Entry condition

Runs transactional. Starts when a threshold is crossed.

Exit condition

The unit clears verify. more

In scope

Every unit of production release raised inside Release & Deployment, from the trigger below through to the final step.
6 of the 7 steps, which run without a person present.
1 decision that stops the line until a named person releases it.

Out of scope

Anything outside the envelope set by the owning team. It leaves the line at a gate and becomes the named approver's decision.
Work that belongs to another function. This line hands off to information-technology and does not follow the unit there.
The 5 steps carried on the shared AI GBS spine. They are done for this line but not by this function.

Who owns it

Runs the line

Release Orchestrator

Accountable person

Director, Release Engineering

The end of the escalation path. Above them sits Engineering Chief of Staff for the function.

That team’s remit

Owns release work end to end inside Engineering. more

That remit describes the whole team, not this one procedure, so its counts are larger than the ones on this page.

Autonomy

81% now · ceiling 85%

Canary analysis and automatic revert are faster than any human and run unsupervised. more

The procedure, step by step

7 numbered steps · 1 of them stop for a person

A step is one station on the line. more

No.	Step	Who does it	What happens	System of record	Time on the step	In flight
01	Assemble release GBSgbs	Release Note Agent	Release Note Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.	Group ERP — Materials and Inventory	3.1 hrsstandard 4.0 hrs	7
02	Score risk Agentworkflow	Change Risk Agent	Change Risk Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.	Configuration Management Database	17 minstandard 29 min	14
03	Change board approve HumanpolicyDecision	Director, Release Engineering Releases: Director, Release Engineering	Work stops. Director, Release Engineering reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: Held for a named human when the unit exceeds the release decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Hands off to information-technology	Group ERP — Materials and Inventory	3.8 hrsstandard 8.4 hrs	1
04	Deploy canary GBSgbs	Release Note Agent	Release Note Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.	Group ERP — Materials and Inventory	44 minstandard 1.5 hrs	6
05	Analyze GBSgbs	Release Note Agent	Release Note Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.	Group ERP — Materials and Inventory	1.1 hrsstandard 1.5 hrs	40
06	Promote GBSgbs	Release Note Agent	Release Note Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.	Group ERP — Materials and Inventory	2.6 hrsstandard 3.4 hrs	4
07	Verify GBSgbs	Release Note Agent	Release Note Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.	Group ERP — Materials and Inventory	2.8 hrsstandard 4.8 hrs	32

The swimlane

The same steps, laid out by who is holding the work

Three lanes: a person deciding, an agent working, and the shared services spine. more

Person1 station and 26% of the dwellAgent1 station and 2% of the dwellShared spine5 stations and 72% of the dwell3 crossings between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

Group ERP — Materials and Inventory

Configuration Management Database

Group ERP — Materials and Inventory

Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

Run the procedure

One unit walked along that swimlane on the happy viable agentified path

Press run and a single unit enters at station 01. Each station takes exactly the dwell this platform records for it and is held by whoever the estate says holds it. more

speed

worked clock

00:00

allowance clock

00:00

stations cleared

0/7

the happy path, worked time0 min of 14 hrs

the same run against its allowance0 min of 24 hrs

Human

decides · 1

Agent

does the work · 1

GBS

shared spine · 5

run log

Nothing has happened yet. more

where the worked time goes14 hrs a unit

Person3.8 hrs · 26%Agent17 min · 2%Shared spine10 hrs · 72%3 crossings between lanes

what makes this path viable

The lanes are the recorded lanes. 1 of the 7 stations stop for a person and every one of them still does on this run.
Every one of the 1 decision is still taken by the person who holds it. The happy path is that each one is released first time, not that it is skipped.
The owning team is held to a 85% autonomy ceiling and this run sits at 74% unattended, inside it.
2 systems are attributed across the stations, and 0 of them are connected. Nothing in this run has been watched executing against a real system of record.

what would have to change

One decision, held by Director, Release Engineering. more

stays with a person

03 Change board approve — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.

what this run is, and what it is not

This is a run, not a forecast. more

Happy means nothing goes wrong: no station raises an exception, no gate sends the unit back, no rework loop fires and nothing sits in a queue between stations. more

The second clock is the allowance. more

A decision may be handed to the agent lane only if two things hold … more

The run reads the station rows only. more

What this run does not model: arrival patterns, contention between procedures for the same person, shift patterns, weekends, learning curves, and the cost of anything. more

Run it again, going wrong

The same unit, the same stations, broken the way the estate already records breaking

This is the same unit on the same stations, breaking. more

No break below was chosen. more

One play head, two tracks, the same scale. The clean run stops when it runs out of stations; the other one keeps going.

As written

7 stations, nothing waiting, nothing sent back

0 min of 14 hrs

now Assemble release · Release Note Agent · 3.1 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 26 hrs

now Assemble release · Release Note Agent · 3.1 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen. more

What the two runs say together

4 counted categories land on this procedure. more

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen. more

The separation register records a duty conflict against a sub-function and a named post, not against one procedure. more

Two clocks run. Worked time is the sum of the time the work is actually being done … more

Roles and responsibilities

4 named parties

The responsibility grid is assigned by a rule, not lifted from a chart. more

Party	RACI	Steps	Duty	Escalates to
Release Orchestrator orchestrator	Runs the line	0	Sequences this line, holds its timetable and decides what has to surface to a person. more	Raises to Director, Release Engineering when a unit falls outside the envelope or confidence drops below the floor.
Release Note Agent agent A3% autonomy · ceiling A3% 90% clean · 4% overridden	Responsible	5	Runs the repeatable portion of release & deployment inside the shared transaction spine at spine cost and spine controls.	Escalates to Director, Release Engineering when the unit falls outside the decision envelope or confidence drops below the floor.
Change Risk Agent agent A3% autonomy · ceiling A3% 98% clean · 8% overridden	Responsible	1	Executes the release & deployment step it owns, posts its evidence, and hands the unit to the next stage.	Escalates to Director, Release Engineering when the unit falls outside the decision envelope or confidence drops below the floor.
Director, Release Engineering person	Accountable and responsible	1	Holds 1 decision on this line. more	Accountable to Director, Release Engineering for the decisions held here.

Decision points and escalation

1 places this procedure stops

03 · Change board approve

3.8 hrs

Held for a named human when the unit exceeds the release decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

Director, Release Engineering

Handoffs out of this procedure

Step 03 Change board approve passes the work to information-technology.

The rules this procedure runs inside

4 governing rules

Release & Deployment Decision Envelope

active

EN6-POL-200 · envelope · vv3.3

Agents in this lane may act without a human when the release sits inside the stated value, risk and confidence envelope. more

Approved by Director, Release Engineering · in force 2026-01-23 · reviewed 2026-07-30

Binds Release Note Agent, Change Risk Agent, Deployment Agent, Canary Analysis Agent, Revert Agent

LATAM · US

Release & Deployment Evidence Standard

superseded

EN6-POL-201 · evidence · vv3.1

Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more

Approved by Director, Release Engineering · in force 2025-10-19 · reviewed 2026-07-12

Binds Release Note Agent, Change Risk Agent, Deployment Agent, Canary Analysis Agent, Revert Agent

Global

Release & Deployment Escalation Rule

active

EN6-POL-202 · escalation · vv4.6

Escalation is mandatory when confidence falls below the floor, when two options sit inside the confidence band, or when a break condition on a ratified position fires. more

Approved by Director, Release Engineering · in force 2026-02-26 · reviewed 2026-08-08

Binds Release Note Agent, Change Risk Agent, Deployment Agent, Canary Analysis Agent, Revert Agent

Global

Release & Deployment Autonomy Ceiling

active

EN6-POL-203 · ceiling · vv1.4

The ceiling for this lane is 85 on the platform scale. more

Approved by Director, Release Engineering · in force 2025-02-13 · reviewed 2026-06-17

Binds Release Note Agent, Change Risk Agent, Deployment Agent, Canary Analysis Agent, Revert Agent

Global · EU

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading. more

System	Vendor	Domain	Criticality	Steps	Connection
Group ERP — Materials and Inventory	SAP S/4HANA MM	supply	high	6	modeled
Configuration Management Database	ServiceNow CMDB	itsm	high	1	modeled

0 of the 2 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 1 of them are marked as taking a write back, which is a property of the system, not a live path from here.

How it performs

End to end

14.4 hrs

Summed from the time each step sits, standard 24.2 hrs — running at 59% of the standard.

Touchless

79%

Agent share

86%

A week

2,598

In flight

104

Effort a week

225 human minutes · 640 agent minutes

Volume multiplied by the time on each step. more

Assurance over this procedure

4 governance gates sit above it

The twenty-four controls and eighteen exception classes in this platform are held at estate level … more

Gate	What trips it	Who releases it	Clock	Waivable
Production release authorization approval	Any deployment to a production environment	Release manager and service owner	1 business day	No
Security-sensitive or public API change approval	Authentication, cryptography, payment paths or any published interface contract	Senior engineer and security engineer	1 business day	No
Database migration approval	Any schema change or irreversible data operation	Data owner and CTO delegate	2 business days	No
Agent-authored code sample review oversight	Weekly review of 10% of agent-authored merged changes	Engineering governance	Weekly	Yes

Next to it on the same team

Release & Deployment

Emergency Revert

EN6B

Release Readiness

EN6C

All of Engineering

What this document is and is not

These procedures describe the modeled estate. more

Actions

What is waiting on a person

What one procedure document gives you, and what to check before you treat it as the standard.

151

named approvers appear across the library

Every decision point on every procedure carries a job title, not a queue. more

143

steps in the library hand their unit to another function

A handoff is where a procedure stops being one team’s problem. more

controls exist in the estate, and they belong to no procedure in particular

Controls and exception classes are held estate-wide. more

Operations

What this desk is allowed to start

A surface that only reports is not operable. more

Trigger and bound

A procedure document prints purpose, scope, entry and exit, the numbered steps with the actor on each, the roles and their RACI position, the swimlane, the decision points and escalation, the handoffs, the governing rules with version and approver, the systems by rule and the timings. more

Live observability

What the record shows right now

The whole library, by lane, so a single document can be read against the estate it came from. more

Current distribution

2,748 steps

Agent, inside the function1,38951%

Agent, on the shared spine85131%

Person deciding at a gate50818%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Half. The document is complete and every actor on it is measured more

Not holding on the record

A procedure here carries a version, an approver, an in-force date and a last-review date. more