MeridiansMeridians

1. The funnel thesis

Source path: knowledge-base/knowledge/product/journey/01-1-the-funnel-thesis.md

# 1. The funnel thesis

The visitor is not buying architecture, a lifecycle diagram, or the phrase “persistent graph-world.”
They are buying the ability to turn a consequential life setup into **a living Domain they can understand,
maintain, and explore** — a world that keeps its people, places, resources, rules, evidence,
relationships, and open questions together as conditions change.

The front door therefore leads with **the ecosystem around a choice**, then shows what the Program enables:
the Domain stays current, human judgment enters as attributable Will, and Scenario tests different moves
without discarding the original world. Only after that utility is concrete does the page reveal the larger
horizon: turn-based ecosystems where humans and agents inhabit different perspectives inside one shared
Domain.

**What the visitor is leaving behind is the disposable answer.** A prompt can answer one question and
forget the life around it. A Domain preserves the conditions, shows what moved, and lets the next choice
inherit what earlier choices made true.

```text
Curiosity          Commitment             Activation                    First value
living-world hook → Enter a living Domain → Director account → Hosted ready → grounded Domain

Steered value                                Compounding value
change → Story → inspect forces → explore a move → return → correct → more capable Domain
```

Hosted is the recommended and default product path. License is the sovereign self-hosted branch, not an
equal decision presented before the user understands the value. Marketplace discovery is deliberately
outside the primary funnel until people love the private product. Once it opens, it becomes an *optional*
second on-ramp: a new Director can jumpstart from a configured **Bundle** — a quality Domain or a
Constellation of them, with its research cycles and schedule ready to customise — instead of building
from scratch, and an experienced Director can hand a **private** bundle to someone they're bringing on
(direction, not a shipped step; the built genesis path remains Interview/Research onboarding).
Open on GitHub

Raw Markdown source