An example of managed IT services as a governed process: agents do the 8 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 97ade22e6101…638c
Managed-IT work (patching, config, access) is labour-heavy across many clients; one bad autonomous change is a multi-tenant outage or a privilege-escalation incident. Changes staged through rings with health gates and auto-rollback; JIT least-privilege access; tenant isolation; fleet-wide / privileged / destructive changes escalated.
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 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. 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.