Skip to content

Capabilities

Repo Purpose

  • Maintains the ABS platform documentation set within the DIRAC framework.
  • Captures architecture, business framing, model specifications, integration patterns, and operational diagrams.
  • Acts as a documentation source for BSS workflows, Odoo integration behavior, and related setup examples.
  • Is primarily developer-facing: implementation guidance for asset-centric services, IoT/device coordination, entitlement logic, and ABS-side workflow behavior.

Cross-Repo Positioning

  • dirac-abs focuses on ABS service models, bundles, asset lifecycle concerns, and IoT/device-facing workflow logic.
  • dirac-odoo focuses on Odoo-centric ERP implementation: inventory, sales, people, CRM, and governed ERP object behavior.
  • emob-commercial-models is operations-facing and commercial-facing. It defines the rollout, SOP, pricing, and product/bundle operating model that developers then implement through ABS and Odoo.
  • Durable boundary guidance is summarized in docs/reference/repo-boundaries.md.

Main Knowledge Areas

  • docs/architecture/ Source for ABS platform and DIRAC ecosystem architecture framing.
  • docs/models/ Source for service-domain models, especially BSS design intent, setup data, and tests.
  • docs/diagrams/ Source for PlantUML and rendered diagrams referenced by the written docs.
  • docs/development/ Source for implementation, integration, messaging, and schema guidance.

Context Entry Points

  • Human overview: README.md
  • Documentation home: docs/index.md
  • Model entrypoint: docs/models/index.md
  • Repo-local guidance: docs/context/workflows.md and docs/context/contracts.md

Change Boundaries

  • Prefer updating the canonical markdown doc that explains a concept before adjusting downstream summaries.
  • Keep PlantUML sources aligned with the terminology used in the corresponding design-intent documents.
  • Treat generated MCP context under docs/agent/ and docs/context/ as repo-retained guidance, not disposable scratch output.