Approvals & Provenance Vault¶
Scroll is built so that nothing is filed without a human and everything that is filed is provable. Two mechanisms deliver this: the approval gate and the Provenance Vault.
The approval gate¶
Submission workflows include a gate step. When the run reaches it, the engine pauses and creates an approval checkpoint (a Xybern Authorisation Layer escalation).
- Open the run and you'll see the prepared submission, the filled form data and the AI's analysis, laid out for review.
- Click Approve to release it to the submission step, or Reject to stop it with a recorded reason.
- Until you approve, nothing is submitted to any government portal.
This is the control that makes AI-prepared regulatory filings safe: the AI does the heavy lifting; a person authorises the consequential action.
The Provenance Vault¶
When a workflow completes, its seal step appends a tamper-proof entry to the Provenance Vault, a sealed record of what was filed, for whom, when, and by whom.
The Vault view lists every sealed run with:
| Column | Meaning |
|---|---|
| Sealed | When the record was sealed. |
| Workflow / Jurisdiction | What ran and where. |
| Status / Steps | Outcome and step count. |
| Parties / Value · Ref | Key entities and reference. |
| Compliance | Compliance summary. |
| Entry ID · Hash | The tamper-proof identifier. |
You can export the Vault to CSV for audits. Because each entry is hashed and sealed, it serves as defensible evidence of your regulatory actions, valuable for AML and audit obligations.
Together¶
The gate protects the decision; the Vault protects the record.