Skip to content

DIRAC-ADR-0003: ABS Ecosystem Layering

Status: Accepted Date: 2026-03-29 Scope: Cross-repo platform decision for ABS-related architecture Supersedes: Superseded by:

Context

The ABS architecture notes describe a layered ecosystem connecting application users, applications, ABS core services, interface layers, and partner systems. That structure is useful because it defines where coordination belongs and where external systems should attach, but it was previously documented only as descriptive prose.

Decision

The ABS ecosystem is organized as a layered platform with these boundaries:

  1. Application users interact through role-specific workflows.
  2. Applications provide the interface layer for customer, operator, management, and integration use cases.
  3. ABS core owns business logic, state management, service-model governance, and event-driven orchestration.
  4. The interface layer connects the core to messaging, automation, AI, and other coordination surfaces.
  5. Partner microservices such as Odoo, ARM, and related systems attach as bounded external capabilities rather than collapsing into the ABS core.

The design principles are:

  • separation between core logic and external integration
  • messaging-hub-driven coordination
  • modular services with low coupling
  • scalable deployment posture

Consequences

  • Repositories implementing ABS-adjacent capabilities should preserve the core versus partner-service boundary.
  • External systems should integrate through defined messaging and contract surfaces rather than embedding business logic directly into the ABS core.
  • Repo-local implementation patterns may vary, but the layer boundary remains the canonical platform position.