Why Catha treats this as governance: AI capability and business authority are not the same thing. The business should decide the control before the system is allowed to scale the action.

The control plane and execution plane

The execution plane contains agents, tools, data, workflows, schedules, and external actions. The control plane contains authority, rules, approvals, limits, validation, receipts, monitoring, cost control, error handling, and recovery. The two should be connected but not confused.

Why capability does not equal authority

Modern agents may be able to browse, send mail, modify records, publish content, execute code, and trigger other systems. Governance exists to decide when those capabilities are actually permitted.

How the spine governs a workflow

A governed workflow can trace each material step to a responsible role, authority source, rule, permission, autonomy level, approval requirement, required evidence, failure behavior, retry rule, escalation path, and safe continuation.

Safe Forward Progress

The spine does not treat every defect as a global shutdown. An unresolved issue blocks only the exact dependency it affects while unrelated safe work continues.

Production control

The governance spine extends beyond design. It includes formal testing, production approval, monitoring, cost awareness, emergency stop, recovery, restart authority, and final cross-system readback.

How this fits the Catha AI Governance Build Kit

This topic is one part of the broader Catha AI Governance Build Kit, a fourteen-stage build process covering business outcome, governance discovery, authority, rules, permissions, autonomy, workflow design, validation, receipts, production approval, monitoring, recovery, final readback, and platform export.

The governance baseline belongs to the business. Platform-specific implementation may differ, but approved authority, rules, permissions, autonomy, approvals, and evidence requirements should not silently change.