Open-World Narrative · Features

V5 — Features (Page Index)

A focused page within the Open-World Narrative Features documentation. The full map and every sibling page live in the Features hub.

6sections3 minread1diagram

On this page

This directory holds the V5 (a UE5 open-world narrative universe of six "ruleset cells") feature map, decomposed from the single ../V5_features.md hub into focused, in-depth, code-grounded pages. The hub remains the canonical entry point and preserves every section heading; each page below expands one part of the product with richer, code-grounded detail and an honest implemented / spec-only status. The companion architecture reference lives in ../architecture/.

Cross-reference convention. Page-to-page links are relative (./<slug>.md); the architecture companion for a feature page is linked as ../architecture/<slug>.md. Platform-foundation links point at the shared platform/ space.

Feature landscape#

flowchart TB Promise[V5 six-cell open-world narrative promise] --> Cells[Ruleset cells] Cells --> Urban[Urban crime] Cells --> Period[Period drama] Cells --> Frontier[Frontier] Cells --> Hunter[Monster hunter] Cells --> Squad[Galactic squad] Cells --> Vacuum[Hard vacuum] Urban --> Shared[Shared gameplay world narrative and presentation] Period --> Shared Frontier --> Shared Hunter --> Shared Squad --> Shared Vacuum --> Shared Shared --> Mind[Mind Palace evidence deduction and authored cases] Shared --> Product[Modes multiplayer creator workshop online and live service] Mind --> Platform[Accessibility localization rights production world and launch] Product --> Platform

The landscape separates the six-cell product scope from shared foundations and from actual implementation maturity. Each cell owns distinct movement, combat, world, narrative, and content rules; Mind Palace and platform services compose them through versioned contracts.

Use this index to choose the player/cell/cross-cell promise, then pair it with the closest architecture page. Follow authored truth and rights through runtime, authority, persistence, presentation, services, and evidence. Finally check backlog, dependencies, product review, current corpus/assets/code/tests/builds, and release/operational evidence before assigning a completion state. A plugin shell, research note, fixture case, or shared base class does not prove a supported cell.

Every focused feature page appears exactly once below. The V5 documentation guide explains the six-cell truth model and role paths; the diagram atlas provides case, data, state, module, production, and release models. Cross-links preserve relationships without duplicating canonical ownership.

Orientation#

The Six Ruleset Cells#

Cross-Cell Systems#

Modes, Online Services & Live Operations#

Platform, Compliance & Production#