Every execution on Majormatic produces a draft. That draft remains a draft until a qualified professional explicitly reviews and acknowledges it. Supervision cannot be bypassed, disabled, or automated away.
Supervision is the mechanism that ensures AI is infrastructure, not authority. The platform executes. The human decides.
After execution completes, the output enters a supervised review state. The user reviews the draft and makes one of three decisions.
The platform has completed execution and produced a structured output. The output is available for review but carries no professional weight until acknowledged. It is clearly marked as a draft.
When the user clicks Acknowledge, they formally accept responsibility for the output. An audit record is created immediately with their identity and timestamp. The output is now edit-locked — no further changes to the draft content.
Finalisation seals the output permanently. The finalised record is immutable. It is saved to the Output Vault (shown in the current interface as Generated Vault). Billing settles at this point. The audit trail is complete.
Not every app requires explicit acknowledgement. But any app that produces outputs with legal, financial, regulatory, or professional consequences must require it.
Legal memos, case analysis, contract summaries, and any output a professional will act on without independent verification require explicit acknowledgement.
Financial assessments, credit analysis, management accounts, and structured financial outputs must pass through supervision before finalisation.
Compliance documents, regulatory submissions, policy outputs, and any output presented to a regulator or governing body require explicit human sign-off.
Every supervision event — acknowledgement, rejection, finalisation — is recorded in the immutable audit trail
Learn more →How supervision fits into the full run lifecycle from creation to finalisation
Learn more →Where finalised outputs are sealed and stored after the supervision gate is complete
Learn more →