Skip to content
@UAPFormat

UAPF | Unified Algorithmic Process Format

Unified Algorithmic Process Format (UAPF) Specification

Unified Algorithmic Process Format [UAPF]

Status: Draft Version 0.9 License: MIT Spec Type: Open Standard

Open standard for machine-executable enterprise processes.

Overview

UAPF (Unified Algorithmic Process Format) is an open, machine-readable standard for expressing enterprise workflows, decision logic, roles, exceptions, and multi-agent execution semantics. It enables organizations to convert human workflows and undocumented operational knowledge into explicit, portable, AI-executable algorithms—the universal algorithmization layer for modern AI-driven enterprises.

How UAPF started

UAPF was created in January 2026 while a group of industry practitioners was preparing a response to the Monetary Authority of Singapore's public consultation on AI Risk Management Guidelines. Drafting the answers exposed a gap existing methodologies and standards did not close: AI governance frameworks described the model well, but had no shared, machine-readable way to describe the process the model runs inside, the decisions it makes, and the cases it escalates to humans. Instead of inventing a new notation, we compiled the proven OMG cornerstones already trusted in regulated industries — BPMN 2.0, DMN 1.3, and CMMN 1.1 — into a single versioned, agent-readable package format. The first version of UAPF was published with the MAS submission.

Motivation

Enterprises increasingly deploy AI agents to execute business processes, but:

  • Most processes are described only in text.
  • Many operational rules live only in employees’ heads.
  • Process knowledge disappears when employees change roles.
  • Every AI agent platform uses different internal structures.

UAPF solves this by providing:

  • A universal import/export format.
  • Alignment with established international standards (OMG BPMN/DMN/CMMN).
  • AI-native capabilities (MCP, A2A).
  • Version-controllable, machine-executable models.
  • Interoperability across agents, orchestrators, and institutions.

Design Principles

  • No new modelling language: Reuses existing ISO/OMG standards.
  • Agent-native: Models include agent roles, capabilities, MCP tools, and A2A messaging schemas.
  • Interoperable: Portable across modelling tools, automation engines, and AI runtimes.
  • Composable: BPMN + DMN + CMMN + MCP + A2A → one algorithmic package.
  • Governable: Supports metadata, provenance, auditability, and compliance.

Specification Structure

A UAPF package is a zip-based container:

<process>.uapf/
  ├── manifest.json
  ├── process/
  │     ├── bpmn.xml
  │     ├── cmmn.xml
  ├── decisions/
  │     ├── *.dmn
  │     └── glossary.json
  ├── agents/
  │     ├── roles.json
  │     ├── capabilities.json
  │     └── bindings.json
  ├── integration/
  │     ├── mcp-tools.json
  │     ├── a2a-schemas.json
  │     └── api-endpoints.json
  └── metadata/
        ├── version.json
        ├── provenance.json
        └── compliance.json

Each file has a formal JSON Schema defined under /schemas.

Core Technologies

UAPF aligns with globally adopted standards:

Component Standard
Workflow BPMN 2.0 / BPMN 3.0 draft
Decision Logic DMN 1.3+
Case Management CMMN 1.1
Agent Tooling MCP (Model Context Protocol)
Multi-Agent Messaging A2A Specification
Serialization JSON Schema / XML

Validator Schemas

Schemas located in /schemas validate UAPF packages and ensure cross-platform compatibility, including:

  • uapf-manifest.schema.json
  • uapf-roles.schema.json
  • uapf-capabilities.schema.json
  • uapf-bindings.schema.json
  • uapf-mcp-tools.schema.json
  • uapf-a2a-schemas.schema.json

Example Use Cases

Government

  • Document intake → routing → approvals → archival.
  • Inter-institution coordination.
  • Automatic classification via DMN.
  • Multi-agent distribution using A2A.

Software Development (RUP/Agile)

  • Iteration workflows.
  • Design → analysis → implementation flows.
  • Agent-based code generation, testing, reporting.

Enterprise Operations

  • Procurement.
  • Compliance workflows.
  • Customer service logic.
  • Risk evaluation.

Execution Lifecycle

An AI orchestrator (e.g., LangGraph, CrewAI, AutoGen) loads UAPF as:

  1. Graph (from BPMN/CMMN).
  2. Ruleset (from DMN).
  3. Agent mapping (roles → tasks).
  4. Tool interface via MCP.
  5. Multi-agent coordination via A2A.

This enables full organizational operations to be executed by agents.

Roadmap

v1.0 Goals

  • Finalize schema versioning.
  • Add canonical examples.
  • Publish reference parser (Python/Node.js).
  • Publish UAPF Playground (web viewer).
  • Integrate Veritrust decentralized identity.

v1.1 Goals

  • Formal BPMN 3.0 agentic extensions.
  • Simulation engine.
  • Compliance and safety modules.
  • EU AI Act alignment.

License

MIT License — open standard, free to use, free to implement.

Contributions

Pull requests, issues, and proposals are welcome. Standardization direction is coordinated under the Neksus AI / UAPF working group.

Popular repositories Loading

  1. uapf-engine uapf-engine Public

    Reference execution engine for UAPF packages (HTTP API)

    TypeScript 2 1

  2. uapf-mcp uapf-mcp Public

    Reference MCP server that exposes UAPF-engine as MCP tools

    TypeScript 1 1

  3. uapf-examples uapf-examples Public

    Canonical UAPF example packages for multiple industries

    Python 1 1

  4. UAPF-specification UAPF-specification Public

    UAPF SSOT specification

    Python 1

  5. .github .github Public

    Readme

  6. uapf-python uapf-python Public

    Official Python parser & validator for UAPF packages

    Python

Repositories

Showing 10 of 13 repositories

People

This organization has no public members. You must be a member to see who’s a part of this organization.

Top languages

Loading…

Most used topics

Loading…