Referential
Domain model
Referential aggregate relationships and the boundary between durable facts, policy, and live operations.
Aggregate map
Durable fact versus live decision
| Referential fact | Another owner |
|---|---|
| Vehicle administrative status | Operational access verdict — Cycle + Rules |
| Permit validity window | Whether coverage is sufficient for a live decision |
| Bay dimensions | Occupation, reservation, temporary unavailability — Allocation |
| Itinerary calling sequence | One dated departure — Scheduling |
| Schedule recurrence and stop times | Generated occurrence — Scheduling |
| Installed checkpoint capability | Device health and command acknowledgement — Cycle |
| Payout beneficiary | Amount owed, settlement, and payout — Billing |
Validity is derived at query time. Referential never copies “eligible,” “permit valid,” or “may enter” flags onto a vehicle.
History pattern
Lifecycle records retire, suspend, revoke, or decommission instead of deleting. Published itinerary and schedule corrections create successor revisions. Payout details append effective-dated versions. Carrier and category changes append vehicle history.
The result is one answer to “what was true then?” without reconstructing facts from overwritten rows.