The OpenWOP protocol v2 · cut 2026-09-05
Everything that defines OpenWOP.
Everything that defines OpenWOP (the wire contract, how it changes, its security posture, and the project behind it) is linked from this page.
Specification
The normative wire contract. v2 is the current major, cut 2026-09-05.
- v2 spec corpus the normative core documents, plus the optional extension families.
- REST API reference every endpoint with request, response, and error envelope, rendered from
api/v2/openapi.yaml. - Profiles the three named profiles a host can claim. Everything else is advertised as an individual capability.
Comparisons and positioning
Where OpenWOP sits relative to adjacent agent protocols.
- A2A vs MCP vs OpenWOP a specification-level comparison of agent-to-agent collaboration, tool/context integration, and durable workflow orchestration.
- Tool calling what tool calling standardizes, and the four surfaces OpenWOP adds on top of it: catalog, durable invocation events, fail-closed authorization, and effect idempotency.
- OpenExO 3.0 and OpenWOP an architecture thesis for using OpenWOP as the durable execution protocol beneath OpenExO 3.0, the Intelligence Stack, REWRITE, and Edge Twins.
- Overview & axioms the six axioms, the claim vocabulary, and the rule deciding what is core and what is an extension.
Conformance
How a host proves it implements the spec.
RFCs
How the protocol evolves.
Governance
Who decides what gets in, and how.
- Governance decision rules, role definitions, the sole-steward operating rules, and the conditions for moving to a cross-vendor working group.
- Maintainers who the maintainers are, and how they are added or removed.
- Contributing change rules (editorial, additive, safety fix, breaking), the checks every pull request must pass, and the DCO sign-off.
Security
What's promised, what's threat-modelled, and how to report a vulnerability.
Versioning and roadmap
What's stable, what's planned, what's tracked but not committed.
Read the paper.
OpenWOP: A Vendor-Neutral Protocol for Durable, Portable Agentic Workflow Orchestration (Zenodo, CC BY 4.0): the protocol-level argument, a reproducible cross-language portability result, and the full evidence artifact.
- Communitychannels, comment windows, and how to file an RFC
- Implementing OpenWOPthe four role-specific entry points