USER JOURNEY — current product and World direction

Owner: the end-to-end product funnel, its hand-offs, primary actions, recovery paths, and measurement. This is the file to update whenever a user-facing route, CTA, activation milestone, or experienced-user continuation changes.

POSITIONING.md owns what Meridians is. BRAND_COPY.md owns reusable language. PRODUCT_BEHAVIOURS.md owns the repeated human practice. The feature specs own their implementation contracts. This document owns how those pieces meet one person in order.

The current funnel leaves describe the shipped Domain/Studio/Stories/Hosted path and remain valid until a World experience exists. The future journey adds a second activation path after a Domain becomes playable:

premise or source → Domain → Scenario → choose preset / seats / cadence → World → return each turn

Do not invent the detailed World onboarding yet. The stable requirement is that a person can deploy a preset quickly, understand what they are playing, choose manual or agent-driven seats, see when the world is active or resting, and return to perspective-appropriate changes rather than an omniscient activity feed.