0% read on this device
Browse the curriculum

Start Here

Vision

First Principles

Operating Model

Domain Model

Agent Factory

Runtime Architecture

AI Engineering

Autonomous Workflows

Verification & Delivery

Factory Platform

Quality Engineering

Security & Governance

Case Studies

Labs

Interview Practice

Research Journal

Reference

Curriculum/Operating Model/A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Operating Model5 min readchapterQuick Read

Enterprise Governance Operating Model and Decision Rights

Problem solved: Make authority explicit from enterprise risk appetite to one system, release, incident, and autonomy decision. Three levels: Executive governance; enablement and control; accountable system and business ownership. Critical s

Status: Review readyRisk: criticalLifecycle: intent · plan · execute · verify · deliver · learnContent reviewed 2026-08-30Maturity guide →
Claim boundaryThis is curriculum guidance. It does not by itself prove a production implementation.
architecture mode

A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.

4. Decision contract

Every portfolio, system, release, incident, and autonomy decision records:

  • subject, exact version, purpose, risk, and requested authority;
  • accountable decision owner and participating roles;
  • policy baseline, evidence, counterevidence, uncertainty, and exceptions;
  • alternatives including a lower-autonomy option;
  • decision, conditions, expiry, review trigger, and reason;
  • dissent or unresolved concern;
  • downstream grants or restrictions; and
  • correlation to later outcomes, incidents, and learning proposals.

Hidden model reasoning is neither required nor a valid authority artifact. Retain observable inputs, decisions, actions, outputs, and evidence.

8. Failure modes, detection, and recovery

FailureSignalImmediate actionRecovery
No named ownerInventory check failsBlock activation or promotionAccept named owner and backup
Self-approvalProducer and approver identity matchDeny decisionRe-run with independent reviewer
Expired exceptionExpiry monitorRestore baseline restrictionReassess or close exception
Slow emergency responseContainment SLO breachInvoke delegated backup authorityExercise and revise on-call chain
Assurance conflict ignoredDissent absent from decision recordPause material actionRecord, resolve, or explicitly escalate dissent

Measure decision latency, overdue reviews, exception age, self-approval attempts, control-test failure, time to contain, time to verified recovery, and outcomes by approved autonomy tier.

9. Tradeoffs and nonclaims

Central governance improves consistency but can become a bottleneck. Federated ownership improves speed but can fragment standards. Use centrally governed minimum controls with locally accountable implementation and risk-based escalation. This chapter does not prescribe job titles, legal conclusions, or a universal committee structure. It is review ready, not evidence that any organization operates the model.

External review

Review this chapter.

Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.

  • Claim
  • Boundary
  • Failure
  • Evidence