neon-sprawl/docs/decomposition

Decomposition Workspace

This workspace contains detailed planning artifacts derived from the finalized master plan:

• Source of truth: neon_sprawl_vision.plan.md
• Tech stack baseline: docs/architecture/tech_stack.md
• Scope here: executable decomposition (epics, modules, milestones)

Folder Layout

• epics/ - One file per player-facing epic (E1–E9) with implementation slices.
• tooling/ - Cross-cutting operator tracks (e.g. content authoring) that are not numbered with the nine core epics; same slice style, separate CT.* module IDs.
• modules/ - Contract definitions, client vs server authority, PvP × combat engine, quest scope × party, data reload × telemetry ops, docs vs implementation, full module dependency register (E1–E9 and CT modules), per-module docs, and interface notes.
• milestones/ - Phase-gated implementation tracks and pass/fail checklists.

Working Rules

1. Do not rewrite baseline vision in these files; link back to the master plan.
2. Keep slices backlog-ready (clear owner, dependencies, acceptance criteria).
3. Use stable IDs (E1, E1.M1, etc.) for core game epics; use CT.M1-style IDs for content tooling so tooling stays out of the E1–E9 sequence.
4. Every new slice must reference telemetry and validation where applicable.

Epic files (E1–E9, master plan)

Epic	Document
1 - Core Player Runtime	epics/epic_01_core_player_runtime.md
2 - Classless Progression	epics/epic_02_classless_progression.md
3 - Crafting Economy	epics/epic_03_crafting_economy.md
4 - World Topology	epics/epic_04_world_topology.md
5 - PvE Combat	epics/epic_05_pve_combat.md
6 - PvP Security	epics/epic_06_pvp_security.md
7 - Quest / Faction	epics/epic_07_quest_faction.md
8 - Social / Guild	epics/epic_08_social_guild.md
9 - LiveOps / Integrity	epics/epic_09_liveops_integrity.md

Template for new epics or major revisions: epics/_epic_template.md

Cross-cutting tooling (not E1–E9)

Track	Document	Modules (register)
Internal authoring & content pipeline	tooling/internal_authoring.md	CT.M1–M3

Next Actions

1. Expand slices into engineering tickets; keep module IDs aligned with the master plan.
2. Populate modules/module_dependency_register.md as contracts stabilize.
3. Refine milestones/phase_execution_plan.md with dates and owners when execution starts.