Majormatic uses scoped Vault custody, with Input Vault for source/context materials and Output Vault for generated, reviewed, finalised, and evidenced outputs. Inputs and outputs are stored in separate namespaces, each with distinct access and retention rules.
Inputs and outputs never mix. The Vault is split into two separate areas with different purposes, access controls, and retention periods.
Every file you upload before an execution — documents, data, references — is stored in the Input Vault. Files are linked to the run they were provided for. They are accessible to the user who uploaded them and authorised administrators. Input Vault is shown in the current interface as Primary Vault.
Uploaded input files, reference documents, and raw evidence provided by the user before execution.
Active 30-day retention window by default. Vault extension is available beyond the active window.
Accessible to the user who uploaded and authorised admins. No direct URL access — files are served via secure, time-limited download links.
Every finalised output is sealed into the Output Vault. Once sealed, it cannot be modified. The Output Vault is the system-of-record for professional outputs — the evidence that the right process produced the right result. Output Vault is shown in the current interface as Generated Vault.
Finalised, acknowledged outputs from governed executions. Each output is linked to its run, governance record, and acknowledgement event.
Sealed on finalisation. Cannot be modified, overwritten, or deleted after sealing. Immutability is enforced at the platform level.
Open the sealed record to view its contents. Export options — JSON, TXT, DOCX, and PDF — are available from inside the record view. Access events are recorded in the audit trail.
Before running an app, upload reference documents, data files, or evidence. Uploaded files go into your Input Vault and are linked to the execution.
The platform runs the app against your inputs under governance rules. The generated output is a draft — not yet in the Output Vault.
Review the draft output. When satisfied, acknowledge responsibility. The output is now acknowledged and ready to finalise.
Finalisation seals the output into the Output Vault. The record is immutable. You can download the finalised output at any time.
The acknowledgement gate that must be passed before outputs are sealed to the Output Vault
Learn more →Every Vault access — upload, download, finalisation — is recorded in the immutable audit trail
Learn more →Where your projects, active runs, and Vault-linked outputs are organised
Learn more →