Skip to content

Capabilities

Repo Purpose

  • Maintains developer-facing design documentation for dirac-odoo.
  • Focuses on Odoo-centric ERP behavior: inventory, sales, CRM, people, governance boundaries, and custom ov.* model extension strategy.
  • Explains how serviced-account (SA) and portal-app (PA) governance interacts with native Odoo objects and custom Odoo models.

Cross-Repo Positioning

  • dirac-odoo is the developer-facing ERP/Odoo repo.
  • dirac-abs is the developer-facing ABS repo for asset, entitlement, bundle, and IoT/device behavior.
  • emob-commercial-models is operations-facing and commercial-facing, defining the commercial model and SOP layer that developers implement through Odoo and ABS.
  • Durable boundary guidance is summarized in docs/reference/repo-boundaries.md.

Main Knowledge Areas

  • docs/ Human-facing design pages for SA, PA, and Odoo model behavior.
  • docs/adr/ Durable design decisions for this repo.
  • docs/terminology/ Canonical vocabulary used across the repo.

Change Boundaries

  • Prefer editing the most specific design page rather than patching summaries.
  • Keep Odoo ERP semantics explicit and distinct from ABS asset semantics.
  • Keep terminology aligned with related repos when cross-repo terms have already been normalized.