Capability 04 — Govern

Every action bounded, approved, and auditable

Governance isn't a settings page you visit once. It is evaluated on every request, before every worker attempt, and again when a paused approval resumes hours later.

Guardrails

Nine categories, declared per step

A guardrail can redact, block, transform, or require approval. Each workflow step names the categories it must clear — and execution stops if any of them isn't satisfied.

01Data accessControls which data may be retrieved and combined.
02PrivacyControls sensitive data disclosure, minimization, and redaction.
03Model inputControls information supplied to a model.
04Model outputValidates and transforms generated output.
05ActionControls connector writes and external side effects.
06FinancialControls financial interpretation and transaction actions.
07ComplianceApplies regulatory and contractual requirements.
08CostControls model, connector, and workflow consumption.
09Human approvalRequires an authorized person before execution continues.
Roles & permissions

Editable roles, protected authority

Roles are server-side permission bundles, not hard-coded policy. Standard roles are catalog presets you can start from and edit. What you cannot do is escalate — protected owner authority, incident authority, and legal-hold authority can never be obtained through an ordinary custom role.

  • Deny by default. Authorization denies unknown actions, inactive policies, tenant mismatches, missing permissions, and insufficient authentication assurance.
  • Revocation takes effect immediately. Deferred work re-resolves the actor's current membership and grants before each attempt, so suspension and permission removal land before the job runs.
  • Browser claims are never trusted. Organization, role, and assurance are derived server-side from a verified session or workload token.
Business OwnerProtected

Protected accountable owner. Full administration plus billing, data export, and offboarding authority.

Customer Super Admin

Broad administration including billing and export, without protected owner authority.

Admin without billing

Configuration, credentials, connections, workflow execution and approval, audit, and role management.

Staff

Ordinary approved workflow access — read the organization, execute and cancel workflows.

Permission catalog
organization.readconfiguration.managecredential.manageconnection.manageworkflow.executeworkflow.cancelworkflow.approveaudit.readrole.managebilling.managedata.exportorganization.offboard
Cost control

Budgets are policy, not a monthly surprise

AI spend is governed the same way data access is. Organization-level budgets and cost guardrails cap model, connector, and workflow consumption — with thresholds that warn before they stop, and authenticated, permission-scoped mutations whenever a budget changes.

WarnNotify ownersThreshold crossed; execution continues.
Require approvalHuman in the loopFurther spend needs an authorized approver.
StopFail closedConsumption halts rather than overrunning.
Audit

Append-only, and deliberately incomplete

The audit stream records identifiers, policy decisions, timing, and redacted summaries. It does not record secret values, unrestricted source payloads, exception messages, or vendor response bodies — because an audit log that captures everything becomes the next thing you have to protect.

Reading the stream is itself an authorized, audited action, evidenced with only the actor, page size, result count, and whether a cursor was present.

workflow.approvedactor · policy decision · timing
connection.verifiedtenant-bound reference · no secret material
execution.failedcoarse category only · no exception text
audit.readactor · page size · result count
Bring your policy

Show us the rule you can't currently enforce

Most businesses have a policy that exists in someone's head or a document nobody reads. Call us with one, and we'll show you what it looks like as a guardrail that actually stops execution.