Skip to content

Dirac Odoo Models

Document Index

Small notes: progressive architecture decisions are tracked in Architecture Decision Records; repo vocabulary is defined in Terminology. Model-shaping guidance now also includes Odoo Model Extension Strategy, including visibility regimes and CRUD baselines. The recommended reading frame for developers is now SA Design Refinement Layers, which explains the intended V0/V1/V2/V3 progression. Repo-local draft material is indexed in Working Notes so source notes remain discoverable without replacing the authoritative docs set.

Developer Note

Treat V3 as the current default for any new SA visibility scope. Older stamp-first guidance in V0 and some V2 pages remains useful for historical context and migration analysis, but it should not be expanded as the default pattern for new work. For new scoped visibility and for refactoring older stamped models, start with ADR 0003 - V3 Association-Model Migration Pattern. Read that ADR as the durable implementation contract for externalized SA scoping: native Odoo class x should normally remain unchanged, with no inverse association added merely for SA governance convenience.

Documentation Structure

  • Active Designs hold the current human-facing design narrative for SA, PA, and Odoo model behavior.
  • ADR records durable decisions that should remain stable across sessions and later refinements.
  • Reference collects stable supporting pages such as terminology and reader guidance.
  • Agent Context exists for tooling support, but appears last because this MkDocs site is primarily for human readers.

Cross-Repo Boundary

  • dirac-odoo is the developer-facing Odoo/ERP repo for inventory, sales, CRM, people, and ERP-side model semantics.
  • dirac-abs is the developer-facing ABS repo for assets, bundles, entitlements, and IoT/device workflows.
  • emob-commercial-models is the operations-facing and commercial-facing repo that defines the commercial model and SOP layer implemented through Odoo and ABS.

Use Repo Boundaries when you need the durable ownership split rather than the active design narrative.