Skip to content

DIRAC-ADR-0002: Platform Boundaries And Ownership

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

Context

The previous architecture content mixed platform concepts with repo-local implementation guidance. That made it hard to determine whether a statement was binding across the workspace or only descriptive for one component.

The standardization effort for dirac-* repositories requires an explicit ownership boundary so canonical decisions stay centralized and local details stay with the owning repo.

Decision

The dirac-framework repository is the platform decision authority for the dirac-* workspace.

  • dirac-framework owns canonical cross-repo ADRs, platform boundaries, and shared architectural contracts.
  • dirac-<component> repositories own implementation guidance, repo-local ADRs, and explicit override ADRs when they diverge from a canonical platform decision.
  • Architecture narrative is not authoritative when an ADR exists on the same topic.
  • Repo-local documents must reference canonical ADRs instead of restating them as independent architecture doctrine.

The primary platform responsibilities are:

  • UXI: unified user access surfaces
  • FED: API encapsulation, DTO contracts, and discoverable capabilities
  • BRO: messaging hub and event exchange coordination
  • Domain repos: bounded implementation of domain services and workflows

Consequences

  • Architecture pages in this repository should be concise background or summary material, not the primary source of binding decisions.
  • Canonical and override ADR paths become the stable MCP discovery surface.
  • Component repositories must document exceptions explicitly instead of drifting through narrative prose.
  • Future documentation cleanup should migrate decision-shaped content into ADRs before expanding architecture background.