Workflow automation for work that has to be done right.
Draw the process. Publish it. Run it.
Aegis Magnum Labs builds one engine for governed work: a designer for the form, a state machine for the steps, and a record that remembers every decision. Someone who owns the process composes it. Publish it, and it runs.
Proposed by the system, decided by people.
Built in Canada.
- Passed: Every state reachable from Draft
- Passed: Approved and Closed are terminal
- Passed: Approve is bound to the Approver lane
- Warning: Returned has no clock; the requester can wait forever
- Passed: Four-eyes: the approver is not the reviewer
The workflow designer, with the lint panel that checks a definition while it is drawn. What it accepts is what the publish gate accepts.
One platform, four parts
A form designer, a workflow designer, the engine that runs what they publish, and an assistant that proposes but never decides. Every product line is built from the same four parts.
The form, as a definition
Form Designer
Fields, sections and help text, with sections that show, hide or lock depending on the step the record is in.
The person who owns the process builds the form: fields grouped into sections, help text where people hesitate, and the policy header your records already carry on paper.
Request
editable in the Requester laneIndependent review
hidden until SubmittedApproval
locked after ApprovedThe steps, drawn and checked
Workflow Designer
States, transitions and lanes on a diagram your reviewers can read, with a lint panel that checks the definition while you draw it.
Name the states a record can be in and the moves between them. Give each move a lane, so it is clear who acts, and bind it to a capability where the process needs a guard.
- Passed: Every state reachable from Draft
- Passed: Approved and Closed are terminal
- Passed: Approve is bound to the Approver lane
- Warning: Returned has no clock; the requester can wait forever
- Passed: Four-eyes: the approver is not the reviewer
The framework that runs it
Workflow Engine
A versioned, guarded, role-checked state machine with a full audit trail, running inside your own application, against your own database.
Every record carries its definition version, its current state and an append-only history of every move: who, when, in which lane, and why.
| When | Lane | Moved to | By |
|---|---|---|---|
| Tue 8 Sep, 09:12 | Requester | Submitted | R. Osei |
| Tue 8 Sep, 14:40 | Reviewer | In review | M. Chen |
| Thu 10 Sep, 11:05 | Reviewer | ReturnedMissing drawing reference. | M. Chen |
| Thu 10 Sep, 16:22 | Requester | Submitted | R. Osei |
| Mon 14 Sep, 09:00 | System | EscalatedNo action for 5 business days; escalated to the unit head. | clock |
| Mon 14 Sep, 10:31 | Approver | ApprovedFour-eyes satisfied: the approver is not the reviewer. | A. Okafor |
AI that augments, and never decides
Assist
Assist proposes a classification, a routing, a follow-up or a draft. It shows its sources and how confident it is. A person decides.
A proposal is a first-class object in the record: what was suggested, on what evidence, with what confidence, and what the person did with it.
Classify as a temporary modification with a restore-by date of 30 days, route to the Reviewer lane for independent review, and open a follow-up for the affected procedure.
- Based on
- the request text, the change type definition, and the last two records of this type.
- Confidence
- High
How it works
Three parts, in the order you would do them.
Step 1: Design the form
Choose the fields, group them into sections, and decide which sections show, hide or lock at each step. Add the help text people need and the policy header your records already carry.
Step 2: Draw the steps
Name the states a record can be in and the moves between them. Give each move a lane, so it is clear who acts, and guards such as four-eyes or not-the-prior-actor where the process needs them. Add a clock where the process has one.
Step 3: Publish, then run
A check reads the whole definition first and refuses unreachable steps, dead ends and approvals with no approver. Published versions never change. Records already in flight finish on the version they started.
Built into products
The same four parts, applied. Each product line is a portfolio of processes already running as published definitions.
Change management for regulated operators
Praxis
The library, for teams building their own governed applications
Workflow Designer
Health and safety, as an application on the engine
Aegis
Case management for support and service teams
Iatros
Designed to the standards our customers are held to
We design to SOC 2 and the other frameworks regulated organisations are measured against, and we say so in posture language, never as a certification we do not hold.
If it has a form, steps, a decider and a clock, it fits.
Proposed by the system, decided by people. Bring the form and the approval chain you have today; we will show it running.