Open-World Narrative · Guides & deep dives

V5 Diagram Atlas

All six cells compose shared foundations, but their movement, combat, vehicle, world, narrative, and content rules remain cell-owned.

9sections2 minread

On this page

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#

FlowchartFlowchart: 15 steps and 20 connections.Player surfacesV5 world and ruleset hostUrban crimePeriod dramaFrontierMonster hunterGalactic squadHard vacuumShared gameplay worldservices and presentationMind Palace evidence anddeductionAuthority persistencecross-play and live serviceCase authoring andworkshopVersioned case andcontent corpusCases clues deductionssaves replays and auditsBuild rights compliancequality and operations
Flowchart: Flowchart. Flowchart: 15 steps and 20 connections.

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#

sequenceDiagram actor Player participant Surface as Investigation surface participant Case as Case authority participant World as Cell world state participant Evidence as Evidence ledger participant Deduction as Mind Palace participant Narrative as Dialogue and consequence Player->>Surface: Inspect scene person or object Surface->>Case: Request observation in current revision Case->>World: Validate reachability state and authority World-->>Case: Authoritative observation context Case->>Evidence: Record discovered evidence with provenance Evidence-->>Surface: Visible clue and disclosure Player->>Deduction: Propose link hypothesis or accusation Deduction->>Case: Validate against immutable authored truth alt unsupported or premature Case-->>Surface: Refusal contradiction or missing support else supported Case->>Narrative: Commit consequence and new world revision Narrative-->>Surface: Dialogue quest and world outcome end

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#

Entity-relationship diagramEntity-relationship diagram: 15 entities and 15 relationships.containsversionsversionsnamescontainsconstrainsderivesopenspinsrecordsdiscovered_asproposescommitsincludesemitsCELLWORLDWORLD_REVISIONCASE_DEFINITIONCASE_VERSIONSUSPECTCLUEALIBISOURCE_RECORDPROFILECASE_SESSIONDISCOVERYDEDUCTIONCONSEQUENCEAUDIT_EVENT
Entity-relationship diagram: Entity-relationship diagram. Entity-relationship diagram: 15 entities and 15 relationships.

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#

State diagramState diagram: 13 states and 15 transitions.schema cast truth clues and solution completereferential logic and rights checks passassets dialogue triggers and world bindings existQA accessibility safety and quality passimmutable compatible case version releasedeligible world and player session uses versionincomplete invalid or prohibitedcontradiction dead end or quality failurerights safety or correctness issuecompatible successor chosen for new sessionsDraftStructuredValidatedPlaytestableReviewedPublishedActiveRejectedRevisionRetractedMigrated
State machine: State diagram. State diagram: 13 states and 15 transitions.

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#

classDiagram class V5Host { activateCell() loadWorldRevision() } class CellPlugin { ruleset movementModel contentPolicy } class SharedGameplay { GAS perception morality } class MindPalace { recordEvidence() validateDeduction() } class CreatorSuite { authorCase() validatePackage() } class PlatformServices { authority persistence crossplay } V5Host --> CellPlugin : activates CellPlugin --> SharedGameplay : specializes V5Host --> MindPalace : hosts CreatorSuite --> MindPalace : publishes versioned case V5Host --> PlatformServices : composes PlatformServices --> CellPlugin : pins compatible versions

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#

V5 estateMind map: 23 ideas.V5 estateCellsUrban crime and bureauinvestigationsPeriod drama and historicalauthenticityFrontier survival andtraversalMonster hunting andalchemyGalactic squad andcompanionsHard vacuum andNewtonian spaceflightCross-cellMind Palace and authoredcasesGAS animation input andcombatPerception crowds moralityand dialogueWorlds vehicles mountsand shipsCreation and onlineCreator suite corpus andworkshopModes multiplayer andcross-playPersistence progressionand live serviceCompanion community andsupportPlatformAccessibility localizationand rightsTelemetry performance andtestingBuild content and datapipelinesSecurity compliancerelease and operations
Mind map: V5 estate. Mind map: 23 ideas.

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 operations
Show 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#

From V5 narrative concept to supported caseUser journey: 8 stages.1Define cell truth sources rights and cultural postureResearch. Narrative, Rights. Score 5 of 5.2Author cast clue logic consequences and world bindingsResearch. Content. Score 5 of 5.3Check schema referential logic and reachable solutionValidate. Tools, QA. Score 5 of 5.4Review dialogue assets accessibility safety and localizationValidate. QA, Governance. Score 5 of 5.5Package immutable version and test runtime savesIntegrate. Engineering. Score 4 of 5.6Verify world authority services cook and compatibilityIntegrate. Engineering, Release. Score 5 of 5.7Publish cohort observe support and rights signalsOperate. SRE, Product. Score 5 of 5.8Correct retract migrate or roll back with auditOperate. Owners. Score 5 of 5.
User journey: From V5 narrative concept to supported case. User journey: 8 stages.

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#

timeline title V5 release evidence Contract : Six-cell scope and shared specialization boundaries : Case content save service and compatibility schemas Runtime : Cell gameplay world investigation and presentation : Authority persistence cross-play creator and providers Verification : Case logic journey save migration and adversarial tests : Accessibility performance rights security and cook evidence Candidate : Immutable content set platform certification and support : Staged rollout observability recovery and rollback Supported : Named cells modes platforms content versions and regions : Current rights incidents regressions and operational proof

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.