Changelog

This is a real, dated record of what has shipped. The API is v0.1 and path-unversioned (see Versioning below and the versioning reference). No version numbers are claimed here beyond v0.1 — the entries below describe the actual work.

v0.1 — 2026-07-02

The first coherent release of the governed-orchestration platform: an engine that runs a process to a human gate, parks, and resumes on a signed verdict — with every irreversible side effect held behind a connector you opt in to.

Governed run engine + park/resume

• Durable process runs. A run executes a vertical's flow until it reaches a human gate, then parks (status: awaiting_human) and persists. It resumes when a resume signal arrives carrying the gate's step-id and the human's decision, which is merged and the flow re-driven idempotently. See Concepts and Run a governed process.
• Exclusive / parallel gateways in flows route on the recorded verdict, so a single gate decision (e.g. approved, SAR signed, sanctions hit confirmed) steers the run down the correct downstream branch.

User-configurable HTTP connectors, shadowed until signed off

• Bring-your-own connectors. Steps map to HTTP connectors you configure per step, so a step can call your real systems of record.
• Shadow-until-signed-off. Irreversible steps (reversible: false) run shadowed (dry-run) by default and only fire for real once (a) the connector is deliberately opted in and (b) a human gate upstream has collected a signed verdict. Governance is the default, not an add-on. See Connect a step and Configure gates and autonomy.

BPMN 2.0 import/export

• Round-trip BPMN 2.0. Import an existing BPMN 2.0 process and export Minctrl flows back out, so the governed flow lives alongside the notation your organization already uses. See Import / export BPMN.

45 governed flows across 11 verticals

• 45 process templates ship, spanning 11 domains — fintech, finance, healthcare, HR, insurance, IT, legal, logistics, security, supply-chain, and telecom. Each is a real end-to-end flow with primary-source steps, exclusive/parallel gateways, human gates, and an irreversible-execute step held behind a gate. Runnable examples live in the Cookbook.

Docs site

• This documentation site launched — quickstart, tutorials, guides, cookbook recipes, concepts, an API reference generated from the OpenAPI schema, and the two SDKs generated against that same schema.

---

Versioning

The API is v0.1 and path-unversioned — there is no /v1 prefix in the URL; you call /process-runs, /auth/*, and so on directly. While the API is at v0.1 it should be treated as pre-1.0: the surface can still change as endpoints are hardened.

How breaking changes will be communicated. Until a stable v1.0 is cut:

• Every breaking change is recorded here in the changelog, dated, with a note on what moved and how to migrate.
• Additive changes (new endpoints, new optional fields, new verticals) are not treated as breaking and may land at any time — the generated SDKs surface them automatically.
• When the API stabilizes, a versioning scheme and deprecation policy will be published in the versioning reference before anything is removed.