An example of workers compensation claims as a governed process: agents do the 8 steps, and a person signs the gate before anything irreversible happens. Download it, import it into your workspace, and adapt it to your systems.
minctrl.process/v1 · hash ce0723e58891…316c
Workers'-comp claims handling is high-volume AOE/COE compensability + AWW/benefit computation under 50 state acts, where a wrong denial or benefit termination denies an injured worker statutory benefits and is actionable as bad-faith claims handling. Injuries intaken, compensability determined and benefits computed straight-through; the licensed claims adjuster signs the compensability determination before the EDI claim is filed with the state.
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 8 steps and 1 gate; 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. A run is pinned to the exact graph it started on.
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.