< Prev | Up: Session Overview | Next >

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	Lines	Context
1	schema-backoffice.md	689	Operators, tours, vehicles, crew, pricing
2	schema-commerce.md	383	Bookings, payments, tickets, checkout
3	schema-operations.md	1184	Dispatch, service legs, telemetry, boarding
4	schema-communications.md	394	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	Lines	Content
5	event-catalog.md	~150	Master registry of all 53 domain events
6	event-contracts-backoffice.md	~180	Backoffice event payloads
7	event-contracts-commerce.md	285	Commerce event payloads
8	event-contracts-operations.md	284	Operations event payloads
9	event-contracts-pricing.md	~150	Pricing event payloads

Protocols (prioritized by V0.1 relevance)

Must read:

• booking-lifecycle-protocol.md (381 lines)
• cancellation-protocol.md (226 lines)
• kalkulations-engine.md (179 lines)
• price-matrix-variant-spec.md (234 lines)

Read if time allows:

• notification-pipeline-protocol.md (966 lines!)
• offline-sync-protocol.md (239 lines)
• dispatch-availability-engine.md (212 lines)

Skim for later:

• inbox-protocol (521 lines), incident-broadcast (242 lines), vehicle-swap (228 lines), crew-qualification (165 lines), channel-provisioning (229 lines), invoice-service (149 lines), mcp-agent-bridge (143 lines).

🔍 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 (1184 lines) too large? Consider splitting.
• [ ] Is notification-pipeline-protocol.md (966 lines) too large?
• [ ] Are event contracts consistent with current schema column names?
• [ ] Which protocols describe v0.1 vs. future work? Are they clearly labeled?

🗺️ Mindmap & Path Optimization

Grab your pen and paper:

• [ ] Map a Cross-Domain Event: Take BookingConfirmed from the Commerce domain. Trace how it updates the Dispatch board in the Operations domain.
  • Observation: You need schema-commerce.md → event-catalog.md → event-contracts-commerce.md → dispatch-availability-engine.md → schema-operations.md.
  • Optimization: Is this 5-hop path too complex for an agent or developer? Should we embed the event payload definitions directly into the schema files next to the tables that trigger them?

📝 Findings & Actions

Severity	File / Topic	Issue & Optimization Potential	Action Required

---

< Prev | Up: Session Overview | Next >