ADR 019 Directus Content Administration
Context
Section titled “Context”ADR 008 selected Strapi, but current assembly manifest and stage topology configure Directus. Keeping Strapi accepted would document a service that current architecture does not use.
Decision
Section titled “Decision”Use Directus as editorial content-administration surface.
- Directus owns editorial CRUD, media administration, and operator authoring UX.
- Supabase Postgres remains primary content data store.
- Supabase Storage remains content asset store.
- Backend domain/application slices own publication lifecycle, visibility, validation, audit, and business-trigger decisions.
- Frontend consumes backend contracts; it does not depend on Directus internals.
- Directus metadata and configuration do not become duplicate domain authority.
Implementation Evidence
Section titled “Implementation Evidence”Current stage observation supplied during audit includes Directus container.
Pinned repository evidence confirms configuration. This audit did not verify
editorial workflows, schema bootstrap, storage writes, or deployment health, so
implementation remains partial.
Consequences
Section titled “Consequences”Strapi references are historical. Content behavior missing from backend contracts cannot be implemented as frontend or Directus-only business logic.
Revision History
Section titled “Revision History”- 2026-07-10: accepted; supersedes ADR 008.