don
/
neon-sprawl-archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
neon-sprawl-archived/docs/decomposition
History
don 25c0dd37e2 Document tech stack, README, and align prototype critical path with modules. 
Add locked C# / .NET 8 + Godot baseline in docs/architecture/tech_stack.md and
README; link stack from vision plan and decomposition index. Fix vision plan
module graph and lists: include E1.M4 (AbilityInputScaffold) after E5.M1 and
E2.M3 in pre-production additions; update Solo-Dev build order accordingly.

Made-with: Cursor
 		2026-03-29 17:04:37 -04:00
..
epics Update module dependency register and README with new epic documentation and refined next actions. Added SecurityTierZoneFlags module and clarified dependencies in the planning documents. 2026-03-29 16:47:37 -04:00
milestones Initial project vision and decomposition planning baseline. 2026-03-29 16:09:57 -04:00
modules Update module dependency register and README with new epic documentation and refined next actions. Added SecurityTierZoneFlags module and clarified dependencies in the planning documents. 2026-03-29 16:47:37 -04:00
README.md Document tech stack, README, and align prototype critical path with modules. 2026-03-29 17:04:37 -04:00

README.md

Decomposition Workspace

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

  • Source of truth: cyberpunk_mmo_vision_86a57ef3.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, dependency register, 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, P1.M1, etc.) to preserve traceability.
  4. 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

  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.