Governance
Governance in Subbasis is operational: policy, approvals, and evidence are part of execution, not afterthoughts.
What this means
Governance defines what actions can run, by whom, under which conditions, and how outcomes are reviewed.
Why it matters
AI-assisted operations without governance create risk amplification. Governance keeps execution aligned with organizational responsibility.
How Subbasis handles it
Governance primitives include:
- Permission boundaries
- Approval gates
- Policy checks
- Reviewable execution history
Subbasis governance also ties to organization model and role structure so permissions and review responsibilities are explicit.
Example scenario
A finance workflow may allow an agent to prepare a vendor payment request, but require a human approval gate before any external action is executed.
Policy checks verify scope, approval status, and allowed connector path before execution.
What to configure
- role-based permission matrix
- policy rules by operation type
- approval gate conditions and approvers
- evidence requirements for sensitive actions
- review routines for exceptions/failures
Limits and deployment notes
- Governance depth depends on plan and deployment setup.
- Subbasis provides regulated-ready technical primitives; this is not a certification claim.
Related docs
Read Reference limits.