Composition

#How It Works

The backbone is the Node hierarchy: an organization contains Nodes, a Node can contain child Nodes, and Nodes whose archetype permits it own Offerings. Offerings can combine into Bundles. On top of that structure, Contracts bind two or more party Nodes and Milestones gate what those contracts do. Value lives on a parallel plane: Wallets scope where value moves, Ledger Events record financial facts, and Cap Tables record each Node's ownership allocation. Oracles sit at the edges as evidence or trigger boundaries.

#How It Connects

Composition names how the entities relate; each entity page is the canonical home for its own definition and rules.

• Node — the unit of structure. The organization hierarchy is a rooted, acyclic tree of Nodes.
• Container Node — the parent business-unit archetype that holds children but owns no Offerings.
• Offering — what an offer-owning Node makes available externally.
• Bundle — combines Offerings while preserving component identity.
• Contract — the agreement binding party Nodes.
• Milestone — reviewable checkpoint that gates contract behaviour without driving the contract lifecycle itself.
• Wallet — scope of value movement.
• Ledger Event — append-only financial fact; the source truth.
• Cap Table — ownership allocation among Nodes, in basis points.
• Oracle — evidence or trigger boundary at the edges of the model.
• Configuration Artifact — the governed setup units that make all of the above well-defined for one organization.

#Statements

The statements below state each rule precisely.

Structure and topology

• An organization is composable.
• An organization contains Nodes.
• A Node can contain child Nodes.
• 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 behavior.

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.

#Why It Matters

Almost every later page assumes this assembly already makes sense. Knowing that a Container Node holds children but never Offerings, or that a Contract binds party Nodes while a Milestone only gates contract behavior, is what lets the entity pages stay focused on their own rules. Composition is the map that keeps topology, catalog, agreements, and money from reading as unrelated vocabularies.