When a workflow, actor label, or system term changes, update both the markdown explanation and the referenced diagram source.
Prefer editing .puml sources rather than only touching rendered image outputs.
BSS and Odoo integration terminology should stay aligned with related DIRAC repos when cross-repo terminology decisions have already been made.
Use PA as the current portal-app language. Treat OVApp as legacy wording
unless historical reference is required.
Use service model for runtime ABS behavior. Reserve service template for
commercial packaging in emob-commercial-models.
Treat Odoo business transactions as the entitlement and pricing source of
truth. ABS enforces and substantiates entitlement through physical and IoT
operations.
Do not introduce a separate ABS-owned asset affiliation model while Odoo-side
asset anchoring is based on stock and inventory constructs.
Keep the system split explicit:
dirac-abs owns ABS asset, bundle, entitlement, and IoT/device behavior.
dirac-odoo owns Odoo ERP-side transaction, inventory, sales, and people semantics.
emob-commercial-models owns operations-facing commercial framing and SOP guidance built on top of both systems.
Treat docs/reference/repo-boundaries.md as the stable reader-facing summary of
that split.