Majormatic is governed by design. Every execution is subject to rules that validate the app, enforce human supervision, and ensure outputs cannot become final without explicit professional acknowledgement.
Governance is not a feature that can be enabled or disabled. It is a structural property of every execution on Majormatic. You cannot run an app without governance applying. You cannot bypass supervision. You cannot finalise an output without acknowledgement.
Before any execution begins, governance validates the app, confirms the estimated cost, and checks that the user and organisation have the access and entitlements required. Only then does execution proceed.
Every ABI App must define its inputs, workflow, outputs, risk level, and supervision requirements before it can be used. Invalid apps are blocked before execution. The platform validates the structure on every run.
Apps that produce legal decisions, financial calculations, regulatory outputs, or other high-stakes results require explicit human review and acknowledgement before the output is treated as final. This cannot be bypassed.
Every user sees the estimated cost before an execution proceeds. You confirm or cancel. Execution does not start without your confirmation. You are never charged without seeing the cost first.
Every execution creates an immutable audit record. The record captures inputs, outputs, governance decisions, supervision events, and the finalisation record. Records cannot be modified or deleted.
Enterprise organisations can configure governance policies that apply to all executions within their account — requiring additional supervision, restricting certain app types, or setting execution limits. Organisation policies always operate within platform boundaries.
Governance operates at three levels. Each level can restrict further — never relax — the level above it.
The baseline rules that apply to every execution on Majormatic — regardless of organisation or app. These cannot be weakened by any user, admin, or app configuration.
Enterprise organisations can add more restrictive governance policies — for example, mandating supervision for all executions or restricting which app types their users can access.
Each ABI App declares its own governance requirements — risk level, supervision requirement, and execution constraints. App-level governance cannot relax the platform or organisation levels.