An example of transaction reporting exception remediation as a governed process: agents do the 9 steps, and a person signs 2 gates before anything irreversible happens. Download it, import it into your workspace, and adapt it to your systems.
minctrl.process/v1 · hash fd27b72e6448…94b3
Firms generate 100K-2M+ rejected, late or paired-but-unmatched MiFIR/EMIR/CFTC transaction reports a year, and analysts hand-triage each NACK, hunt the root cause across the OMS, reference-data and the ARM/TR feed, then manually re-key and backload corrections. The work is slow, error-prone and breaks SLA windows, exposing the firm to escalating regulatory fines and remediation programmes for persistent under/over-reporting. Agents triage every exception, root-cause it against the regulator's validation rules and reference data, draft deterministic field-level repairs and backloaded corrections, and stage the corrected batch — clearing the routine, rule-grounded cases automatically. Only the regulator-facing irreversible actions reach a human: a licensed officer signs off the corrected batch before resubmission and approves any material under/over-reporting self-disclosure to the FCA/ESMA/CFTC.
A minctrl.process/v1 document: the graph and the hash of the process it becomes.
Import into Minctrl opens this example in your workspace; one click stores it as your first version. Import JSON does the same with the file, and a file changed after download is refused.
Every connector starts in shadow: steps run, nothing leaves Minctrl until you configure a connector and switch it live.
Change signers, time limits and steps on the canvas. Each save is a new version; a running case stays on the version it started with.
Start from this example. Import the file in Processes, connect your own systems, and adapt the steps on the canvas. Agents run the reversible steps; every irreversible step waits at a gate for the role you choose. The example has 9 steps and 2 gates; you can change any of them.
Every run start, signature and change to the process is written to a hash-chained audit log your auditor can verify and export. The example is modelled on MiFIR/EMIR; whether your process meets it is a decision for your compliance team.
No. Minctrl will not make a process runnable while an irreversible step can be reached without a human gate, and one person cannot sign two gates of the same run.