Release Notes

This page states what the current release of O2A covers, which decisions it folds in, and which topics remain open for a future release. For the meanings themselves, use the statement pages; read this page when you need to know how settled a given area is.

#Release Scope

The current release is a first cleanup written as plain-English statements of meaning:

• This site is the O2A standard, written as normal-English statements of meaning.
• It covers entities, actions, relationships, attributes, constraints, lifecycles, configuration, and derived financial views.
• It uses semantic Configuration Artifact identifiers (the CA-XXXXXX names).

#What The Standard Governs

O2A defines meanings. It does not prescribe how a product implements them:

• O2A is a semantic reference for the structure and economics of composable organizations.
• A product, design, or software effort may use O2A meanings to build on.
• An implementation never redefines an O2A meaning; it realizes it.

#Future Standard Work

These topics remain future standard work unless a later release changes their posture. They are grouped by the role they play in the composition of agreements — extensions that strengthen O2A's expressive power without enlarging its small set of core primitives.

#Strengthening multi-party agreement

A V1 contract binds at least two party Nodes; the one structural exception is the JOINT_VENTURE variant of a Revenue Split, which atomically creates a contract-node at signing and thereby supports a hub-and-spoke shape across N participants. Two future items extend the general case beyond that special form:

• multi-party signing — direct N-party signing of any contract type, without requiring the JOINT_VENTURE special case;
• contract tags — a labelling mechanism for grouping related contracts so that a set of agreements can be reasoned about as a single composed commitment.

Together these let practitioners express compound agreements (for example, the contracts that jointly constitute a launch commitment or a revenue-sharing community across multiple units) as first-class artefacts of O2A rather than as ad-hoc bundles in the implementing product.

#Strengthening conditional behaviour

A V1 Milestone is human-attested and lives inside one contract. Two future items broaden the conditional layer:

• milestone acceptance authority by contract type — explicit rules about who may accept a milestone for each contract type, removing the current reliance on implementation-defined policy;
• Oracle trigger family activation — the second milestone trigger family already named in V1 but not yet active, enabling automated acceptance driven by an evidence source rather than by human attestation.

These items refine outcome-conditional behaviour without introducing new entities.

#Strengthening evidence and attestation

• structured SLA attestation — a defined shape for service-level evidence attached to contracts and milestones, replacing free-text terms for SLA content;
• Channel and Customer as first-class current-release entities — these concepts exist informally in V1 and would graduate to formal entities to support clearer downstream modelling.

#Querying the model

• portable query surfaces — an explicit, standardised way to query the O2A graph (for example, for financial views) so that implementations can expose equivalent reads without each defining its own retrieval API.

#What This Release Does Not Cover

Some adjacencies are deliberately not part of O2A, in this release or planned ones, and are documented here so that implementations can place them elsewhere with confidence.

• Governance framing of contracts. Operating-margin targets, evolution triggers (level-up, spin-out, royalty stepdown), exit options, and the policies that govern when contracts get renegotiated, terminated, or replaced are out of O2A's scope. They belong to the runtime layer that operates on the O2A graph, not to the structural model. O2A's small core is preserved by keeping these higher-order behaviours as policies on top of the O2A entities, attached through Milestone effects and ledger events, rather than as new model objects.
• Higher-order patterns. Composite contract patterns are compositions of the three contract primitives together with the Future Standard Work items above. They are expressed in the material that builds on O2A, not in the model itself; the standard remains expressed as primitives plus a small set of composition affordances (multi-party binding, conditional gating, tagging).