docs: tidy data_and_ops_policy table and vision plan links

Widen content-reload policy table columns; use proper markdown links to
neon_sprawl_vision.plan.md (not code-span wrapped URLs).

Made-with: Cursor
pull/6/head
VinPropane 2026-03-30 19:05:49 -04:00
parent 85d3070969
commit 813baa670d
1 changed files with 7 additions and 5 deletions

View File

@ -8,12 +8,14 @@ Prototype-throughearly-pre-production rules for **how gameplay data is loaded
Applies to **JSON/YAML** (or equivalent) loaded by the server: [E2.M1](E2_M1_SkillDefinitionRegistry.md) / [E2.M2](E2_M2_XpAwardAndLevelEngine.md) `LevelCurve` and skill data, items, recipes, quests, zones, etc.
| Environment / phase | Policy |
|---------------------|--------|
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Prototype default** | Load at **process start** after **CI validation** (JSON Schema or agreed validators). No requirement for hot reload in the first milestone. |
| **Development** | Optional **file-watcher reload** or **developer-only** admin endpoint to re-read tables; must be **disabled or authenticated** in any shared/staging/prod-like deploy. Document the switch in server config. |
| **Tuning without redeploy** | Prefer **[E9.M3 — LiveBalanceControlPlane](E9_M3_LiveBalanceControlPlane.md)** and **[E2.M4](E2_M4_ProgressionPacingControls.md)** when those exist—not ad-hoc editing production disk files. |
**E2.M2:** Replace vague “reload policy TBD” with: **boot load** for prototype; optional dev reload as above; production path goes through gated balance patches per tech stack.
---