Architecture Decision Records

2026-06-18

This folder holds progressive architecture decisions for dirac-odoo.

Use numbered ADR files such as 0001-title.md, 0002-title.md, and so on.

Current ADRs

• 0001 - V1 SA Construction Model
• 0002 - ov.* Model Namespace And Semantic Independence
• 0003 - V3 Association-Model Migration Pattern
• 0004 - Fleet And Item Governance Layer
• 0005 - V3 SA-POS Governance
• 0006 - SA Access Security Foundation (Proposed)
• 0007 - Asset Registry and Component Model — Odoo Implementation (Accepted)
• 0008 - Assembly-Cell Process with SA Governance (Proposed)

Current Focus

For current implementation work, start with 0003 - V3 Association-Model Migration Pattern. For fleet/item-specific design, then apply 0004 - Fleet And Item Governance Layer. For POS retail governance, see 0005 - V3 SA-POS Governance.

Security Track (New)

ADR 0006 opens the security hardening track:

• 0006 - SA Access Security Foundation — gap analysis (5 gaps), industry pattern references (UNIX, OWASP, NIST, HashiCorp, PKI), and staged Track A (authentication) / Track B (authorization) implementation plan. Key action: add ir.rule to pos.order and ov.sa_* models (Track B, Stage 1).

That ADR now carries the repo's durable guidance for:

• two-layer SA and actor association design
• strict subset-rule enforcement
• externalized governance overlays over native Odoo classes
• the default rule that native class x should not be modified merely because SA scope exists
• engineering rationale and query-efficiency expectations for sparse association tables
• fleet/item governance through explicit fleet and fleet-membership associations when operational grouping must remain independent from physical location
• SA access security foundation: authentication (Track A) and authorization (Track B) separation, industry pattern mapping, staged hardening plan