What Is O2A

A shared language for describing how composable organizations are structured, governed, and made financially readable.

Operational ontology for enterprise architecture

O2A stands for Open Organization Alliance and it is an operational ontology for enterprise architecture published and maintained by Boundaryless SRL (boundaryless.io).

O2A represents a shared language to describe the structure, the agreements and the economic behaviour common in modular, composable organizations in a form that humans and computational agents can both read.

O2A describes the irreducible elements, properties, and interactions of a form of organization that overcomes the traditional limitations of functional and matrix organizations — towards organizations made of composable modules and autonomous units, largely coordinated through node-to-node contracts and shaped by investments and customer value rather than top-down management.

As a standard it's formalized in a canonical format in the form of prose and semantic triplets and wants to enable the creation of both conceptual and software interfaces for computational agents and humans to cooperate, to facilitate better decision-making in an organization at scale.

The Three Layers

O2A separates three things that are often conflated. Each has a different scope and a different lifecycle, and the rest of the standard follows from keeping them apart.

1 — Definitions (scope: the standard). The shared semantic meanings O2A defines: a small set of entities and the rules that bind them. An organization is a composition rather than a monolith — a tree of Nodes (teams, business units, subsidiaries) that own Offerings, bind one another through Contracts, gate behaviour with Milestones, move value through Wallets, and record it as Ledger Events. These definitions are universal: every organization reading O2A reads the same ones. Model Map walks the whole surface.

2 — Configurations (scope: one organization). How one organization tailors the universal definitions to itself, by authoring Configuration Artifacts — the CA-XXXXXX setup units that record its unit types, its customers, the natures of its offerings, its financial governance. The shape is fixed by the standard; the values are the organization's. See Configuration.

3 — Data (scope: runtime). The runtime operational facts — the actual Nodes created, Contracts signed, Ledger Events recorded. Data carries meaning only once the configuration that governs it has been validated, which is why configuration comes before operation.

O2A defines the first two layers — the definitions and the configuration grammar — and the meaning the third must satisfy. It does not prescribe the software that implements them: different products and stacks can realize the same standard and stay interoperable because they share the same definitions. The standard is declarative and expressed as atomic semantic statements, so it can be executed as code while staying maintainable as prose.

What O2A Defines

Within the first layer, O2A draws an explicit boundary around what it covers:

  • entities such as Nodes, Offerings, Contracts, Milestones, Wallets, Cap Tables, Ledger Events, Oracles, and Configuration Artifacts;
  • the relationships and attributes those entities carry;
  • governed action meanings and lifecycle states;
  • configuration dependencies and readiness rules;
  • invariant constraints and derived financial-view semantics.

Why It Matters

O2A is a semantic standard that allows composable organizations to describe their organizational units (i.e., Nodes), the relationships between them, and the Contracts and agreements that bind them. It also describes the value flows each organizational unit contributes to — from individual Offerings to the more complex value propositions formed when multiple Offerings are bundled together.

The standard can be used as a purely descriptive surface for strategy and organization-design activities, but it is at its strongest in the creation of software interfaces that let humans and agents consume and produce data to align organizational topology with the resources and opportunities available in the ecosystem.