Act on it together

Workflow Routing & Gating

Move work to the right person, automatically.

When a submission arrives or a decision is made, workflow routing evaluates your rules and moves the item to the right actor — gating progress on approvals, thresholds, or role conditions before it can advance. Replace ad-hoc email chains and manual handoffs with a defined, auditable decision path.

Shape

Operational dimensions

Requires approval

Each output waits on a human decision.

Event-triggered

Fires when an upstream condition occurs.

Low data gravity

Light state; replaceable any time.

Two-way integration

Reads from and writes to external systems.

Inputs

work-item payload (form submission, case record, document)
routing rule-set (conditions, branch logic, role mappings)
actor directory (role → assignee resolution)
current routing position + prior gate history

Outputs

next-actor assignment with notification
gate verdict (proceed / hold / reject / escalate)
immutable audit log entry per gate evaluation
updated routing position on work-item

Mechanism

Routes a discrete work item along a defined decision/approval path, gating progression on rule-evaluated conditions (approver sign-off, role match, threshold, branch condition).

Why this is a primitive

Cannot be decomposed: the rule-engine that selects the next step and admits-or-blocks progression is a single indivisible operation. Without the routing-and-gating engine there is no primitive left — just a form. It does NOT carry per-instance state (that's stateful-lifecycle) and does NOT cadence a sequence over time (that's coordinated-sequencing); it evaluates 'who/what is next, may we proceed?' once per arrival at a node.

Where it shows up

HR onboarding approval chain — new hire form routes through department head → IT provisioning → payroll sign-off, each gated on the previous approver's sign-off

Contract review pipeline — legal draft routes to business unit, then legal counsel, then CFO approval, gating on redline-cleared condition at each stage

Financial exception handling — expense claim above threshold auto-routes to finance manager; below threshold auto-approves and routes to accounting system

Healthcare referral coordination — GP referral routes to the correct specialist queue based on diagnosis code, urgency flag, and availability rules

Related primitives

Composes with

Stateful Object Lifecycle →Temporal Dependency Scheduling →Multi-Role Live Operational Surface →Classificatory Inference →Explanatory Inference →Coordinated Multi-Party Sequencing →Published Surface (Documentation / Knowledge Site) →Access-Controlled Recipient Delivery →Collaborative Document Workspace →

Alternative to

Stateful Object Lifecycle →Coordinated Multi-Party Sequencing →