Standard operating procedures · Engineering
The Engineering procedure manual
33 written procedures across 11 teams, made of 176 numbered steps. 37 of those steps are a person deciding and 139 are agent work … more
Procedures
33
Median 5 steps long.
Numbered steps
176
Every one carries exactly one actor.
Decision points
37
21% of this function's steps stop for a person.
Agent steps
139
75 of them on the shared spine.
Named agents
89
Registered against the teams inside this function.
Units a week
116,848
Across every procedure in this manual.
Who this manual belongs to
Accountability above the procedures
Accountable
Chief Technology Officer
The end of the escalation path for every procedure in this manual. more
Chief of staff
Engineering Chief of Staff
Holds the operating rhythm of the function: the cadence these procedures are reviewed on and the queue of changes waiting to be made to them.
Autonomy across this function
71% now · 80% target
This is the function’s declared autonomy, not a reading taken from the procedures. Measured off the procedures themselves, 79% of the steps in this manual run without a person. The two are different questions and they do not have to agree.
The service level
Change request triage
response-time · target 240 mins · Rolling 30 days, median
Nothing measures this yet. The target is declared; the attainment is not.
Triage timestamps are not consistently written, so attainment here is estimated from a monthly sample rather than measured across the population.
Governance gates on this function
4 declared
These are rules about the function as a whole, not about one procedure. 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 |
Run any procedure in this manual
33 to choose from
This is a run, not a forecast. One unit enters the procedure and is walked station by station in the recorded order, each station taking exactly the dwell the estate records for it, held by whoever the estate says holds it. The clock you watch is worked time: the sum of the time the work is actually being done. Pick a procedure on the left and press run. 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. Viable means the path is the one the estate already permits: the lanes are the recorded lanes, every decision that stops for a person still stops for that person, and no step is moved unless the owning team has autonomy ceiling left to cover it. It is a floor for how fast this procedure can go while staying inside its own rules, not a promise about any particular Tuesday.
Nothing has happened yet. more
- 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 70% autonomy ceiling and this run sits at 86% unattended, inside it.
- 1 system is attributed across the stations, and 0 of them are connected. Nothing in this run has been watched executing against a real system of record.
One decision, held by Chief Architect. more
- 07 Review board ratify — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.
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
Portfolio & Intake
3 procedures · 16 steps · 4 decisions
Runs the line
Engineering Intake Orchestrator
Accountable
VP Engineering Operations
Layers in play
strategy · observe · workflow · gbs
That team’s remit
Owns request work end to end inside Engineering. more
Why the ceiling sits there
Triage, estimation and dependency mapping are agentic. more
The 4 rules every procedure in this team runs inside
Portfolio & Intake Decision Envelope
activeEN1-POL-200 · Envelope · v5.6 · approved by VP Engineering Operations
Agents in this lane may act without a human when the request sits inside the stated value, risk and confidence envelope. more
Portfolio & Intake Evidence Standard
activeEN1-POL-201 · Evidence · v1.0 · approved by VP Engineering Operations
Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more
Portfolio & Intake Escalation Rule
activeEN1-POL-202 · Escalation · v3.5 · approved by VP Engineering Operations
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
Portfolio & Intake Autonomy Ceiling
activeEN1-POL-203 · Ceiling · v3.8 · approved by VP Engineering Operations
The ceiling for this lane is 74 on the platform scale. more
| Code | Procedure | Steps | Decisions | Who does the work | Agent % | A week | |
|---|---|---|---|---|---|---|---|
| EN1A | Intake-to-BacklogT | 7 | 2 | 71% | 4,388 | ||
| EN1B | Capacity RebalanceA | 4 | 1 | 75% | 73 | ||
| EN1C | Investment PositionJ | 5 | 1 | 80% | 1 |
Architecture & Design
3 procedures · 17 steps · 3 decisions
Runs the line
Architecture Orchestrator
Accountable
Chief Architect
Layers in play
strategy · policy · observe · workflow
That team’s remit
Owns design decision work end to end inside Engineering. more
Why the ceiling sits there
Agents author the design options and the decision record. more
The 2 rules every procedure in this team runs inside
Architecture & Design Decision Envelope
activeEN2-POL-200 · Envelope · v5.8 · approved by Chief Architect
Agents in this lane may act without a human when the design decision sits inside the stated value, risk and confidence envelope. more
Architecture & Design Evidence Standard
activeEN2-POL-201 · Evidence · v1.6 · approved by Chief Architect
Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more
| Code | Procedure | Steps | Decisions | Who does the work | Agent % | A week | |
|---|---|---|---|---|---|---|---|
| EN2A | Design DecisionJ | 7 | 1 | 86% | 5 | ||
| EN2B | Pattern Compliance SweepT | 5 | 1 | 80% | 6,939 | ||
| EN2C | Architecture Strategy PositionJ | 5 | 1 | 80% | 2 |
Build
3 procedures · 16 steps · 4 decisions
Runs the line
Build Orchestrator
Accountable
Director, Platform Engineering
Layers in play
strategy · observe · workflow
That team’s remit
Owns change work end to end inside Engineering. more
Why the ceiling sits there
Code generation and dependency maintenance are near-touchless. more
The 4 rules every procedure in this team runs inside
Build Decision Envelope
activeEN3-POL-200 · Envelope · v3.2 · approved by Director, Platform Engineering
Agents in this lane may act without a human when the change sits inside the stated value, risk and confidence envelope. more
Build Evidence Standard
activeEN3-POL-201 · Evidence · v1.0 · approved by Director, Platform Engineering
Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more
Build Escalation Rule
activeEN3-POL-202 · Escalation · v2.9 · approved by Director, Platform Engineering
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
Build Autonomy Ceiling
activeEN3-POL-203 · Ceiling · v5.0 · approved by Director, Platform Engineering
The ceiling for this lane is 86 on the platform scale. more
| Code | Procedure | Steps | Decisions | Who does the work | Agent % | A week | |
|---|---|---|---|---|---|---|---|
| EN3A | Feature BuildT | 6 | 2 | 67% | 1,610 | ||
| EN3B | Dependency UpdateT | 6 | 1 | 83% | 6,826 | ||
| EN3C | Documentation SyncT | 4 | 1 | 75% | 7,091 |
Code Review & Quality
3 procedures · 14 steps · 5 decisions
Runs the line
Code Quality Orchestrator
Accountable
Director, Engineering Quality
Layers in play
strategy · policy · observe · workflow
That team’s remit
Owns pull request work end to end inside Engineering. more
Why the ceiling sits there
Analysis and comment generation are fully agentic and never get tired. more
The 3 rules every procedure in this team runs inside
Code Review & Quality Decision Envelope
under reviewEN4-POL-200 · Envelope · v3.7 · approved by Director, Engineering Quality
Agents in this lane may act without a human when the pull request sits inside the stated value, risk and confidence envelope. more
Code Review & Quality Evidence Standard
activeEN4-POL-201 · Evidence · v4.1 · approved by Director, Engineering Quality
Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more
Code Review & Quality Escalation Rule
activeEN4-POL-202 · Escalation · v2.1 · approved by Director, Engineering Quality
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
| Code | Procedure | Steps | Decisions | Who does the work | Agent % | A week | |
|---|---|---|---|---|---|---|---|
| EN4A | Pull Request ReviewT | 6 | 2 | 67% | 6,838 | ||
| EN4B | Quality Debt SweepT | 4 | 1 | 75% | 304 | ||
| EN4C | Convention ChangeT | 4 | 2 | 50% | 2,432 |
Test & Assurance
3 procedures · 15 steps · 3 decisions
Runs the line
Test Orchestrator
Accountable
Director, Quality Engineering
Layers in play
strategy · observe · workflow · gbs
That team’s remit
Owns test run work end to end inside Engineering. more
Why the ceiling sits there
Test generation, selection and triage are the highest-autonomy work in Engineering. more
The 2 rules every procedure in this team runs inside
Test & Assurance Decision Envelope
activeEN5-POL-200 · Envelope · v1.7 · approved by Director, Quality Engineering
Agents in this lane may act without a human when the test run sits inside the stated value, risk and confidence envelope. more
Test & Assurance Evidence Standard
activeEN5-POL-201 · Evidence · v3.4 · approved by Director, Quality Engineering
Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more
| Code | Procedure | Steps | Decisions | Who does the work | Agent % | A week | |
|---|---|---|---|---|---|---|---|
| EN5A | Release Test CycleT | 6 | 2 | 67% | 5,597 | ||
| EN5B | Flaky Test RemediationT | 5 | 0 | 100% | 2,706 | ||
| EN5C | Performance BaselineT | 4 | 1 | 75% | 7,697 |
Release & Deployment
3 procedures · 15 steps · 3 decisions
Runs the line
Release Orchestrator
Accountable
Director, Release Engineering
Layers in play
strategy · policy · observe · workflow · gbs
That team’s remit
Owns release work end to end inside Engineering. more
Why the ceiling sits there
Canary analysis and automatic revert are faster than any human and run unsupervised. more
The 4 rules every procedure in this team runs inside
Release & Deployment Decision Envelope
activeEN6-POL-200 · Envelope · v3.3 · approved by Director, Release Engineering
Agents in this lane may act without a human when the release sits inside the stated value, risk and confidence envelope. more
Release & Deployment Evidence Standard
supersededEN6-POL-201 · Evidence · v3.1 · approved by Director, Release Engineering
Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more
Release & Deployment Escalation Rule
activeEN6-POL-202 · Escalation · v4.6 · approved by Director, Release Engineering
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
Release & Deployment Autonomy Ceiling
activeEN6-POL-203 · Ceiling · v1.4 · approved by Director, Release Engineering
The ceiling for this lane is 85 on the platform scale. more
| Code | Procedure | Steps | Decisions | Who does the work | Agent % | A week | |
|---|---|---|---|---|---|---|---|
| EN6A | Production ReleaseT | 7 | 1 | 86% | 2,598 | ||
| EN6B | Emergency RevertT | 5 | 1 | 80% | 6,809 | ||
| EN6C | Release ReadinessT | 3 | 1 | 67% | 4,656 |
Site Reliability
3 procedures · 17 steps · 3 decisions
Runs the line
Reliability Orchestrator
Accountable
Director, Site Reliability
Layers in play
strategy · policy · observe · workflow · gbs
That team’s remit
Owns incident work end to end inside Engineering. more
Why the ceiling sits there
Correlation and runbook execution run in seconds without a human. more
The 3 rules every procedure in this team runs inside
Site Reliability Decision Envelope
activeEN7-POL-200 · Envelope · v1.6 · approved by Director, Site Reliability
Agents in this lane may act without a human when the incident sits inside the stated value, risk and confidence envelope. more
Site Reliability Evidence Standard
activeEN7-POL-201 · Evidence · v4.7 · approved by Director, Site Reliability
Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more
Site Reliability Escalation Rule
activeEN7-POL-202 · Escalation · v4.6 · approved by Director, Site Reliability
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
| Code | Procedure | Steps | Decisions | Who does the work | Agent % | A week | |
|---|---|---|---|---|---|---|---|
| EN7A | Incident ResponseT | 8 | 1 | 88% | 7,793 | ||
| EN7B | Error Budget EnforcementT | 5 | 1 | 80% | 3,053 | ||
| EN7C | Capacity ResponseT | 4 | 1 | 75% | 5,263 |
Technical Debt
3 procedures · 16 steps · 3 decisions
Runs the line
Technical Debt Orchestrator
Accountable
Director, Engineering Effectiveness
Layers in play
strategy · observe · workflow
That team’s remit
Owns debt item work end to end inside Engineering. more
Why the ceiling sits there
Detection, migration and deprecation are mechanical and agentic. more
The 2 rules every procedure in this team runs inside
Technical Debt Decision Envelope
activeEN8-POL-200 · Envelope · v4.7 · approved by Director, Engineering Effectiveness
Agents in this lane may act without a human when the debt item sits inside the stated value, risk and confidence envelope. more
Technical Debt Evidence Standard
activeEN8-POL-201 · Evidence · v5.7 · approved by Director, Engineering Effectiveness
Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more
| Code | Procedure | Steps | Decisions | Who does the work | Agent % | A week | |
|---|---|---|---|---|---|---|---|
| EN8A | Debt RemediationT | 6 | 1 | 83% | 7,727 | ||
| EN8B | Deprecation CampaignT | 5 | 1 | 80% | 4,772 | ||
| EN8C | Debt Doctrine PositionJ | 5 | 1 | 80% | 4 |
Developer Experience
3 procedures · 16 steps · 2 decisions
Runs the line
Developer Experience Orchestrator
Accountable
Director, Developer Platform
Layers in play
strategy · observe · workflow · gbs
That team’s remit
Owns developer request work end to end inside Engineering. more
Why the ceiling sits there
Environment provisioning and toolchain setup are fully self-service and touchless. more
The 3 rules every procedure in this team runs inside
Developer Experience Decision Envelope
under reviewEN9-POL-200 · Envelope · v4.3 · approved by Director, Developer Platform
Agents in this lane may act without a human when the developer request sits inside the stated value, risk and confidence envelope. more
Developer Experience Evidence Standard
activeEN9-POL-201 · Evidence · v4.1 · approved by Director, Developer Platform
Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more
Developer Experience Escalation Rule
under reviewEN9-POL-202 · Escalation · v3.3 · approved by Director, Developer Platform
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
| Code | Procedure | Steps | Decisions | Who does the work | Agent % | A week | |
|---|---|---|---|---|---|---|---|
| EN9A | Environment RequestT | 5 | 0 | 100% | 3,674 | ||
| EN9B | Friction RemediationT | 6 | 1 | 83% | 5,890 | ||
| EN9C | Developer OnboardingT | 5 | 1 | 80% | 4,391 |
Security Engineering
3 procedures · 19 steps · 4 decisions
Runs the line
Security Engineering Orchestrator
Accountable
Director, Security Engineering
Layers in play
strategy · policy · observe · workflow · gbs
That team’s remit
Owns finding work end to end inside Engineering. more
Why the ceiling sits there
Scanning, credential revocation and low-risk patching are automatic because speed is the control. more
The 3 rules every procedure in this team runs inside
Security Engineering Decision Envelope
activeEN10-POL-200 · Envelope · v1.6 · approved by Director, Security Engineering
Agents in this lane may act without a human when the finding sits inside the stated value, risk and confidence envelope. more
Security Engineering Evidence Standard
activeEN10-POL-201 · Evidence · v3.4 · approved by Director, Security Engineering
Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more
Security Engineering Escalation Rule
activeEN10-POL-202 · Escalation · v5.1 · approved by Director, Security Engineering
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
| Code | Procedure | Steps | Decisions | Who does the work | Agent % | A week | |
|---|---|---|---|---|---|---|---|
| EN10A | Vulnerability RemediationT | 7 | 1 | 86% | 3,326 | ||
| EN10B | Secret Exposure ResponseT | 6 | 2 | 67% | 4,241 | ||
| EN10C | Threat Model ReviewJ | 6 | 1 | 83% | 3 |
Engineering Analytics
3 procedures · 15 steps · 3 decisions
Runs the line
Engineering Analytics Orchestrator
Accountable
Director, Engineering Analytics
Layers in play
strategy · observe · workflow · gbs
That team’s remit
Owns analysis work end to end inside Engineering. more
Why the ceiling sits there
Metric assembly and trend detection are fully agentic. more
The 4 rules every procedure in this team runs inside
Engineering Analytics Decision Envelope
activeEN11-POL-200 · Envelope · v1.4 · approved by Director, Engineering Analytics
Agents in this lane may act without a human when the analysis sits inside the stated value, risk and confidence envelope. more
Engineering Analytics Evidence Standard
under reviewEN11-POL-201 · Evidence · v3.4 · approved by Director, Engineering Analytics
Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more
Engineering Analytics Escalation Rule
activeEN11-POL-202 · Escalation · v4.3 · approved by Director, Engineering Analytics
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
Engineering Analytics Autonomy Ceiling
activeEN11-POL-203 · Ceiling · v5.6 · approved by Director, Engineering Analytics
The ceiling for this lane is 88 on the platform scale. more
| Code | Procedure | Steps | Decisions | Who does the work | Agent % | A week | |
|---|---|---|---|---|---|---|---|
| EN11A | Monthly Engineering ReadA | 6 | 1 | 83% | 83 | ||
| EN11B | Cost per Service ReadA | 4 | 1 | 75% | 52 | ||
| EN11C | Measurement Doctrine PositionJ | 5 | 1 | 80% | 4 |
Where this manual comes from
Nobody wrote these procedures. more
What it cannot claim
The twenty-four controls and eighteen exception classes in this platform are held at estate level … more
These procedures describe the modeled estate. more
Actions
What is waiting on a person
What a single function manual is for, and the three things worth checking the moment you open one.
governing rules bind the teams inside these functions
Every team carries between two and four rules covering evidence, envelope, escalation and ceiling. 395 are active. more
governance gates are declared across the function estate
A governance gate is a rule about the function, not about a single procedure: a threshold, a named approver and a clock. more
points separate the most and least agent-run function, Customer Service and Legal
Customer Service runs 90% of its steps without a person and Legal runs 76%. The gap is not a target and not a failing … more
Operations
What this desk is allowed to start
A surface that only reports is not operable. more
Trigger and bound
A function manual gathers every procedure the function owns, grouped by the team that runs it, with the orchestrator, the accountable human, the autonomy ceiling and the governing rules printed against each team. more
Live observability
What the record shows right now
How the manuals differ in size, by number of written procedures. more
Current distribution
211 procedures
Is policy and strategy coming to fruition
Whether the written intent is holding here
Holding on structure, not on assurance. more
Not holding on the record
Every manual is complete: 475 procedures with nothing unassigned, 154 teams each carrying an orchestrator and a named accountable human, and every step attributed to a lane. more