This atlas provides the cross-cutting visual models for V5's six-cell open-world narrative universe. It covers cell composition, investigation flow, durable evidence, case lifecycle, module ownership, product estate, content production, and release evidence. The focused documentation and current implementation, assets, tests, builds, rights, and operations remain authoritative.
Six-cell product landscape#
This picture is wider than it can be shown here. Move across it, or read it as text.
Drawn from its Mermaid source.
As text
Parts: - Player surfaces - V5 world and ruleset host - Urban crime - Period drama - Frontier - Monster hunter - Galactic squad - Hard vacuum - Shared gameplay world services and presentation - Mind Palace evidence and deduction - Authority persistence cross-play and live service - Case authoring and workshop - Versioned case and content corpus (data) - Cases clues deductions saves replays and audits (data) - Build rights compliance quality and operations Connections: - Player surfaces to V5 world and ruleset host - V5 world and ruleset host to Urban crime - V5 world and ruleset host to Period drama - V5 world and ruleset host to Frontier - V5 world and ruleset host to Monster hunter - V5 world and ruleset host to Galactic squad - V5 world and ruleset host to Hard vacuum - Urban crime to Shared gameplay world services and presentation - Period drama to Shared gameplay world services and presentation - Frontier to Shared gameplay world services and presentation - Monster hunter to Shared gameplay world services and presentation - Galactic squad to Shared gameplay world services and presentation - Hard vacuum to Shared gameplay world services and presentation - Shared gameplay world services and presentation to Mind Palace evidence and deduction - Shared gameplay world services and presentation to Authority persistence cross-play and live service - Case authoring and workshop to Versioned case and content corpus - Versioned case and content corpus to Mind Palace evidence and deduction - Mind Palace evidence and deduction to Cases clues deductions saves replays and audits - Authority persistence cross-play and live service to Cases clues deductions saves replays and audits - Cases clues deductions saves replays and audits to Build rights compliance quality and operations
Show source
flowchart TB
Player[Player surfaces] --> Host[V5 world and ruleset host]
Host --> Urban[Urban crime]
Host --> Period[Period drama]
Host --> Frontier[Frontier]
Host --> Hunter[Monster hunter]
Host --> Squad[Galactic squad]
Host --> Vacuum[Hard vacuum]
Urban --> Shared[Shared gameplay world services and presentation]
Period --> Shared
Frontier --> Shared
Hunter --> Shared
Squad --> Shared
Vacuum --> Shared
Shared --> Mind[Mind Palace evidence and deduction]
Shared --> Online[Authority persistence cross-play and live service]
Creator[Case authoring and workshop] --> Corpus[(Versioned case and content corpus)]
Corpus --> Mind
Mind --> Evidence[(Cases clues deductions saves replays and audits)]
Online --> Evidence
Evidence --> Release[Build rights compliance quality and operations]
All six cells compose shared foundations, but their movement, combat, vehicle, world, narrative, and content rules remain cell-owned. Mind Palace is a cross-cell investigation contract, not a license to collapse each cell's authored truth.
Investigation sequence#
The player-visible clue, durable discovery, deduction proposal, authored truth, and resulting world consequence are distinct. Presentation may obscure or dramatize, but it cannot mutate the canonical solution to reward a guess.
Durable case and world records#
This picture is wider than it can be shown here. Move across it, or read it as text.
Drawn from its Mermaid source.
As text
Parts: - CELL - WORLD - WORLD_REVISION - CASE_DEFINITION - CASE_VERSION - SUSPECT - CLUE - ALIBI - SOURCE_RECORD - PROFILE - CASE_SESSION - DISCOVERY - DEDUCTION - CONSEQUENCE - AUDIT_EVENT Connections: - CELL to WORLD (one to zero or many): contains - WORLD to WORLD_REVISION (one to zero or many): versions - CASE_DEFINITION to CASE_VERSION (one to zero or many): versions - CASE_VERSION to SUSPECT (one to one or many): names - CASE_VERSION to CLUE (one to one or many): contains - CASE_VERSION to ALIBI (one to zero or many): constrains - CLUE to SOURCE_RECORD (zero or many to zero or many): derives - PROFILE to CASE_SESSION (one to zero or many): opens - CASE_VERSION to CASE_SESSION (one to zero or many): pins - CASE_SESSION to DISCOVERY (one to zero or many): records - CLUE to DISCOVERY (one to zero or many): discovered_as - CASE_SESSION to DEDUCTION (one to zero or many): proposes - DEDUCTION to CONSEQUENCE (one to zero or many): commits - WORLD_REVISION to CONSEQUENCE (one to zero or many): includes - CASE_SESSION to AUDIT_EVENT (one to zero or many): emits
Show source
erDiagram
CELL ||--o{ WORLD : contains
WORLD ||--o{ WORLD_REVISION : versions
CASE_DEFINITION ||--o{ CASE_VERSION : versions
CASE_VERSION ||--|{ SUSPECT : names
CASE_VERSION ||--|{ CLUE : contains
CASE_VERSION ||--o{ ALIBI : constrains
CLUE }o--o{ SOURCE_RECORD : derives
PROFILE ||--o{ CASE_SESSION : opens
CASE_VERSION ||--o{ CASE_SESSION : pins
CASE_SESSION ||--o{ DISCOVERY : records
CLUE ||--o{ DISCOVERY : discovered_as
CASE_SESSION ||--o{ DEDUCTION : proposes
DEDUCTION ||--o{ CONSEQUENCE : commits
WORLD_REVISION ||--o{ CONSEQUENCE : includes
CASE_SESSION ||--o{ AUDIT_EVENT : emits
Case truth, cell world, player session, discovery, deduction, and consequence versions remain separate so save/load, workshop update, correction, replay, and rollback do not rewrite history.
Case content lifecycle#
This picture is wider than it can be shown here. Move across it, or read it as text.
Drawn from its Mermaid source.
As text
Parts: - Start (initial) - Draft - Structured - Validated - Playtestable - Reviewed - Published - Active - Rejected - Revision - Retracted - Migrated - End (final) Connections: - Start to Draft - Draft to Structured: schema cast truth clues and solution complete - Structured to Validated: referential logic and rights checks pass - Validated to Playtestable: assets dialogue triggers and world bindings exist - Playtestable to Reviewed: QA accessibility safety and quality pass - Reviewed to Published: immutable compatible case version released - Published to Active: eligible world and player session uses version - Draft to Rejected: incomplete invalid or prohibited - Playtestable to Revision: contradiction dead end or quality failure - Revision to Structured - Published to Retracted: rights safety or correctness issue - Active to Migrated: compatible successor chosen for new sessions - Retracted to End - Rejected to End - Migrated to End
Show source
stateDiagram-v2
[*] --> Draft
Draft --> Structured: schema cast truth clues and solution complete
Structured --> Validated: referential logic and rights checks pass
Validated --> Playtestable: assets dialogue triggers and world bindings exist
Playtestable --> Reviewed: QA accessibility safety and quality pass
Reviewed --> Published: immutable compatible case version released
Published --> Active: eligible world and player session uses version
Draft --> Rejected: incomplete invalid or prohibited
Playtestable --> Revision: contradiction dead end or quality failure
Revision --> Structured
Published --> Retracted: rights safety or correctness issue
Active --> Migrated: compatible successor chosen for new sessions
Retracted --> [*]
Rejected --> [*]
Migrated --> [*]
Published versions are immutable. Correction or rights withdrawal creates a new version or retraction policy; it does not silently change the truth behind an active save.
Runtime and authoring composition#
The authoring and runtime sides meet at versioned contracts. Creator tools cannot write directly into an active case session, and a cell cannot bypass platform authority or persistence.
Product and ownership estate#
This picture is wider than it can be shown here. Move across it, or read it as text.
Drawn from its Mermaid source.
As text
Tree:
- V5 estate
- Cells
- Urban crime and bureau investigations
- Period drama and historical authenticity
- Frontier survival and traversal
- Monster hunting and alchemy
- Galactic squad and companions
- Hard vacuum and Newtonian spaceflight
- Cross-cell
- Mind Palace and authored cases
- GAS animation input and combat
- Perception crowds morality and dialogue
- Worlds vehicles mounts and ships
- Creation and online
- Creator suite corpus and workshop
- Modes multiplayer and cross-play
- Persistence progression and live service
- Companion community and support
- Platform
- Accessibility localization and rights
- Telemetry performance and testing
- Build content and data pipelines
- Security compliance release and operationsShow source
mindmap
root((V5 estate))
Cells
Urban crime and bureau investigations
Period drama and historical authenticity
Frontier survival and traversal
Monster hunting and alchemy
Galactic squad and companions
Hard vacuum and Newtonian spaceflight
Cross-cell
Mind Palace and authored cases
GAS animation input and combat
Perception crowds morality and dialogue
Worlds vehicles mounts and ships
Creation and online
Creator suite corpus and workshop
Modes multiplayer and cross-play
Persistence progression and live service
Companion community and support
Platform
Accessibility localization and rights
Telemetry performance and testing
Build content and data pipelines
Security compliance release and operations
The estate is a reading index. Product-wide claims require evidence across all applicable cells; a cell-specific capability must remain labeled as such.
Authored-content journey#
Drawn from its Mermaid source.
As text
Steps: - 1. Define cell truth sources rights and cultural posture (good). Research. Narrative, Rights. Score 5 of 5. - 2. Author cast clue logic consequences and world bindings (good). Research. Content. Score 5 of 5. - 3. Check schema referential logic and reachable solution (good). Validate. Tools, QA. Score 5 of 5. - 4. Review dialogue assets accessibility safety and localization (good). Validate. QA, Governance. Score 5 of 5. - 5. Package immutable version and test runtime saves (good). Integrate. Engineering. Score 4 of 5. - 6. Verify world authority services cook and compatibility (good). Integrate. Engineering, Release. Score 5 of 5. - 7. Publish cohort observe support and rights signals (good). Operate. SRE, Product. Score 5 of 5. - 8. Correct retract migrate or roll back with audit (good). Operate. Owners. Score 5 of 5.
Show source
journey
title From V5 narrative concept to supported case
section Research
Define cell truth sources rights and cultural posture: 5: Narrative, Rights
Author cast clue logic consequences and world bindings: 5: Content
section Validate
Check schema referential logic and reachable solution: 5: Tools, QA
Review dialogue assets accessibility safety and localization: 5: QA, Governance
section Integrate
Package immutable version and test runtime saves: 4: Engineering
Verify world authority services cook and compatibility: 5: Engineering, Release
section Operate
Publish cohort observe support and rights signals: 5: SRE, Product
Correct retract migrate or roll back with audit: 5: Owners
Research, authorship, logic validation, runtime realization, platform packaging, and live operations all contribute distinct evidence.
Evidence order#
The sequence does not imply equal cell maturity. Each supported claim names its cell, content version, platform, and evidence.
How to use this atlas#
Use the landscape and estate for ownership, trace an investigation with the sequence and data model, review content changes with the lifecycle/composition models, and use the journey/evidence order for release. Continue to the V5 guide, feature index, and architecture index.