Who Reads This: Seven Events, Seven Entry Paths Into the Six Acts

Find the event that brought you here and take that path; do not read this front to back. The seven paths below each run four to six pages and route the most common arrivals: a security engineer handed a rollout to assess, an auditor's client asked for proof, a platform engineer whose merge gate rejects the bot, an engineering leader operationalizing a mandate, a developer who is the subject of one, a power user ahead of governance, and a founder blocked by a CISO. Each path weaves through the same six acts, so wherever you start, the next page is one click away.

The pattern under all seven is consistent across the audience research: almost nobody searches "AI governance." An external event lands on someone's desk, a rollout to assess, a merge that won't go through, a security questionnaire, and the search query is the event, not the principle (audience synthesis). Framework names surface in that same order. Community speech says SOC 2 first, then HIPAA and GDPR, then NIST, with ISO 42001 at near zero; only auditors speak framework natively.

The six acts run in order if you do want the full argument, and every path eventually crosses the thesis: automate the loop, not the keystroke.

• Overview. Orients and frames the build, assemble, or buy decision.
• Build the Environment. The isolated, reproducible machine and the threats that justify it.
• Manage the Work. The human-and-agent workflow: process, identity, decision gates, takeover, rollout.
• Prove It Holds. The compliance case as architecture.
• The Landscape. How industry actually runs agents.
• Reference. The checklists and the library.

Tasked to assess a rollout: the security engineer's path

A security or AppSec engineer at a 1,000 to 5,000 person company. The trigger verb is literal: "I've been tasked with evaluating the security implications of this decision". You want guardrails and incident evidence, not philosophy.

Read: What team-scale engineering requires → The lethal trifecta → Incidents overview → The seven properties → The checklist.

Asked for proof of responsible AI: the GRC path

GRC, internal audit, or AI-governance staff. Your questions rarely hit forums; they go to your auditor. Schellman's FAQ records the top one: how do you bring various compliance initiatives together into a single audit? You are the one persona that already says "ISO 42001."

Read: Why the laptop never had to answer this → Framework mapping → One audit, many frameworks → The four-axis audit query → Auditor questions.

An agent PR nobody can merge: the platform engineer's path

You hit governance as a bug report. The canonical one, from GitHub Community #175965: "The agent can create a PR, but no one can merge it because the commits are unsigned and the ruleset applies organization-wide." Nobody types "segregation of duties" into a forum; they type "Copilot PR cannot be approved."

Read: When branch protection blocks the bot → Agent identity → Binding to the human → Author, never approver → Reference architecture.

Operationalizing an adoption mandate: the engineering leader's path

An EM, director, or CTO facing the intake flood: "What's your process or framework for evaluating these AI tool requests?" Your real questions live in unsearchable Slacks, so the audience research reconstructs this profile from its shadow and flags it as partly inferred. You need economics and something forwardable.

Read: Why the laptop model breaks → Build, assemble, or buy → Honest numbers → Cohorts beat mandates → Measuring outcomes.

Measured, mandated, or banned: the governed developer's path

A senior IC who is mandated, banned, or measured. The 420-point r/ExperiencedDevs thread: "evaluated on how much they use AI, based on IDE metrics. Not evaluated on what you built." You are the largest public audience and the one most handbooks ignore. This one argues attribution protects you rather than surveils you, and that opt-out is a control, not a courtesy.

Read: What is logged about you → Attribution → Accountability stays human → Mandates and measurement → Review as a gate.

Running agents overnight already: the power user's path

Running agents overnight with --dangerously-skip-permissions. One r/ClaudeAI user wrote a strict "AI Instance Governance Rules" prompt, then reported back: "Took a couple of hours before Claude completely ignored every single rule." Your home-grown setup (credential-less container, separate reviewer, human holds the push key) is the design pattern this handbook formalizes.

Read: Sandboxing → One environment per task → Credentials and secrets → Egress control → Incident: Replit → Reference architecture.

Blocked by a CISO's security review: the founder's path

An agent-product founder in a vendor security review. The r/TheFounders version: "is there anything similar to SOC 2 but specifically for AI compliance?" The answer is ISO 42001. The asker didn't know the name, and that vocabulary gap is why this path leads with the questionnaire, not the framework.

Read: Security questionnaire → The checklist → SOC 2 and ISO 27001 → ISO 42001 → Certified and insured.

The roster oversamples the loud and predates the latest incidents

The Reddit evidence ends in May 2025, before the attribution wars and the largest incidents, so its silences are dated, not current. Public quotes also oversample people without private channels: ICs, solo operators, small founders. The real buying audience is likely more senior and less desperate than the verbatim record suggests (audience synthesis). If none of the seven fits you, start with the thesis and read in order.