Landing-page sequence
From the Meridians Wiki · Public · Maintained · joint
The current public page leads with “The causal simulator”, then asks “Have a problem?” and answers “Train the pathway before you live it.” It describes a negotiation, hard conversation, sales call, or launch becoming a living world: people, wants, knowledge, and constraints remain in play while the person acts inside it.
The current source of truth is
gateway-public.ts, not this document. Keep
the exact values below synchronized with that source.
Sci-fi/space framing and 'selective pressure' are retired from public surfaces (2026-09-21).
The rendered sequence is hero → worlds → grove → runtime → pricing. The hero carries no more than two short sentences; the sections below earn the mechanism and delivery detail.
The Studio is advertised with one real, full-cockpit photograph of the Astral Network. Keep the surrounding controls visible so the image proves that the graph is an operative lens inside the instrument, not an isolated concept render; do not restore a theme or view carousel here. The landing page itself follows the shared theme contract and exposes the compact theme picker in its navigation; changing the page theme does not recolour the real Astral Studio photograph.
| Beat | Approved idea | Job in the funnel |
|---|---|---|
| Hero | Pill: The causal simulator · Title: Have a problem? · Accent: Train the pathway before you live it. · Body: A negotiation, a hard conversation, a sales call, a launch. Meridians turns the situation into a living world — the people in it, what they want, what they know, what they can't say — and lets you act inside it. · Body accent: Characters you can see and hear. Decisions under consequence. Decide, see what you caused, rewind, try another way — and walk in already knowing the cost. · CTA: See how it works · Proof: Decide · see what you caused · retry | Current hero copy from gateway-public.ts. |
| Premise | Because everything is recorded, everything can be replayed. | Name the mechanism in one line: a recorded world can be run forward rather than imagined. |
| Worlds | For you · Decisions under consequence · For sales teams · Practice worlds · For marketing · Market simulations · For strategy · Fate pathways | The four worlds.forms titles in gateway-public.ts. |
| Audience | For people who would rather decide inside a story than watch one resolve. | Name the roleplay-minded reader as the alternative-to-reading audience. |
| Three mediums | Decide in a Scenario. Read an Experience. Wander a World. | Show the three ways one world is inhabited — peers, not a ladder. |
| Primary action | See how the world works | Enter the medium story without implying that the dedicated reader is shipped. |
| World and medium | A long journey needs more than survival. It needs worlds worth entering. | Bring the promise home to a common reader through the hour-long training world, then extend its remembered narrative into the pocket-dimension horizon. |
| Worked Domain | A Domain holds the world together. Even before it becomes a novel. | Show the serious research and judgment utility of the same world foundation. |
| Program | The Program keeps it alive. You keep it yours. | Reveal Research → Opinion → Merge → Position as the continuity engine. |
| Will | The world computes; you commit. | Show Will injected from outside the simulation — an attributable correction, commitment, or agent tool call entering the Domain, so every divergence has an author. |
| Scenario | Make the critical move. Let the story continue. | Show direct and asynchronous play now, then the deeper Episode roleplay form in development. |
| Analysis | When the journey narrows. Open another world. | Use the fictional voyage graph to show how constrained routine, traveller attention, and consequential novelty relate through the pentad. |
| Horizon | Explored once. Read forever. | Name the production/consumption split: exploration finds routes worth having; reading serves finished text and images. |
| Grove | Pressure title: Meridians World Search (MWS) · Pressure body: The core algorithm. A Monte Carlo tree search over the meridians of a world: it runs the world forward down many pathways, spends its effort where the outcome is most uncertain and most costly, and grows the world at the forks that matter. Each path comes back with its price. It develops the world; it never plays your move. | Current grove.pressureTitle and grove.pressureBody from gateway-public.ts. |
| Plans | Run your Domain your way. | Explain Hosted continuity and the sovereign local alternative after value is understood. |
The short proof line is "Decide · see what you caused · retry." The current hero CTA is "See how it works." The closer is the brand tagline, "Explore the fate. Live the one you chose." Public copy must not imply a reader interface exists: the specification is written, the interface is not built. Never name a licensed franchise as an available world — the shippable formulation is a canon you own or have the rights to, with public-domain works as the worked example.
The Will beat is load-bearing, not decoration: a Meridians world never moves on its own. Copy may say the engine holds the rules, the memory, and the price of a move, and that the move itself is injected from outside — by a reader at a fork, a group at the card table, a Director, or an agent through MCP. Never imply the engine makes the commitment, and never describe autonomous exploration as Will: it proposes and prices futures, it does not choose.
One claim must stay precise across every beat: "does not generate while you read it" belongs to the prepared Experience alone. A World generates as it is wandered, so copy may promise it is explorable at any moment in its history, but never that it is free to inhabit.
The Horizon body may carry the quieter identity line “No perspective sees the whole; one kept history preserves what changed.” It supports the approved headline rather than becoming a second headline.
The space story asks whether we are alone and what more existence may contain as open Fate, never as an answer Meridians already possesses. Its immediate human problem is the long passage: a vessel or mobile datacenter with finite power and attention, delayed information, slowly changing physical surroundings, and human and AI travellers who still need novelty, practice, and encounter. A pocket dimension answers with a new world that remembers rather than disposable diversion. Copy must also say that Meridians is building the recorded-world and consequence layer on Earth, not operating the spacecraft or claiming these worlds preserve wellbeing, transfer skill, or establish mission readiness without external evidence.
Public copy speaks in pentad forces — World embodies, System constrains, Causality connects, Fate remains open, and Theme recurs — as a macro world model and symbolic frame. 五行 supplies the names, glyphs, and pentad geometry; no fixed scene-to-scene generating or controlling relation is asserted. Record-specific lagged couplings remain measured evidence, and independence is a valid reading. The sign glyphs may appear as notation beside a force name. Do not present the correspondence as historical Chinese doctrine, five substances, astrology, or prophecy.
Do not lead with the Program lifecycle, graph architecture, multiplayer mechanics, World, or a generic “AI agents” claim. Public copy must distinguish shipped Research, Domains, Program, Scenario, Stories, Studio, Hosted, MCP, and custom configurations from Stageplay incubation, live Episode direction, and experimental Worlds. A useful Domain or Scenario does not need to graduate into either later form.
Akashyatra may demonstrate what a creator-owned living universe means. Preserve Jason Yu's authorship and the boundary between authored canon, structured extraction, and future played history.