Dirac ABS

2026-04-07

Developer-facing documentation for the ABS side of DIRAC.

What This Repo Covers

• ABS service models and bundle behavior
• asset-centric workflows and entitlement logic
• IoT and device-facing coordination patterns
• integration boundaries with Odoo and the wider DIRAC stack

Reading Order

• Start with Business Overview for the platform purpose and scope.
• Read Architecture Overview and DIRAC Framework for system structure.
• Use Model Index to enter the active service-model documentation, especially BSS.
• Use Development Home for implementation guidance.

Documentation Structure

• Business frames value, market, and rollout context.
• Architecture explains the DIRAC and ABS system shape.
• Design captures durable design surfaces and model structure.
• Models holds service-model details such as BSS workflows and setup data.
• Development holds developer guidance, integration notes, and implementation references.
• ADR records durable decisions.
• Reference collects stable supporting material.
• Agent Context remains available for tooling, but appears last because this site is human-first.

Cross-Repo Boundary

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

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

Current Focus

• BSS remains the most developed model in this repo.
• Current work centers on keeping ABS design guidance aligned with the Odoo and commercial-model repos for next-stage implementation.

---

Small notes: progressive architecture decisions are tracked in Architecture Decision Records; stable lookup material lives under Reference.