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.

Use the smallest safe stop

Possible containment levels include a single action hold, workflow branch stop, full workflow stop, agent or tool disable, domain stop, and global emergency stop.

Authority must be explicit

The system should not depend on the malfunctioning component to authorize its own shutdown. Stop authority and restart authority should be defined in advance.

Preserve evidence before cleanup

Recovery should retain the trigger, last confirmed successful step, approval state, external-action status, relevant receipts, logs, configuration, and downstream evidence.

Recovery is not the same as retry

Recovery may involve resume, rollback, manual correction, alternate path, rebuild, human takeover, or retirement of the affected capability.

Restart is a governance decision

After serious incidents, restart should require evidence such as remediation, retest, state resolution, monitoring restoration, permission verification, and authorized human approval.

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.