- Split dependency table by epic; every Depends On ID is a register row - Add InteractionRequest to E1.M1 contract column per epic 1 - Footnote E4.M3 backend world services; E4.M3 register deps E4.M1 only - Add 28 new module markdown files (E1.M3–E9.M4 gaps) - Link per-module docs index to all 37 files - Cross-link existing module docs; remove obsolete E1.M3 register note from E5.M1 - Update decomposition README modules blurb Made-with: Cursor |
||
|---|---|---|
| .. | ||
| epics | ||
| milestones | ||
| modules | ||
| README.md | ||
README.md
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 epic with implementation slices.modules/- Cross-epic contracts, full module dependency register (all epic modules), per-module docs, and interface notes.milestones/- Phase-gated implementation tracks and pass/fail checklists.
Working Rules
- Do not rewrite baseline vision in these files; link back to the master plan.
- Keep slices backlog-ready (clear owner, dependencies, acceptance criteria).
- Use stable IDs (E1, E1.M1, P1.M1, etc.) to preserve traceability.
- Every new slice must reference telemetry and validation where applicable.
Epic Files
| 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
Next Actions
- Expand slices into engineering tickets; keep module IDs aligned with the master plan.
- Populate
modules/module_dependency_register.mdas contracts stabilize. - Refine
milestones/phase_execution_plan.mdwith dates and owners when execution starts.