In these docs

Context Layer for Odoo

Current limitations.

The honest edges of the technical alpha: what is experimental, unreleased, or deliberately not claimed. Read this before building on OCL so expectations match what is actually proven today.

Technical alpha · Odoo 19 Updated 2 August 2026

This is an early technical alpha. It is substantial and honest, which means being clear about its edges. None of the following is a bug; it is the current state.

Scope

  • Odoo 19 only. Community and Enterprise, stock. Odoo 17, 18, and any future version are not supported or advertised.
  • Use-case-focused kernel. 44 verified entries is a focused kernel, not complete coverage of Accounting, Sales, Inventory, or Purchase. See Coverage and release status.
  • Stock-scoped claims. Released facts are proven against stock Odoo 19. Custom modules, localizations, tenant policy, access rules, company, and currency can change the correct answer for a specific database. Resolving those is the job of the tenant overlay, which is a foundation, not a finished product.

The tenant system

  • The tenant system (overlay, memory, drift, governed memory, export and deletion audit, isolation) is an implemented local-alpha foundation, not a hosted commercial product. The hosted workflow, the review UI, production security controls, and real pilots are still ahead.

Benchmark

  • Live model runs exist, but independent blind human scoring is pending. Until it is complete and passing, there is no published accuracy figure, no chart, and no “gate passed” claim. See Benchmark methodology.

Distribution

  • The open standard is public at github.com/Nantiai/ocl-standard (Apache-2.0): the format, validator, conformance suite, reference SDKs, ten candidate example entries, and an example MCP server. See the Quickstart.
  • What is not public yet: the verified 44-entry runtime, a hosted endpoint, and the full five-operation service over real Odoo 19 data. These come with runtime access, granted directly. The TypeScript client ships as the contract but is not on npm yet.

What OCL does not promise

The hard limits

OCL is interpretation infrastructure. It does not:

  • eliminate hallucinations, or guarantee any AI answer is correct;
  • make an AI-generated write automatically safe (write-intent validation is advisory and never authorizes);
  • replace or weaken Odoo permissions, record rules, or business methods;
  • self-verify. Machine-testable rules and applicability are executed; meaning that cannot be machine-tested relies on attributable evidence or authorized review.

Naming

  • “Context layer” and “OCL” are working category labels, not a final product name. Final naming is deferred to a trademark review. OCL is an independent nanti.ai project and is not affiliated with or endorsed by Odoo S.A.

Getting access

Start today with the open standard: clone github.com/Nantiai/ocl-standard and follow the Quickstart. For the verified runtime on real Odoo 19 data, request verified runtime access; it is granted directly.