Session 2 — Domain & Product Model

Goal: Confirm the domain model, entity relationships, user journeys, and commercial logic are complete and correct. Estimated time: 90 min (domain-model.md alone is 43 KB — the heaviest single doc)

Reading Order

#	File	What It Covers
1	PRODUCT_domain-model.md	Every entity definition, bounded context models, aggregate roots.
2	PRODUCT_user-journeys.md	B2C booking, dispatcher, driver, passenger flows.
3	PRODUCT_payments-and-billing.md	Payment providers, billing model, subscription tiers.
4	PRODUCT_mollie-integration.md	Mollie API integration, deposit config, refund flows.
5	PRODUCT_migration-and-onboarding.md	Concierge onboarding, legacy data migration.
6	PRODUCT_differentiators-10-percent.md	Key differentiating features and competitive moats.

🔍 What to Validate

• [ ] domain-model.md is the single most important file. Cross-reference key entities against the schema files (Session 5) — do they match?
• [ ] User journeys: do they still reflect the actual UX you intend to build? Check against workspace feature docs in apps/workspace/docs/.
• [ ] Mollie integration: is the deposit/balance payment flow still the chosen approach? Any changes since this was written?
• [ ] Migration doc is only 2.5 KB — this is flagged as a critical gap. Is there a migration playbook anywhere else?
• [ ] Are PricingRule and CapacityRule value objects defined anywhere beyond a mention? (Flagged in TODOS.md as undefined.)
• [ ] payments-and-billing.md: does it define the actual subscription tiers, or only the billing engine choice?
• [ ] differentiators.md: are the claimed differentiators still unique, or have competitors closed the gap?

Findings