Referential overview
The advanced master-data module and its 29 shipped capabilities.
Referential owns the durable facts every other SmartGare module reads: carrier identity, fleet, permits, physical topology, timetable geography, service catalog, schedules, authorizations, payout beneficiaries, and import provenance.
Explore the domain
Domain model
Understand aggregate ownership and the boundary with live operations.
Carriers and coordinations
Lifecycle, activation readiness, beneficiary history, and memberships.
Vehicles, identity, and permits
Fleet records, readings, permit validity, expiry, import, and eligibility.
Station topology
Stations, areas, bays, checkpoints, and installed capabilities.
Service catalog
Lines, operator assignments, itineraries, recurrences, stop times, and calls.
Authorizations and imports
Transport-authority grants, provenance, statements, and explicit conflicts.
MCP surface
Authenticated tool mirror over the same use cases and query ports.
Generated endpoints
Browse the operation and schema reference produced from OpenAPI.
Core guarantees
- Master data never stores an operational access verdict.
- Lifecycle changes are explicit, reasoned, and history-preserving.
- Unique and exclusion constraints close application-level races.
- Stale or losing writers receive
409, never silent overwrite. - HTTP, MCP, persistence, and cross-module callers share the same domain rules.
- Each endpoint and tool declares a permission.
Surface families
| Concern | REST family |
|---|---|
| Carrier and beneficiaries | /referential/v1/carriers |
| Fleet and permits | /referential/v1/vehicles, /vehicle-identifiers, /vehicle-permits |
| Topology | /stations, /station-areas, /bays, /checkpoints |
| Service catalog | /destinations, /lines, /itineraries, /schedules |
| Coordinations | /coordinations |
| Transport authority | /authorizations |
| Import evidence | /import-staging |
| Eligibility | /checkpoints/{id}/eligibility |