Scaffold directus service planning structure
Initial commit. Establishes the .planning/ tree mirroring processor's
shape (ROADMAP.md as nav hub + per-phase folders with READMEs and
granular task files).
Six phases:
1. Slice 1 schema + deploy pipeline — what Rally Albania 2026 needs.
Org catalog (orgs, users, vehicles, devices) + event participation
(events, classes, entries, entry_crew, entry_devices). db-init/
for the positions hypertable + faulty column. snapshot/apply
tooling. Gitea CI dry-run. Dogfood seed of Rally Albania 2026.
Nine task files with full Goal / Deliverables / Specification /
Acceptance criteria / Risks / Done sections.
2. Course definition — stages, segments, geofences, waypoints, SLZs.
PostGIS extension introduced here.
3. Timing & penalty tables — co-developed with processor Phase 2.
entry_segment_starts, entry_crossings, entry_penalties,
stage_results, penalty_formulas.
4. Permissions & policies — Directus 11 dynamic-filter Policies per
logical role. Deployment-time work, deferred to keep early phases
focused on the data model.
5. Custom extensions — TypeScript hooks/endpoints implementing the
cross-plane workflows the schema implies (faulty-flag → Redis
stream emit, stage-open materializer, etc.).
6. Future / optional — retroactivity preview UI, command-routing
Flows, audit trails, federation rule import. Not committed.
Non-negotiable design rules captured in ROADMAP.md: schema authority
in Directus + snapshot-as-code + db-init for non-Directus DDL +
sequential idempotent migrations + entrypoint apply order + no
application logic in Flows + permissions deferred to Phase 4.
Architectural anchors point at the wiki at ../docs/wiki/ — the schema
draft, the Rally Albania 2025 source page, plus the existing
processor/postgres-timescaledb/live-channel pages. Each task file
calls out the wiki refs an implementing agent should read first.
README.md mirrors the processor service README structure: quick start,
local Docker test, prod/stage deployment notes, env vars, CI behavior.
julian
a8e808e71c