History

VinPropane b68d74b0b8 NEO-57: add prototype resource node catalogs, schemas, and CI gates Four frozen ResourceNodeDef rows and per-node yield tables under content/resource-nodes/ with JSON Schema validation and Slice 2 gates (four nodeDefIds, gatherLens coverage, scrap_metal_bulk yields only).		2026-05-24 13:49:47 -04:00
..
epics	NEO-45: lock prototype salvage mastery catalog, schemas, and CI.	2026-05-16 19:50:09 -04:00
milestones	Initial project vision and decomposition planning baseline.	2026-03-29 16:09:57 -04:00
modules	NEO-57: add prototype resource node catalogs, schemas, and CI gates	2026-05-24 13:49:47 -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: point docs and rules at Linear NEO issue ids	2026-04-13 13:15:32 -04:00

README.md

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.

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, 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.

Linear alignment

Engineering work is tracked as issues in Linear (team NEO), grouped under projects that mirror epics and modules. Do not recreate a Jira-style Feature issue tier—module- or slice-level grouping is labels on the issue only.

Express that grouping with labels (for example the decomposition module id — E1.M1, CT.M2, etc.). Issues belong to a project (e.g. Epic 1, E1.M1, Tech Debt); labels carry scope without a separate Feature work item.

Epic files (E1–E9, master plan)

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

Cross-cutting tooling (not E1–E9)

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

Next Actions

Expand slices into Linear issues under epic/module projects; tag module / slice scope with labels (not a duplicate Feature tier). 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.

README.md Unescape Escape