Dirac Odoo Models¶
Document Index¶
- SA Design Refinement Layers
- Serviced Account Mini Model
- Odoo Model Extension Strategy
- PA SA Context and Attribution Model
- SA Contact Model
- SA Member Hierarchy and Manager Operations
- Terminology Reference
- Architecture Decision Records
- Reference
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 progression.
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-odoois the developer-facing Odoo/ERP repo for inventory, sales, CRM, people, and ERP-side model semantics.dirac-absis the developer-facing ABS repo for assets, bundles, entitlements, and IoT/device workflows.emob-commercial-modelsis 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.