Specifications

Status: map, not a spec. Each spec owns its own status ledger; this page only says what each one owns and how they fit toward the two roadmaps. Nothing here creates a new ontology or a fourth product.

Domain defines. Branch preserves. Scenario resolves. Episode embodies. World inherits and lives.

Priorities (2026-09-21)

Meridians is a causal simulator for decisions under consequence and training: a consequential situation becomes a kept world — actors with incentives and private information, rules, constraints, open questions — that is run forward, acted inside, and remembered. Two names carry the whole design:

• Meridians are the fate pathways of a world — the routes it can still travel. Causality is the consequential decisions and turning points where a pathway bends.
• Meridians World Search (MWS) is the core algorithm: a Monte Carlo tree search over a world's meridians. It runs the world forward down many pathways, spends its budget where the outcome is most uncertain and most costly, develops the world at those forks (new scenes, actors, constraints where the tree is thin), and returns each pathway with its price. It proposes and prices; it never chooses — Will is injected from outside. Owned by branch-refinement (the search) over fate-exploration (the scout). Specified, not shipped; per-branch Iterate refine is the shipped fragment.

Two roadmaps, kept separate on purpose:

1. Causal MCTS VNs — the roadmap. Situation intake (voice interview as direction; by hand through MCP today) → situation model → actor models → causal hypotheses → world construction → MWS over the branch tree → the VN as interface (characters you can see and hear; voice, sound, music) → play → consequence → reflection → re-simulation. Sold B2C (decision preparation: negotiations, hard conversations, career and founder decisions) and B2B (sales practice worlds, marketing simulations via Scenario, strategy and crisis practice). Owned across fate-exploration, branch-refinement, training-worlds, visual-novel, latent-traits. Micro analysis of the scene (sonic) sits inside this roadmap as a value-add whose only job is engagement and conveying the macro consequence; it is unbuilt and never a second programme. The argument and the build-ordered tracks are strategy 14.
2. VNMMO — the stretch goal. A persistent, many-seat universe that runs the same simulator more automated: MWS as a shared tree with a value per seat, many wills under one canon (world, world-tree). It depends on a mature MWS and a proven simulator; nothing in the primary roadmap depends on it. Not on the public surfaces beyond a stretch-goal mention.

The specs and what each owns

How they compose — one loop, two roadmaps

MWS grows the tree                (branch-refinement, over fate-exploration's scout)
→ flag plan fixes forks + band    (training-worlds §4, flags)
→ world prepared and served       (visual-novel, production, world/Factory)
→ person decides; record written  (flags §3, latent-traits §2)
→ reading: θ · stance · moments   (training-worlds §5, latent-traits §3)
→ target band for the next hour   (latent-traits §4 → branch-refinement §3)
→ MWS grows the tree …

Two loops over one substrate, and the boundary between them is the whole design:

• MWS develops and selects worlds. Its value is a property of forks and futures — consequence, divergence, reach, item information inside a declared band. It never reads a person's θ, response, or history.
• Latent traits measure the person. The record is private, domain-native, post-play, with standard error attached; its one output to the world side is the band. It never chooses for the person and is never a verdict.

Neither may commit: Will is injected from outside, attributable, and the engine computes what followed.

The two roadmaps are the same loop at two scales:

1. Causal MCTS VNs — one seat (or one team) and one situation; the loop above as stated, entered either from a world we made or from a situation the person brought. The person's record across many hours (latent-traits) is read as intervals, and transfer is proven only externally.
2. VNMMO (stretch) — the same loop under many wills: first a family of timeline-dated, replayable VNs released into a shared multiverse as MWS earns them (world-tree); then many seats in one kept world, MWS as a shared tree with a value per seat (branch-refinement §12), each person's record their own inside the crowd (world roadmap; strategy 01 care rules). Directional until a bounded multi-seat run has been played.

Product framing and evidence rules live outside this folder: positioning, strategy 01, strategy 12, Two magics.