Skip to main content

UAICP v0.3 Is Live: Reliability Contract for Agentic Workflows

· 2 min read
UAICP Team
Core Maintainers

Agentic systems are moving from conversational assistance to autonomous workflow execution where model outputs can trigger real-world side effects.

This creates a critical gap: while models are probabilistic, production workflows demand deterministic control.

UAICP addresses this gap by defining standard reliability controls that are enforceable in runtime code, regardless of orchestration framework.

Why UAICP Matters

Prompting an LLM to "use tools carefully" is not a safety mechanism. Frameworks like AutoGen, CrewAI, LangGraph, and the OpenAI Agents SDK are powerful orchestrators, but production reliability requires explicit gating semantics.

Common failure modes include:

  • skipped tool calls or stale context assumptions
  • responses delivered without concrete evidence
  • unverified high-risk writes to production systems
  • no replayable audit trail showing how decisions were made

UAICP standardizes the minimum contract required for trustworthy execution.

Core Reliability Capabilities

UAICP enforces:

  • Deterministic state transitions: INTAKE -> PLANNING -> EXECUTING -> VERIFICATION -> DELIVERY
  • Evidence-gated delivery: outputs cannot be delivered without required evidence
  • Verifier checks before delivery: required checks must pass before finalization
  • Policy-gated writes: high-risk writes require explicit policy clearance and rollback coverage

What Ships Today

Protocol version:

  • v0.3 contract, including parent_trace_id, safe partial streaming boundaries, and rollback_action requirements for write_high_risk.

Published packages (latest patch release 0.3.1, published February 26, 2026):

  • TypeScript: @uaicp/core, @uaicp/adapter-langgraph
  • Python: uaicp-core, uaicp-adapter-autogen
  • Rust: uaicp-core, uaicp-adapter-rig

Adapter validation:

  • 52 passing adapter tests across TypeScript, Python, and Rust implementations.

What UAICP is Not

UAICP is not another execution framework. It is a protocol contract and implementation pattern designed to sit under your existing orchestrators.

Implementation Path

To start implementation:

Get Involved