Model Map

This map walks the whole O2A surface at a glance and links each concept to the page where it is defined. It is a reader orientation page, not a second source of meaning — when in doubt, the linked pages govern.

O2A is read in three layers — the Definitions (the shared meanings), the Configurations an organization authors to tailor them, and the Data it records at runtime. See What Is O2A for that frame. This map covers the Definitions layer; the CA-XXXXXX Configuration Artifacts that belong to the Configurations layer are listed in their own family near the end.

#Whole Model

At the highest level, O2A is one configurable network whose meanings are shared and whose values are organization-specific:

• O2A describes an organization as a configurable network.
• The network contains organizational units, cataloged offerings, governed agreements, value-movement surfaces, evidence boundaries, setup rules, lifecycle states, actions, and derived financial views.
• The shared standard defines the meanings.
• Each organization supplies its own configuration values and runtime facts.

#Foundations

These are the principles the rest of the map rests on:

• O2A names the standard.
• Organization names the configured organizational network that uses the standard.
• A statement records one meaning, relationship, attribute, action, constraint, lifecycle, or derived financial view.
• Evidence supports decisions, transitions, corrections, and milestone acceptance.

#Organizational Structure

The shape of an organization is a rooted, acyclic tree of Nodes, classified by configuration:

• Node is the organizational unit.
• Container Node is the parent business-unit Node that contains child Nodes and owns no Offerings.
• A Node's unit type — what kind of organizational unit it is, e.g. a department, a product line, a region — comes from CA-UNITYP, the Configuration Artifact that defines the unit types an organization uses.
• A Node's lifecycle — the stages it can move through during its life as an organizational unit — comes from CA-UNILIF, or, when CA-UNILIF has not been explicitly authored, from the default single-stage basis.
• Node hierarchy is rooted and acyclic.

#Catalog And Offerings

What an organization makes available, and the commercial behavior behind it, sits in the catalog:

• Offering is something the organization makes available to others — sold, granted, or otherwise provided — recorded as a cataloged capability owned by a Node whose configuration permits offering ownership.
• An offering has an Offering Nature — the kind of thing it is, for example a subscription, a one-off product, or a usage-metered service — configured in CA-OFFNAT, the Configuration Artifact that defines the offering natures an organization uses.
• Each offering nature carries a Business Equation: the rule that describes how the offering's economics behave — how revenue is recognized, how costs accrue, what triggers value movement. Choosing a business equation is what determines an offering's economic behavior.
• CA-BUSEQU is the Business Equations component embedded in CA-OFFNAT — the set of revenue-and-cost behavior patterns that offering natures can use.
• Bundle combines offerings or capabilities while preserving component identity.

#Agreements

Commitments among Nodes are governed by contracts and their gating checkpoints:

• Contract is a governed commitment among party Nodes.
• O2A recognizes Purchase, Revenue Split, and Investment contracts.
• Replicable Contract Format is a reusable contract template — a pre-filled agreement shape — used to author new Draft Contracts without rebuilding the same structure each time.
• Milestone is a reviewable checkpoint inside a Contract.
• Contract lifecycle uses Draft, Signed, Active, and Terminated.
• Milestone lifecycle uses Pending and Reached.

#Value And Evidence

Value movement, ownership, and the evidence that supports them are recorded as source facts:

• Wallet scopes value movement.
• Ledger Event records an append-only financial fact.
• Cap Table records Node ownership allocation in basis points.
• Oracle names an evidence or trigger boundary.
• Wallet balances and P&L views derive from Ledger Events.

#Configuration

Before an organization can operate, it tailors the standard through governed setup artifacts:

• Configuration Artifact governs one setup concern.
• Operational Readiness is the validated configuration basis needed before operation.
• CA-CUSNED configures Customers & Needs.
• CA-UNITYP configures Unit Types & Hierarchy.
• CA-OFFNAT configures Offering Natures.
• CA-BUSEQU names Business Equations embedded in CA-OFFNAT.
• CA-UNILIF configures Unit Lifecycle when explicitly authored.
• CA-PLMGMT configures P&L Management.
• CA-SHRSVC configures Shared Services when shared service providers exist.
• CA-GTMACC configures Go-To-Market Access where external-client access is in use.

#Actions And Lifecycles

How objects change, and the state they move through, are stated separately but work together:

• Actions state governed business operations.
• Lifecycles state governed object progressions.
• Actions preserve the invariants of the affected concepts.
• Lifecycle transitions can require evidence, authorization, or validated configuration basis.

#Derived Financial Views

Financial meaning is never stored as truth; it is rebuilt from recorded events and configuration policy:

• Ledger Events are financial source facts.
• Wallet balances derive from Ledger Events.
• Node P&L derives from Ledger Events and configuration policy.
• Shared cost allocation is a derived calculation.
• Financial views have explicit period scope.