julian
52524eb72d
Five collections + 10 relations + 5 composite unique constraints,
captured into snapshots/schema.yaml (now 105 KB, up from 53 KB).
Collections:
- events — 11 fields incl. organization_id M2O, discipline enum
(rally / time-trial / regatta / trail-run / hike),
starts_at/ends_at required.
- classes — 8 fields incl. event_id M2O, code unique within event.
- entries — 11 fields incl. event_id/vehicle_id (nullable for foot
races) /class_id M2O, race_number, status enum with
8 lifecycle values, archive on `withdrawn`.
team_id deliberately omitted (Phase 2+).
- entry_crew — junction with role enum
(pilot/co-pilot/navigator/mechanic/rider/runner/hiker).
- entry_devices — junction with optional assigned_user_id (panic button
body-wear); ON DELETE SET NULL on that field since
user removal shouldn't block the device record.
10 M2O relations wired, all ON DELETE RESTRICT except
entry_devices.assigned_user_id (SET NULL).
db-init/005_event_participation_unique_constraints.sql adds composite
UNIQUE on:
events (organization_id, slug)
classes (event_id, code)
entries (event_id, race_number)
entry_crew (entry_id, user_id)
entry_devices (entry_id, device_id)
---
Destructive-apply incident (recovered):
First attempt at this task hit a real foot-gun. After creating the 5
collections via MCP, we ran `compose build && up -d`. The image rebuild
baked in the snapshot from task 1.4 (only 7 collections). Boot's
schema-apply step ran `directus schema apply --yes` against that stale
snapshot — saw the 5 new collections in the DB but not in the snapshot
— DELETED THEM, taking the constraints with them.
Recovery: re-created the 5 collections + 10 relations via MCP, ran the
ALTER TABLE statements directly via psql to restore the constraints,
ran schema:snapshot BEFORE any further restart so the YAML reflects
the live state. Documented the operator rule (never rebuild with
uncommitted schema changes) inline in the task spec and in the
directus wiki entity page (separate commit in trm/docs).
Phase 3 hardening on the radar: DIRECTUS_SCHEMA_APPLY_MODE env var
with auto/dry-run/skip modes so dev environments default to non-
destructive behavior.
ROADMAP marks 1.5 done. Phase 1 progress: 7/9 tasks complete (1.1–1.7);
1.8, 1.9 remain.
8.6 KiB
directus — Roadmap
The TRM business plane. Directus 11 instance owning the relational schema and exposing it via REST/GraphQL/WebSockets/Admin UI. Schema-as-code via snapshots/ + db-init/, applied at container startup.
This file is the single navigation hub for all implementation planning. Each phase has its own folder with a README and granular task files. Update statuses here as work lands.
Status legend
| Symbol | Meaning |
|---|---|
| ⬜ | Not started |
| 🟦 | Planned (designed, not coded) |
| 🟨 | In progress |
| 🟩 | Done |
| ⏸ | Paused / blocked |
| ❄️ | Frozen / future / optional |
Architectural anchors
The service is specified by the wiki at ../docs/wiki/. Implementing agents should read these pages before starting any task:
- Architecture —
docs/wiki/sources/gps-tracking-architecture.md,docs/wiki/concepts/plane-separation.md,docs/wiki/concepts/failure-domains.md - This service —
docs/wiki/entities/directus.md - Schema design —
docs/wiki/synthesis/directus-schema-draft.md - Reference rulebook —
docs/wiki/sources/rally-albania-regulations-2025.md(canonical real-world fixture for federation rule shapes) - Downstream / sibling —
docs/wiki/entities/postgres-timescaledb.md,docs/wiki/entities/processor.md,docs/wiki/concepts/live-channel-architecture.md
Non-negotiable design rules
These rules govern every task. Any deviation must be discussed and documented as a decision before code lands.
- Schema authority lives in Directus. Collections, fields, relations are defined through Directus and round-tripped via
directus schema snapshot. The exception is thepositionshypertable (owned by processor) and any other DDL Directus cannot represent (PostGIS-specific syntax, custom indexes, hypertable creation) — those live indb-init/*.sql. db-init/*.sqlis sequential, idempotent, and guarded. Files numberedNNN_name.sql. Each is internally idempotent (IF NOT EXISTS,ADD COLUMN IF NOT EXISTS). The runner skips files already recorded inmigrations_applied. Manual application of out-of-order files is forbidden.- Apply order at boot: db-init runner →
directus schema apply --yes→directus start. Any failure halts boot. Implemented inentrypoint.sh. - Snapshot lives in git, edited only via the admin UI. Hand-editing
snapshots/schema.yamlis forbidden — round-trip through the UI keeps the format consistent with whatdirectus schema snapshotproduces. - One PR = one snapshot regeneration. PRs that change schema include the regenerated snapshot. CI verifies the snapshot matches what
directus schema snapshotwould produce against an applied database. - No application logic in Flows. Flows are reserved for declarative orchestration (notifications, simple field updates, webhook routing). Domain logic lives in
extensions/(TypeScript hooks/endpoints) where it is reviewed, tested, and version-controlled like any other code. - Permissions are a separate phase. Adding a collection in Phase 1–3 does NOT come with its access policies — those land deliberately in Phase 4. Until then collections are admin-only by default. This avoids premature commitment to role definitions before the data model is settled.
- Image starts from
directus/directus:11.x. No forking the upstream image. Customizations are: bundled extensions under/directus/extensions/, snapshot/db-init artifacts under/directus/snapshots/and/directus/db-init/, and an entrypoint wrapper.
Phases
Phase 1 — Slice 1 schema + deploy pipeline
Status: 🟨 In progress (1.1–1.7 done; 1.8, 1.9 remaining)
Outcome: A Directus instance with the org-level catalog (orgs, users, organization_users, vehicles, devices and their org junctions) and event-participation collections (events, classes, entries, entry_crew, entry_devices) live and snapshot-tracked. db-init/ covers the TimescaleDB extension, the positions hypertable, and the faulty column. Image builds via Gitea Actions with a CI dry-run that catches snapshot drift before deploy. Rally Albania 2026 is registered as the first event in admin UI to dogfood the registration workflow. This is what Rally Albania 2026 needs.
See phase-1-slice-1-schema/README.md
| # | Task | Status | Landed in |
|---|---|---|---|
| 1.1 | Project scaffold | 🟩 | pending user commit |
| 1.2 | db-init runner script | 🟩 | pending user commit |
| 1.3 | Initial migrations (extensions, positions hypertable, faulty column) | 🟩 | pending user commit |
| 1.4 | Org-level catalog collections | 🟩 | pending user commit |
| 1.5 | Event-participation collections | 🟩 | pending user commit |
| 1.6 | Schema snapshot/apply tooling | 🟩 | pending user commit |
| 1.7 | Image build & entrypoint | 🟩 | pending user commit |
| 1.8 | Gitea CI dry-run workflow | ⬜ | — |
| 1.9 | Rally Albania 2026 dogfood seed | ⬜ | — |
Phase 2 — Course definition
Status: ⬜ Not started — depends on Phase 1 Outcome: Stages, segments, geofences (PostGIS polygons), waypoints, and speed_limit_zones as data-layer collections. Operators can define an event's full course before each stage. No processor logic yet — Phase 2 of processor consumes this data and writes crossings/penalties.
See phase-2-course-definition/README.md
Phase 3 — Timing & penalty tables
Status: ⬜ Not started — co-developed with processor Phase 2
Outcome: entry_segment_starts, entry_crossings, entry_penalties, stage_results, and penalty_formulas collections. The schema half of the paired schema/code work that produces real timing results. Penalty evaluator registry shipped on the processor side; rule numeric values shipped here.
See phase-3-timing-and-penalty-tables/README.md
Phase 4 — Permissions & policies
Status: ⬜ Not started — depends on Phases 1–3 Outcome: Dynamic-filter Policies per logical role (org-admin, race-director, marshal, timekeeper, participant, …) covering each collection × action. Multi-tenant isolation enforced by Directus, not by application code. Deployment-time work, not architectural.
See phase-4-permissions-and-policies/README.md
Phase 5 — Custom extensions
Status: ⬜ Not started — depends on Phase 3
Outcome: TypeScript extensions implementing the cross-plane workflows the schema implies: faulty-flag → recompute:requests stream emit; events.discipline validation hook; stage-open trigger materializing entry_segment_starts; CP closing-time computation; entry registration "copy crew from previous entry" custom endpoint.
See phase-5-custom-extensions/README.md
Phase 6 — Future / optional
Status: ❄️ Not committed
See phase-6-future/README.md
Ideas on radar: retroactivity preview UI for geometry edits (Phase 2.5 of processor — needs a UI counterpart here), command-routing Flows (phase-2-commands), audit trail extensions, federation rule import tooling.
Operating model
- Implementation agent contract. Each task file is self-sufficient: goal, deliverables, specification, acceptance criteria. An agent should be able to complete one task without reading the whole wiki — but should skim the wiki references at the top of the task before starting.
- Sequence within a phase. Task numbering reflects intended order. Soft dependencies are explicit in each task's "Depends on" field. Tasks with no dependencies on each other can be done in parallel.
- Status updates. When a task is started, change its row in this ROADMAP to 🟨 and the task file's status badge accordingly. When done, 🟩 + a one-line note in the task file's "Done" section pointing at the merging commit/PR.
- Drift control. If implementation diverges from a task's spec, update the task file before the diverging code lands, with a note explaining why. Do not let plans rot — either fix the plan or fix the code.