neon-sprawl/docs/decomposition
VinPropane 137da33dcc docs: quest scope and party rules (#5)
Add quest_scope_and_party.md: per-character QuestStepState default;
QuestDef modes for solo vs party credit and optional leader turn-in;
E8.M1 dependency for party features; E7.M2 per-character rewards;
open-world prototype default; instance_id binding deferred; edge cases
and telemetry.

Register cross-cutting subsection + intro link; update E7.M1, E7.M2,
E8.M1; contracts, decomposition README, tech_stack related docs.

Made-with: Cursor
2026-03-30 18:58:23 -04:00
..
epics Complete Neon Sprawl rename and server project defaults. 2026-03-29 17:24:35 -04:00
milestones Initial project vision and decomposition planning baseline. 2026-03-29 16:09:57 -04:00
modules docs: quest scope and party rules (#5) 2026-03-30 18:58:23 -04:00
README.md docs: quest scope and party rules (#5) 2026-03-30 18:58:23 -04:00

README.md

Decomposition Workspace

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

Folder Layout

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.