The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the OCL Context Layer listing page.
OCL is an experimental open format for giving AI systems structured, scoped, and verifiable business meaning for Odoo.
An Odoo connector explains how to reach records. An OCL context pack explains what relevant records and fields mean, which tempting interpretations are wrong, what ambiguity must be resolved, and which safety boundaries still apply.
Choose the surface that fits your product:
| Route | Call | Benefit | Alpha availability |
|---|---|---|---|
| MCP for AI agents | get_context, resolve_noun, explain_field | Put scoped Odoo meaning directly in an agent's tool loop | Public example or invitation runtime |
| CLI | get-context "What is revenue?" | Inspect a context pack and its warnings immediately | Public examples now |
| Python validator | validate_entry(entry, schema) | Read and produce interoperable OCL documents | Available now |
| TypeScript integration | Five production operation shapes | Connect a product to the verified hosted runtime | Source alpha and invitation runtime |
Clone and try the context behavior:
The result asks which revenue definition applies and returns the paired warning
against treating account.move.amount_total as universal revenue.
This local server demonstrates the real OCL tool contract using ten public candidate examples. It is not the commercial Odoo 19 runtime.
See Using OCL for the integration flow, MCP calls, CLI commands, SDK examples, response handling, and current access boundary. Connector and MCP implementers should freeze against the connector runtime contract and its conformance fixture. Hosted runtime clients can follow the verified alpha call guide. Developers can first try one live verified decision, then start a scoped seven-day trial without GitHub, package installation, Odoo credentials, or customer data. The GitHub request and email paths remain available as fallbacks.
This repository contains the open interoperability layer:
It does not contain nanti.ai's commercial registry, production assembler, verification harness, source fingerprints, private benchmarks, tenant overlays, memory, or unreleased ontology candidates.
Version 0.1.0 is an experimental technical alpha. The format can change while
independent implementations test it. The examples demonstrate the format; they
are not the commercial verified registry and do not carry a lifetime guarantee.
Odoo 19 is the only current stock-version focus.
Developers can now clone the standard, run conformance, integrate the example MCP server, and report an independent implementation. See the developer alpha guide.
The public alpha is an interoperability surface, not free bulk access to the
commercial verified registry. A bounded verified runtime is live at
https://api.context.nanti.ai; its native form immediately issues a scoped,
expiring evaluation key.
Facts do not become verified because an LLM wrote plausible JSON. A conforming document describes evidence and assertions. A registry operator separately decides which verification policy is sufficient for a release claim.
Odoo is a trademark of Odoo S.A. This project is independently developed and is not affiliated with or endorsed by Odoo S.A.
The open repository is licensed under the Apache License 2.0. The commercial OCL registry and services are separate and are not distributed by this repository.