liveBook · Manning

Governance

As explained in Vibe Engineering

Governance infrastructure is the collection of policies, controls, processes, roles, and supporting systems that direct and constrain system use.

AI agents expose a governance gap: informal conventions, unclear ownership, incompatible licenses, and missing audit trails fail once agents write and change code at scale. Governance therefore turns tribal knowledge into explicit policies, controls, roles, and processes. section 5.5

Policies alone are insufficient. Serious agent workflows need an evidence layer that reconstructs what happened, rather than treating human approval as an audit trail. section 5.5.2

A practical governance control plane should:

  • Record the model, tools, files, generated or transformed code, checks, sessions, and final approver. section 5.5.2
  • Enforce stronger review or security checks for sensitive repositories, critical paths, and changes exceeding defined AI-generation thresholds. section 5.5.2
  • Combine tiered review with reliable tests, sandboxing, fast feedback, and audit trails so automation does not turn queues into rubber-stamping. section 10.6.3

Scale governance to the risk

Two developers on a simple, unregulated project may rely on direct conversation. Large teams, complex systems, and regulated industries gain value from standardization through reduced confusion, faster onboarding, fewer incidents, and audit readiness. Formalize neither too early nor too late. section 5.5.3

How Vibe Engineering covers it

How deep it goes
Moves from policy rationale to evidence-layer architecture and review controls, while deferring exact implementation choices.
Examples
Uses policy files, agent-session records, tool-call logs, critical-path checks, tiered review, and audit trails as concrete governance artifacts.
What it assumes
Assumes agent workflows that edit files, invoke tools, open pull requests, or span sessions, while teaching why informal oversight no longer scales.
What you can do after
Operate/configure governance by defining enforceable policies, capturing agent lineage, and matching review overhead to system risk.
How it connects
Connects AI agents with compliance, audit trails, code review, pull requests, testing, sandboxing, and continuous modernization.

Also explained in

Compare how 9 books explain governance →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.