History

VinPropane 14a6813985 NS-23: Document movement tradeoff — no required obstacle auto-nav Align plan, client/server README, E1.M1 snapshot, and code review note with the chosen design: descend bypass favors smooth stepped surfaces; multi-click around obstacles is OK. NS-24 remains for idle jitter.		2026-04-05 14:56:52 -04:00
..
epics	chore: final branch docs review and Epic 2 E2.M2 note fix	2026-04-03 22:55:21 -04:00
milestones	Initial project vision and decomposition planning baseline.	2026-03-29 16:09:57 -04:00
modules	NS-23: Document movement tradeoff — no required obstacle auto-nav	2026-04-05 14:56:52 -04:00
tooling	chore: add CT content-tooling track and vision plan tooling epic	2026-03-30 23:18:40 -04:00
README.md	chore: document governing design axioms (fun, cyberpunk theme)	2026-04-04 18:46:55 -04:00

Decomposition Workspace

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

Source of truth: neon_sprawl_vision.plan.md — design axioms (fun + distinctly cyberpunk theme) live under Design axioms (governing) in that file.
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.

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, etc.) for core game epics; use CT.M1-style IDs for content tooling so tooling stays out of the E1–E9 sequence.
Every new slice must reference telemetry and validation where applicable.

Epic	Document
1 - Core Player Runtime	epics/epic_01_core_player_runtime.md
2 - Skills and Progression Framework	epics/epic_02_skills_and_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

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

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