Register 0042Chain verifiedSoD · on

Agents run the process. A human signs the step you can't undo.

Import your BPMN or draw the process. Reversible steps run on their own; every irreversible one waits for a signer with the right role — and every signature lands in a hash-linked log anyone can verify.

Start a workspaceTalk to usHow a run is governed →
WhenProcessStepWhoHash
10:41:07Refund approvalOrder #8812 checked against the policy · autoagenta91f…c20e
10:41:08Refund approvalFraud score 0.12 — low blast, reversible · autoagent5d03…7b41
10:41:09Refund approvalIssue refund $1,240 — irreversible, parked awaits a manager—
See it

Three screens, three promises.

The console as it runs today, with sample data for a fictional company.

The Minctrl sign-off queue for a payroll gate: a countdown to its deadline, who may sign (admin, manager, owner), the approve step marked irreversible, and a Deny decision that asks for a required reason.
Sign-off queueEach gate says who may sign and when it is due — and a denial cannot be signed without a written reason.
The Minctrl process canvas for a payroll process: a high-risk human gate labelled “run approved” leads into the irreversible step “Fund net pay via ACH”, under a banner reading Governance-clean.
Process canvasA human gate stands directly before the step that can’t be undone, and the editor checks it as you draw: governance-clean.
The Minctrl audit log after pressing Verify chain: the status reads “chain intact”, above the list of entries — signed gates with who signed and in which role, including a denial with its written reason.
AuditPress Verify chain: every hash is recomputed, and the log answers chain intact — or names the first broken entry.
How it works

Three rules decide every step.

The gate resolver reads two facts from each step — its blast radius and whether it can be undone — and routes it.

§1

Reversible work runs itself

An agent step with a low blast radius and a reversible action auto-runs once its confidence clears the floor (0.70 by default). Below the floor the run parks for a person.

§2

An irreversible step waits for a person

A payout, a filing, a block — any step that can’t be undone stops at a human gate. Medium-risk reversible steps go to a panel of judges first; an inconclusive panel parks too.

§3

The signature is evidence

Who signed, which verdict, against which exact graph: the run is pinned to the hash of the process it started on, and the decision joins the audit chain in the same transaction.

Signers

The right person signs — and never the same person twice.

RoleSigns a gateAlso
OwnerYesTurns separation of duties on or off — audited
AdminYesChanges company policy — audited
ManagerYesWorks the sign-off queue
MemberNoStarts runs, reads the trail
Separation of duties
gate  credit_check   signed  a.lee   · manager
gate  final_payout   a.lee           · manager
      → 409  a different person must sign this gate
gate  final_payout   signed  m.ortiz · manager  ✓

On by default for every company. One person cannot sign two different gates of the same run; the API refuses it, not just the UI.

Audit

An audit log that checks itself.

Each entry carries the SHA-256 of the one before it. Edit or delete any historical entry and verification names the first broken link.

Verify

GET /audit-chain/verify returns valid, the length and the first broken entry.

Export

Hand the whole chain to an auditor as one artifact; they can recompute every hash themselves.

Per run

Every run shows its own entries — who started it, who signed each gate, what ran.

Bring your process

Your process, not our template.

A new workspace starts empty. You bring the process you already run.

BPMN 2.0

Import from Camunda, Signavio or Bizagi

Preview the governed graph and every violation before anything is stored; save it as a versioned process. Export writes it back out without loss.

JSON

A portable, hash-checked file

A minctrl.process/v1 export carries the hash of the graph it becomes. A file edited after review is refused on import.

Canvas

Draw it, or describe it

Start from a blank canvas, or describe the process in a sentence and review the draft. The governance check runs as you edit.

API

Everything in the console is the REST API.

Import · run · sign
curl -X POST $API/process-templates/import-bpmn \
  -H "Authorization: Bearer $TOKEN" \
  -d '{"xml": "<bpmn:definitions…>", "save": true,
       "slug": "refund-approval"}'

curl -X POST $API/process-runs \
  -H "Authorization: Bearer $TOKEN" \
  -d '{"vertical": "refund-approval", "draft": true,
       "inputs": {"order": "8812"}}'
# → {"status": "awaiting_human", "parked_at": "signoff", …}

curl -X POST $API/process-runs/$RUN/resume \
  -H "Authorization: Bearer $MANAGER" \
  -d '{"gate": "signoff", "decision": "approved"}'

Bearer-token auth, an OpenAPI schema at /openapi.json, Python and TypeScript SDKs. Connectors bind a step's tool to your own HTTP API, per company.

A resume by someone without the signing role is refused with 403; a second signature on a gate already cleared, with 409.

API reference →
Talk to us

Not ready to start? Ask first.

Tell us which process you want to put behind a signature. Write to [email protected].

Questions

Questions

What does Minctrl do?

It orchestrates business processes. Agents run the steps that are safe to run on their own; any step that cannot be undone waits for a person with the right role, and every decision is written to a hash-linked audit log.

Do I have to rebuild my processes?

No. Import a BPMN 2.0 model from Camunda, Signavio or Bizagi, or a Minctrl JSON export. The import shows every governance violation before anything is stored.

Can an agent approve an irreversible step?

Not by default. High-blast or irreversible steps always wait for a person; allowing AI clearance there needs an explicit setting and a 0.95 confidence floor, and it is off out of the box.

Who can sign a gate?

Owners, admins and managers. Members can start runs and read the trail. With separation of duties on — the default — one person cannot sign two different gates of the same run.

How does an auditor check the log?

Each entry stores the SHA-256 of the previous one. The verify endpoint recomputes the whole chain and reports the first broken entry; the export lets an auditor recompute it independently.

What happens if I change a process while a run is in flight?

Nothing changes for that run. A run is pinned to the hash of the graph it started on and resumes on exactly that graph.

Next entry

Put your first process on the register.