Organization

#How It Works

An Organization is composable: it contains Nodes, and the Node hierarchy is rooted and acyclic, with the root itself being a Node rather than a separate abstract container. Offerings hang off the Nodes whose archetype permits ownership, Bundles compose Offerings, Contracts bind party Nodes, and Milestones gate contract behaviour. On a parallel plane, Wallets scope value movement, Ledger Events record financial facts, Cap Tables record ownership allocation, and Oracles sit at the edges as evidence or trigger boundaries.

The standard defines what each of these pieces means as a set of plain-English statements; an Organization is the configured realization of those meanings. Different implementations may realize the same standard differently while remaining legible against the same vocabulary.

#How It Connects

An Organization sits above every other entity in the model. Each piece below is a separate page; this section names the relationship.

• Node — the structural unit. The Organization is the rooted tree of Nodes; its root is itself a Node.
• Container Node — the parent business-unit archetype that contains child Nodes and owns no Offerings.
• Offering — what Nodes (whose archetype permits it) make available; the catalog of an Organization.
• Bundle — composes Offerings while keeping component identity.
• Contract — binds party Nodes; the agreement layer.
• Milestone — reviewable checkpoint that gates contract behaviour.
• Wallet — scopes value movement; one of the surfaces where the Organization's money sits.
• Ledger Event — append-only financial fact; the source truth all financial views derive from.
• Cap Table — records each Node's ownership allocation in basis points.
• Oracle — names an evidence or trigger boundary at the edges of the model.
• Configuration Artifact — the governed setup units (CA-XXXXXX codes) that tailor O2A to one Organization before any of the above carries meaning.

#Statements

The statements below fix the compositional rules that hold an Organization together.

Structure and topology

• An Organization is composable.
• An Organization contains Nodes.
• A Node can contain child Nodes.
• The Node hierarchy is rooted and acyclic.
• The organization root is itself a Node at the top of the hierarchy.
• A Node whose archetype permits offering ownership can offer Offerings.
• A Container Node contains child Nodes and does not own Offerings.

Catalog

• An Offering can participate in Bundles.

Agreements and gating

• A Contract binds party Nodes.
• A Milestone gates contract behaviour.

Value and ownership

• A Wallet scopes value movement.
• A Ledger Event records a financial fact.
• A Cap Table records node ownership allocation.

Evidence boundary

• An Oracle represents an evidence boundary or trigger boundary.

Portability

• The standard defines the shared meanings; an implementation realizes them.

#Why It Matters

Organization is the outermost frame that lets every other concept read consistently. Without it there is no shared root for the Node hierarchy, no scope for catalog and contracts, and no boundary for the configuration that tailors the standard to one specific operating context. Get the frame right and topology, money, and agreements all line up underneath it.