About UAPF.dev

UAPF.dev is the developer-facing home of the Unified Algorithmic Process Format.

Purpose

The goal of UAPF is to provide a practical, open and interoperable way to package workflows, decisions and cases into one machine-readable artifact.

UAPF.dev exists to collect the specification, tools, examples and community activity in one place, so architects and developers can adopt the format with minimal friction.

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 that 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 alongside the MAS submission.

Relationship with Algomation

UAPF was originally developed by practitioners working on algomation projects and is currently stewarded by the team behind Algomation.

Algomation provides commercial products and services built on top of UAPF, while UAPF.dev and the UAPFormat GitHub organization focus on the open standard and shared tooling.

Repository structure

The main code and documentation live in the UAPFormat organization on GitHub. The earlier prototype repository at Neksus-AI/UAPF is being migrated there.

Over time, we expect to maintain:

  • A core spec and schemas repository.
  • Language-specific toolkits (Python, Node.js, etc.).
  • Examples and domain-specific blueprints.
  • Optional registry and discovery services.

Roadmap

Planned directions for the UAPF ecosystem include:

  • Stabilizing the core specification and manifest schema.
  • Expanding language bindings and CLI tooling.
  • Publishing high-quality example packages from different industries.
  • Defining a formal governance model and, if appropriate, a foundation.

The roadmap is tracked publicly in the main repository’s issues and milestones.