Context Layer for Odoo
Core concepts.
The vocabulary of the context layer: entries, the three truth layers (base ontology, tenant overlay, tenant memory), the runtime assembler, context packs, contracts, and how one question becomes one small verified context.
The context layer has a small vocabulary. Learn these six words and the rest of the docs read easily.
Entry
An entry is one verified semantic fact: a claim, the evidence behind it, executable assertions that prove it, the scope it applies to, a confidence estimate, and provenance. It is the atom of the layer. The full shape is in Entry anatomy, and the different shapes of claim are in Kinds of knowledge.
The three truth layers
Meaning comes from three layers, each a different source of truth.
| Layer | What it holds |
|---|---|
| Base ontology | Verified semantics per Odoo version and module: what models and fields mean, which filters and joins are correct, which metrics are defined how, and the warnings that go with them. This is the released kernel. |
| Tenant overlay | The differences that make one database its own: detected customizations and instance quirks, proposed and then confirmed with the tenant rather than assumed. |
| Tenant memory | Confirmed business facts and prior decisions, kept with provenance and scope, and revocable. Confirmed once, never rediscovered. |
The base ontology is the released, immutable part. The overlay and memory are the tenant system, which is an implemented foundation in the alpha, not a finished hosted product. See Current limitations.
The runtime assembler
The assembler turns one question into one small context pack: the applicable facts, joins, filters, and warnings for that question, with provenance, sized for the model. It is never a registry dump. Assembly is risk-preserving: a critical warning cannot be silently dropped to fit a token budget.
question -> assembler -> context pack -> any AI (selects the smallest applicable, verified context)Context pack
A context pack is the assembler’s output: a request-scoped JSON (or text) artifact that conforms to the public context-pack schema. It is what the AI actually reads before it answers or acts. More in Context packs and offline.
Contract and applicability
Every entry declares what it applies to: Odoo versions, editions, required modules,
localizations. A contract ties a set of released entries to a guaranteed scope. Together they
are how the layer stays honest across setups: a fact proven for Odoo 19 Community with account
installed is offered only where that holds, and withheld everywhere else.
Odoo stays the authority
None of these layers replace Odoo. The context layer supplies interpretation and safety context; Odoo’s access rights, record rules, ORM constraints, and business methods remain authoritative for what is allowed and how it executes. See Security and boundaries.
How it fits together
- A connector exposes Odoo (transport).
- The assembler reads the three truth layers and builds the smallest verified context pack for the question.
- The AI reasons over that pack and the connector’s data, with fewer unsupported assumptions.
The layer never moves data and never reasons. It supplies meaning to whatever does.