UAPF — Unified Algorithmic Process Format — packages BPMN workflows, DMN decision tables and CMMN case logic into a single, portable artifact that humans, workflow engines and AI agents can all read and execute.
Enterprise processes live across dozens of tools, documents and tribal knowledge. When an AI agent needs to understand "how we handle a permit application" or "what approves a credit request", there is no single source of truth to point to.
BPMN diagrams sit in Visio, DMN tables in spreadsheets, case models in Word documents. No single artifact represents a complete process.
Engines and integrations rely on conventions and ad-hoc glue code. Process interfaces are undocumented and impossible to version.
Large language models and AI agents need explicit, machine-readable definitions — not natural language descriptions — to reason about and execute complex workflows.
UAPF does not invent new notation. It acts as a container and contract for the three OMG standards that together express any enterprise process.
Sequence flows, tasks, gateways, events and sub-processes. The backbone of how work moves from start to finish.
Decision requirement graphs and decision tables that encode eligibility, scoring and classification rules in a machine-executable form.
Discretionary tasks, milestones, sentries and case file items for work that cannot be fully pre-defined — human judgement included.
A UAPF package is a directory (or ZIP archive with .uapf extension)
with a typed manifest and organized model folders. Simple to create, easy to validate.
Typed metadata: package ID, name, version, UAPF level (1–4), which cornerstones are active, file paths, owners and lifecycle state. Validated by JSON Schema.
Every process, decision, case, task and event has a stable URI-based ID that engines, registries and AI agents can reference unambiguously.
Semantic versioning, optional signing and lifecycle status (draft → active → deprecated) make packages governable across environments.
Progressively richer capabilities: Level 1 = BPMN only. Level 2 adds DMN. Level 3 adds CMMN. Level 4 adds resource mapping and agent interfaces.
A UAPF Engine exposes packages over the Model Context Protocol (MCP), giving AI agents structured, authenticated access to process definitions, decision rules and runtime execution — without natural language ambiguity.
Public specifications, open-source reference implementations and a governance model that any organization can participate in. No lock-in.
UAPF builds on BPMN 2.x, DMN 1.3+ and CMMN 1.1 — OMG standards with decades of tooling — rather than inventing proprietary notation.
Every UAPF package is intended to be executed by a compatible engine and invoked by AI agents, not stored as static documentation.
Semantic versioning, optional signing, lifecycle status and stable identifiers make it possible to control, audit and approve every change.
Clone the reference repository, validate an existing manifest, or dive into the specification. UAPF is stewarded by Algomation and open to contributors.