Every app execution on Majormatic follows a defined lifecycle. Each state has clear governance meaning. No output becomes final without passing every required stage.
Every run begins at Created and ends at Finalised, Cancelled, or Failed. Each transition is an event in the audit trail.
A new run has been initiated. Inputs have been validated and the execution request has been accepted. The cost has been confirmed by the user.
The app is actively executing under governance rules. The pipeline is running, inputs are being processed, and the output is being generated. This phase is handled by the platform — no user action required.
Execution is complete and the platform has produced a structured output. The output is available for review but is not yet final. It is clearly marked as a draft. If the app requires supervision, the user must review before proceeding.
The user has reviewed the draft and explicitly acknowledged professional responsibility for the output. The output is now edit-locked — its content is preserved as acknowledged. An audit record of the acknowledgement event has been created.
The output is immutable. It has been sealed to the Output Vault (shown in the current interface as Generated Vault). Billing settles at this point. The finalised output and its full audit record are permanently accessible. This is the system-of-record state.
The run has been archived. The output and audit trail remain accessible but the run is moved to long-term storage. Archived runs can be retrieved at any time.
Runs that do not reach Finalised may end in one of two states:
The execution encountered a technical issue and could not complete. Failed runs are not charged. The audit trail records the failure event and reason.
The run was cancelled before finalisation — either by the user or by the platform. Cancellation releases any held funds. The audit trail records the cancellation.
The human review and acknowledgement gate that moves a run from Draft to Acknowledged
Learn more →Every lifecycle transition is an audit event — all recorded, immutable, and traceable
Learn more →Where finalised outputs are sealed and permanently stored after the lifecycle is complete
Learn more →