FAQ

This FAQ answers the questions readers most often ask while navigating the public O2A docs — what the standard is, where to start, and how the page types differ. It only restates meanings that the statement pages already fix; it never introduces new ones.

#Is O2A A Software Product?

O2A is a semantic standard. It defines meanings that products can implement. Products can express O2A through their own screens, APIs, storage, and delivery choices.

#Where Should I Start?

Start with What Is O2A, then read How To Read O2A, then Model Map for the whole surface, and use Entities to read any concept end-to-end.

#What Is The Difference Between Model Map And Concept Index?

Model Map shows how the concept families fit together. Concept Index helps you find a specific term and the page where it is defined.

#Is Contract Template Still A Current Configuration Artifact?

Reusable contract prefill is the Replicable Contract Format. O2A does not define a separate contract-template configuration artifact.

#What Is A Container Node?

A Container Node is a parent business-unit Node that contains child Nodes and owns no Offerings.

#What Is Operational Readiness?

Operational Readiness is the validated configuration basis needed before live operation. It depends on the current minimum configuration set and any relevant conditional Configuration Artifacts.

#Are Financial Views Source Truth?

Ledger Events are source financial facts. Wallet balances, Node P&L, offering cost views, and other financial views derive from Ledger Events and configuration policy.