Session 5 — Reference Material

Goal: Spot-check schemas, events, and protocols for accuracy against the domain model. Estimated time: 60–90 min (skim — total ~470 KB)

Schemas

#	File	Size	Context
1	schema-backoffice.md	57 KB	Operators, tours, vehicles, crew, pricing
2	schema-commerce.md	31 KB	Bookings, payments, tickets, checkout
3	schema-operations.md	83 KB	Dispatch, service legs, telemetry, boarding
4	schema-communications.md	24 KB	Conversations, messages, templates

Schema review strategy: Pick 3–5 key entities from domain-model.md (e.g., TourTemplate, Booking, ServiceLeg). Find each in the schema file. Confirm columns, types, and constraints match. Check for tenant_id on every domain table.

Events

#	File	Content
5	event-catalog.md	Master registry of all 53 domain events
6	event-contracts-backoffice.md	Backoffice event payloads
7	event-contracts-commerce.md	Commerce event payloads
8	event-contracts-operations.md	Operations event payloads
9	event-contracts-pricing.md	Pricing event payloads

Protocols (prioritized by V0.1 relevance)

Must read:

• booking-lifecycle-protocol.md (24 KB)
• cancellation-protocol.md (14 KB)
• kalkulations-engine.md (13 KB)
• price-matrix-variant-spec.md (19 KB)

Read if time allows:

• notification-pipeline-protocol.md (40 KB)
• offline-sync-protocol.md (13 KB)
• dispatch-availability-engine.md (14 KB)

Skim for later:

• inbox-protocol.md, incident-broadcast-protocol.md, vehicle-swap-protocol.md, crew-qualification-protocol.md, channel-provisioning-protocol.md, invoice-service-protocol.md, mcp-agent-bridge.md

🔍 What to Validate

• [ ] Do schema columns match domain model entity definitions?
• [ ] Does the event catalog match the context map in domain-driven-design.md §8?
• [ ] Is schema-operations.md (83 KB) too large? Consider splitting.
• [ ] Are event contracts consistent with current schema column names?
• [ ] Which protocols describe v0.1 vs. future work? Are they clearly labeled?

Findings