Skip to main content

Operable

An Operable system can be understood, operated, troubleshot and changed safely by humans who did not build it. If only one person knows how it works, it is not production-ready. Every edition of the Baseline is delivered with the roles, the ownership rules, the documentation and the conventions that let the next engineer operate it at 3 AM.

Who operates what​

The same twelve roles across six teams exist in every edition, each as a group the code grants access to:

TeamRolesOwns
PlatformPlatform Lead, Platform EngineerThe landing zone: accounts, subscriptions or projects, network, guardrails, modules, address plan; production approval; incident escalation
DevOpsDevOps Lead, DevOps EngineerPipelines, pipeline identities, deployment strategy, monitoring and alerting, drift triage, incident command
App DevelopmentLead App Developer, App DeveloperThe Web App Blueprint repositories and the cluster workloads
Data EngineeringLead ETL Engineer, ETL EngineerThe Data and ETL Blueprint repositories, the processing jobs, data lake governance
AI/MLLead AI Engineer, AI EngineerML pipelines; optional at first
SecurityLead Security Auditor, Security AuditorFindings triage, compliance evidence, access reviews; read-only

Who can do what is therefore the same in the org chart, in the cloud's access model and in the remote-access matrix. The shared responsibility model places these roles against your cloud provider and BuiltForProd.

A change process anyone can follow​

Every change to shared environments follows the same path in every edition, and nobody applies from a laptop. In the blueprint infrastructure repositories the dev and staging jobs apply on merge and the prod job waits for the required reviewers of the prod GitHub Environment; the Baseline's single apply job runs under the prod Environment. Application code promotes by immutable tag, and rollback is a revert or a promotion of the previous tag, described on the Recoverable page.

Two comment tags make every repository self-describing:

Listing what a deployment must set and what it may change
git grep "TODO: " # values that must be set for your deployment: emails, ids, domains, group ids
git grep "@optional: " # choices the platform works without: switches, packs, sizing, extra stages

Every switch that costs money states its price in the comment beside it, so the person changing it knows what it costs before the plan runs.

How each edition delivers it​

In every edition, CODEOWNERS makes ownership enforceable: environments/core/, units/, .github/, root.hcl, common.hcl, the address plan and scripts/ belong to the infra admins; stacks/ and modules/ to the infra admins and platform leads; security.hcl to the infra admins and the security team; environments/plat/prod/ to the platform leads and the security team. In each secrets repository, sandbox/ and dev/ belong to the developers, and staging/, prod/, .github/, scripts/ and .sops.yaml to the platform leads and infra admins. An approval from any one listed owner satisfies the rule for a path.

AWS Enterprise Baseline​

Each role maps to an ACME_* IAM Identity Center group and a permission set. The Team Roles workbook sizes the minimum team at ten people. Feature switches live in one file per concern: network.hcl per region for NAT per AZ, isolation domains, Network Firewall and Transit Gateway peering, and security.hcl for every security service and the alert email.

The handover includes the deployment workbooks: the design decisions with the reasoning behind every choice, the architecture deep dive, the compliance and audit guides, the Client VPN guide, the module extensibility guide, the team workflow documents and the Update Lifecycle with a runbook for every change that touches an already-deployed platform. The DevOps workflow workbook gives the operator a monitoring checklist with a threshold per signal (subnet utilization above 80 percent, sustained Transit Gateway packet drops, any high or critical GuardDuty finding, any CIS alarm, a runner not starting within two minutes, a cost anomaly above 20 percent). The Team Workflow workbook defines incident severities for your team: P1 (prod down) with a 15-minute response, P2 (prod degraded) within an hour, P3 (non-production) the next business day.

Azure Enterprise Baseline​

Each role maps to an ACME_* Microsoft Entra ID group and Azure RBAC roles at management-group or subscription scope; ACME_AllEngineers carries read access to prod and ACME_BreakGlass the emergency path, 14 groups in all. The groups are created by your IT and looked up by display name, or created by the code with create_groups. CODEOWNERS adds the platform leads to network.hcl, the security team to policies/ (the WAF template) and the DevOps leads to runner-image/, and the prod Environment's reviewers are the platform leads and the DevOps leads, with self-review prevented.

The switch files are environments/core/network/<region>/network.hcl (egress mode, firewall SKU and zones, isolation domains, threat-intelligence mode, the DNS Private Resolver, Traffic Analytics, the point-to-site VPN and its group access matrix) and environments/core/security/security.hcl (Defender plans, Sentinel, compliance initiatives, DDoS protection, Entra log export, CIS alerts, the alert email). PIM is a switch in the identity stack, enable_pim, and Conditional Access starts report-only through conditional_access_state. The handover includes the README of each repository and this site's documentation for the edition; the Azure Enterprise Baseline overview describes what you receive.

GCP Enterprise Baseline​

Each role maps to a Google group acme-<role>@company.com bound to IAM role bundles at the organization, the folders and the stage projects; acme-all-engineers carries read access to prod and acme-break-glass the emergency path, 14 groups in all. Your IT creates the groups, or the code does with create_groups. CODEOWNERS adds the security team to policies/ (the Cloud Armor template) and src/ (the notifier).

Four files hold the switches: environments/core/network/<region>/network.hcl (isolation domains, Cloud NAT, flow log sampling, DNS query logging, threat intelligence, bastions, VPC Service Controls), environments/core/security/security.hcl (Security Command Center tier, Data Access logs, Artifact Analysis, CIS alerts, the notifier and remediation, retention locks, Cloud Armor Enterprise, the alert email), environments/core/identity/identity.hcl (create_groups, enable_pam, PAM notification mailboxes) and environments/plat/plat.hcl (webapp_gke_stages, the stages whose web app clusters receive their grants). The handover includes the README of each repository and this site's documentation for the edition; the GCP Enterprise Baseline overview describes what you receive.

Day-to-day operations​

Drift issues are triaged daily in every edition: a console change is reverted from code; a desired change is brought into code. The drift page describes the triage. The operating conventions above are what the platform is delivered with; the response commitments BuiltForProd itself makes under Managed are on the service level agreements page.

Operated with you or for you​

Everything above assumes your team operates the platform. BuiltForProd Managed adds on-demand engineers, an SLA-backed support contract, or engineers embedded in your team; contacting support lists the channels.

How you verify it​

AWS Enterprise Baseline​

  • IAM Identity Center in the identity account: the ACME_* groups and their permission set assignments.
  • The handover documentation set: every workbook named above.

Azure Enterprise Baseline​

  • Microsoft Entra ID, Groups: the 14 ACME_* groups; Access control (IAM) at mg-acme: their role assignments.
  • Repository settings, Environments, prod: the platform leads and DevOps leads as required reviewers.

GCP Enterprise Baseline​

  • Google Workspace or Cloud Identity admin console, Groups: the 14 acme-* groups.
  • gcloud organizations get-iam-policy 161616161616: the auditor bindings at the organization.

In every edition, .github/CODEOWNERS in each repository shows the rules above, the repository settings show branch protection on main, and git grep "TODO: " on your repositories returns nothing unresolved after handover.