Tactical Action · Guides & deep dives

V4 Diagram Atlas

The host and shared layer supply contracts, not identical behavior.

9sections1 minread

On this page

This atlas is the visual orientation layer for V4's five-cell tactical-action universe. It explains cell hosting, action flow, durable play records, session state, plugin composition, ownership, content production, and release evidence. Focused pages and current implementation/test/build evidence remain authoritative.

Multi-cell runtime landscape#

FlowchartFlowchart: 13 steps and 17 connections.Player input and platformV4 game hostActivated ruleset cellTactical FPSStealth and real-timetacticsAction RPGReal-time strategy2D run-and-gunShared GAS inputanimation AI andpresentationWorld streaming procgenmodes and contentAuthority persistenceprogression and liveserviceSaves replays telemetryassets and auditsBuild platform securitycompliance and operations
Flowchart: Flowchart. Flowchart: 13 steps and 17 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 input and platform
- V4 game host
- Activated ruleset cell
- Tactical FPS
- Stealth and real-time tactics
- Action RPG
- Real-time strategy
- 2D run-and-gun
- Shared GAS input animation AI and presentation
- World streaming procgen modes and content
- Authority persistence progression and live service
- Saves replays telemetry assets and audits (data)
- Build platform security compliance and operations

Connections:
- Player input and platform to V4 game host
- V4 game host to Activated ruleset cell
- Activated ruleset cell to Tactical FPS
- Activated ruleset cell to Stealth and real-time tactics
- Activated ruleset cell to Action RPG
- Activated ruleset cell to Real-time strategy
- Activated ruleset cell to 2D run-and-gun
- Tactical FPS to Shared GAS input animation AI and presentation
- Stealth and real-time tactics to Shared GAS input animation AI and presentation
- Action RPG to Shared GAS input animation AI and presentation
- Real-time strategy to Shared GAS input animation AI and presentation
- 2D run-and-gun to Shared GAS input animation AI and presentation
- Shared GAS input animation AI and presentation to World streaming procgen modes and content
- Shared GAS input animation AI and presentation to Authority persistence progression and live service
- World streaming procgen modes and content to Saves replays telemetry assets and audits
- Authority persistence progression and live service to Saves replays telemetry assets and audits
- Saves replays telemetry assets and audits to Build platform security compliance and operations
Show source
flowchart TB
  Player[Player input and platform] --> Host[V4 game host]
  Host --> Cell[Activated ruleset cell]
  Cell --> FPS[Tactical FPS]
  Cell --> Stealth[Stealth and real-time tactics]
  Cell --> ARPG[Action RPG]
  Cell --> RTS[Real-time strategy]
  Cell --> Arcade[2D run-and-gun]
  FPS --> Shared[Shared GAS input animation AI and presentation]
  Stealth --> Shared
  ARPG --> Shared
  RTS --> Shared
  Arcade --> Shared
  Shared --> World[World streaming procgen modes and content]
  Shared --> Online[Authority persistence progression and live service]
  World --> Evidence[(Saves replays telemetry assets and audits)]
  Online --> Evidence
  Evidence --> Release[Build platform security compliance and operations]

The host and shared layer supply contracts, not identical behavior. Each cell owns its rules, camera, input semantics, AI specialization, content, and performance envelope inside the shared platform boundaries.

Player action sequence#

sequenceDiagram actor Player participant Input as Input mapping participant Cell as Active cell policy participant GAS as Shared ability runtime participant Authority as Server or deterministic authority participant World as AI and world systems participant Present as Animation camera audio and VFX Player->>Input: Device action Input->>Cell: Cell-specific semantic command Cell->>GAS: Ability request with target context GAS->>Authority: Validate state cost timing and ownership alt refused Authority-->>Present: Rejection or recovery feedback else admitted Authority->>World: Apply governed gameplay effect World-->>Authority: Resulting authoritative state Authority-->>GAS: Confirmed outcome GAS-->>Present: Replicated cue and presentation data Present-->>Player: Cell-specific feedback end

Input mapping, cell semantics, shared ability machinery, authority, world effect, and presentation are different responsibilities. Predictive feedback cannot become the source of truth for a multiplayer or persisted effect.

Durable cell and session records#

Entity-relationship diagramEntity-relationship diagram: 14 entities and 13 relationships.ownsmaintainsversionsconfiguresselectsincludescontrolsrecordsversionscontainsrequiresrecordsproducesACCOUNTPROFILESAVE_SLOTCELL_DEFINITIONCELL_VERSIONSESSIONMODE_DEFINITIONPARTICIPANTREPLAYWORLD_REVISIONPROGRESSION_EVENTCONTENT_BUNDLEASSET_PROVENANCEAUDIT_EVENT
Entity-relationship diagram: Entity-relationship diagram. Entity-relationship diagram: 14 entities and 13 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:
- ACCOUNT
- PROFILE
- SAVE_SLOT
- CELL_DEFINITION
- CELL_VERSION
- SESSION
- MODE_DEFINITION
- PARTICIPANT
- REPLAY
- WORLD_REVISION
- PROGRESSION_EVENT
- CONTENT_BUNDLE
- ASSET_PROVENANCE
- AUDIT_EVENT

Connections:
- ACCOUNT to PROFILE (one to zero or many): owns
- PROFILE to SAVE_SLOT (one to zero or many): maintains
- CELL_DEFINITION to CELL_VERSION (one to zero or many): versions
- CELL_VERSION to SESSION (one to zero or many): configures
- MODE_DEFINITION to SESSION (one to zero or many): selects
- SESSION to PARTICIPANT (one to one or many): includes
- PROFILE to PARTICIPANT (one to zero or many): controls
- SESSION to REPLAY (one to zero or many): records
- SAVE_SLOT to WORLD_REVISION (one to zero or many): versions
- WORLD_REVISION to PROGRESSION_EVENT (one to zero or many): contains
- CELL_VERSION to CONTENT_BUNDLE (one to zero or many): requires
- CONTENT_BUNDLE to ASSET_PROVENANCE (one to zero or many): records
- SESSION to AUDIT_EVENT (one to zero or many): produces
Show source
erDiagram
  ACCOUNT ||--o{ PROFILE : owns
  PROFILE ||--o{ SAVE_SLOT : maintains
  CELL_DEFINITION ||--o{ CELL_VERSION : versions
  CELL_VERSION ||--o{ SESSION : configures
  MODE_DEFINITION ||--o{ SESSION : selects
  SESSION ||--|{ PARTICIPANT : includes
  PROFILE ||--o{ PARTICIPANT : controls
  SESSION ||--o{ REPLAY : records
  SAVE_SLOT ||--o{ WORLD_REVISION : versions
  WORLD_REVISION ||--o{ PROGRESSION_EVENT : contains
  CELL_VERSION ||--o{ CONTENT_BUNDLE : requires
  CONTENT_BUNDLE ||--o{ ASSET_PROVENANCE : records
  SESSION ||--o{ AUDIT_EVENT : produces

Cell, mode, content, profile, session, replay, and world-save versions stay explicit so cross-cell activation, migration, rollback, and incident review do not depend on an ambiguous global version.

Cell session lifecycle#

State diagramState diagram: 15 states and 20 transitions.cell mode and content compatibleentitlement platform or compatibility failureplugins and authoritative data readyplugin asset or migration failureworld and participants synchronizedmode permits governed pausemap phase or cell changecompatible target loadedinterrupted transitionrestore succeedsprior snapshot restoredterminal mode stateresults and world revision commitdurable receipts confirmedSelectingActivatingRefusedLoadingFailedActivePausedTransitioningRecoveringRolledBackCompletedSavingEnded
State machine: State diagram. State diagram: 15 states and 20 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)
- Selecting
- Activating
- Refused
- Loading
- Failed
- Active
- Paused
- Transitioning
- Recovering
- RolledBack
- Completed
- Saving
- Ended
- End (final)

Connections:
- Start to Selecting
- Selecting to Activating: cell mode and content compatible
- Selecting to Refused: entitlement platform or compatibility failure
- Activating to Loading: plugins and authoritative data ready
- Activating to Failed: plugin asset or migration failure
- Loading to Active: world and participants synchronized
- Active to Paused: mode permits governed pause
- Paused to Active
- Active to Transitioning: map phase or cell change
- Transitioning to Active: compatible target loaded
- Transitioning to Recovering: interrupted transition
- Recovering to Active: restore succeeds
- Recovering to RolledBack: prior snapshot restored
- Active to Completed: terminal mode state
- Completed to Saving: results and world revision commit
- Saving to Ended: durable receipts confirmed
- Refused to End
- Failed to End
- RolledBack to End
- Ended to End
Show source
stateDiagram-v2
  [*] --> Selecting
  Selecting --> Activating: cell mode and content compatible
  Selecting --> Refused: entitlement platform or compatibility failure
  Activating --> Loading: plugins and authoritative data ready
  Activating --> Failed: plugin asset or migration failure
  Loading --> Active: world and participants synchronized
  Active --> Paused: mode permits governed pause
  Paused --> Active
  Active --> Transitioning: map phase or cell change
  Transitioning --> Active: compatible target loaded
  Transitioning --> Recovering: interrupted transition
  Recovering --> Active: restore succeeds
  Recovering --> RolledBack: prior snapshot restored
  Active --> Completed: terminal mode state
  Completed --> Saving: results and world revision commit
  Saving --> Ended: durable receipts confirmed
  Refused --> [*]
  Failed --> [*]
  RolledBack --> [*]
  Ended --> [*]

Activation, loading, active play, transition, recovery, save, and result settlement are separately observable. Cell change cannot silently reinterpret an incompatible save or content bundle.

Plugin and contract composition#

classDiagram class V4GameHost { activateCell() activateMode() pinVersions() } class SharedGameplay { abilityContract inputContract animationContract } class CellPlugin { ruleset cameraPolicy aiExtensions } class WorldServices { streaming persistence procgen } class OnlineServices { authority matchmaking progression } V4GameHost --> CellPlugin : activates CellPlugin --> SharedGameplay : specializes V4GameHost --> WorldServices : composes V4GameHost --> OnlineServices : composes SharedGameplay --> WorldServices : affects OnlineServices --> CellPlugin : enforces version

The host controls composition and versions; the shared layer exposes extension contracts; the cell supplies behavior; world and online services remain shared authorities rather than cell-private shortcuts.

Cell and platform estate#

V4 estateMind map: 22 ideas.V4 estateCellsTactical planning andbreachStealth schedules andcommandAction RPG abilities andbossesRTS economy armies anddeterminismArcade run-and-gun stagesShared gameplayGAS animation and inputPerception crowds and AIdirectorWorld streaming andprocgenPresentation UI andaccessibilityProduct systemsCampaign co-op PvP andhordeTraining replay andsignature modesCreator content communityand vaultOnline esports progressionand live servicePlatformBuild data telemetry andperformanceSecurity compliance andtrustHardware peripherals andXRCertification operations andlaunch
Mind map: V4 estate. Mind map: 22 ideas.

Drawn from its Mermaid source.

As text
Tree:
- V4 estate
  - Cells
    - Tactical planning and breach
    - Stealth schedules and command
    - Action RPG abilities and bosses
    - RTS economy armies and determinism
    - Arcade run-and-gun stages
  - Shared gameplay
    - GAS animation and input
    - Perception crowds and AI director
    - World streaming and procgen
    - Presentation UI and accessibility
  - Product systems
    - Campaign co-op PvP and horde
    - Training replay and signature modes
    - Creator content community and vault
    - Online esports progression and live service
  - Platform
    - Build data telemetry and performance
    - Security compliance and trust
    - Hardware peripherals and XR
    - Certification operations and launch
Show source
mindmap
  root((V4 estate))
    Cells
      Tactical planning and breach
      Stealth schedules and command
      Action RPG abilities and bosses
      RTS economy armies and determinism
      Arcade run-and-gun stages
    Shared gameplay
      GAS animation and input
      Perception crowds and AI director
      World streaming and procgen
      Presentation UI and accessibility
    Product systems
      Campaign co-op PvP and horde
      Training replay and signature modes
      Creator content community and vault
      Online esports progression and live service
    Platform
      Build data telemetry and performance
      Security compliance and trust
      Hardware peripherals and XR
      Certification operations and launch

Use this map to select the owning feature and architecture pages before making a cross-cell claim. Shared capabilities still require per-cell acceptance and performance evidence.

Content production journey#

From V4 cell content to supported buildUser journey: 8 stages.1Choose cell mode player promise and authorityDefine. Design. Score 5 of 5.2Author data assets provenance and compatibilityDefine. Content, Engineering. Score 5 of 5.3Implement shared contract and cell specializationIntegrate. Engineering. Score 4 of 5.4Wire world presentation online and telemetryIntegrate. Engineering. Score 5 of 5.5Test target cell and cross-cell regressionsVerify. QA. Score 5 of 5.6Validate performance accessibility security and cookVerify. QA, Release. Score 5 of 5.7Stage platform cohort and prove rollbackRelease. Release, SRE. Score 5 of 5.8Update docs decisions evidence and supportRelease. Owners. Score 5 of 5.
User journey: From V4 cell content to supported build. User journey: 8 stages.

Drawn from its Mermaid source.

As text
Steps:
- 1. Choose cell mode player promise and authority (good). Define. Design. Score 5 of 5.
- 2. Author data assets provenance and compatibility (good). Define. Content, Engineering. Score 5 of 5.
- 3. Implement shared contract and cell specialization (good). Integrate. Engineering. Score 4 of 5.
- 4. Wire world presentation online and telemetry (good). Integrate. Engineering. Score 5 of 5.
- 5. Test target cell and cross-cell regressions (good). Verify. QA. Score 5 of 5.
- 6. Validate performance accessibility security and cook (good). Verify. QA, Release. Score 5 of 5.
- 7. Stage platform cohort and prove rollback (good). Release. Release, SRE. Score 5 of 5.
- 8. Update docs decisions evidence and support (good). Release. Owners. Score 5 of 5.
Show source
journey
  title From V4 cell content to supported build
  section Define
    Choose cell mode player promise and authority: 5: Design
    Author data assets provenance and compatibility: 5: Content, Engineering
  section Integrate
    Implement shared contract and cell specialization: 4: Engineering
    Wire world presentation online and telemetry: 5: Engineering
  section Verify
    Test target cell and cross-cell regressions: 5: QA
    Validate performance accessibility security and cook: 5: QA, Release
  section Release
    Stage platform cohort and prove rollback: 5: Release, SRE
    Update docs decisions evidence and support: 5: Owners

A content preview or cell-only test is insufficient; the supported path includes host activation, shared services, platform packaging, and recovery.

Evidence order#

timeline title V4 release evidence Contract : Cell promise and specialization boundary : Shared schemas plugin and compatibility policy Runtime : Host activation gameplay world and authority : Presentation persistence services and telemetry Verification : Per-cell and cross-cell automated journeys : Accessibility performance security and content evidence Candidate : Cook certification operations migration and rollback : Staged cohort and observability Supported : Named cells modes platforms content versions and regions : Current regression incident and recovery evidence

This timeline orders proof; it does not claim all cells mature together.

How to use this atlas#

Start with the landscape and estate, trace a player action and cell session, review data and composition with the ER/class diagrams, and use the production journey/evidence order at release review. Continue to the V4 guide, feature index, and architecture index.