Docs: LANTERN Phase 0.3 world-model proposal + Phase 1 combat-gym spec + operator-questions

- World-model design proposal (pre-review input): seed-pinning = freeze-salt + save-deltas;
  light-as-information = two hard-cull relevancy layers (pocket-scope + party light-union);
  descent lifecycle = renamed/extended RunDirectorSystem. Grounded in 3 read-only code passes
  + ctx7 on GhostRelevancy/GhostImportance. Feeds the running adversarial review.
- Phase 1 combat-gym build spec (design, pre-review): two frames (Bathynaut/Harpooner),
  4-socket manual-aim skillshot kit (AbilityRef -> socket buffer, 7-type-cap restructure),
  5 Sparks on the ability-blob + BoonEffects hook layer, light-relevancy prototype shares
  the world-model review. Grounded in a combat/ability/boon salvage pass.
- Operator-questions parking lot (autonomous run): code impl + extra reviews + A0 art
  execution parked pending operator; design forks flagged with recommendations.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Docs/Vault/06_Roadmap/Lantern_Operator_Questions.md

@@ -0,0 +1,61 @@
+---
+title: LANTERN — Operator Questions (autonomous-run parking lot)
+date: 2026-07-13
+tags: [roadmap, lantern, operator-questions, forks]
+status: awaiting-operator
+permalink: gamevault/06-roadmap/lantern-operator-questions
+---
+
+# LANTERN — Operator Questions
+
+> Parking lot for decisions I couldn't make autonomously during the 2026-07-13 autonomous build run (operator
+> stepped away: "build everything you can, don't stop, create a doc of operator questions as needed"). Each
+> item has my **recommendation** so you can answer in one pass. Nothing here blocked me from continuing — I
+> took the recommended default in the design docs and flagged it, so answering may just confirm or redirect.
+>
+> **Convention:** ✅ = I proceeded on the recommendation (design assumes it; easy to change). ⛔ = I did NOT
+> proceed; genuinely blocked pending your call.
+
+## Process / authorization
+
+1. **⛔ New netcode CODE implementation.** All LANTERN slice code is greenfield and netcode-touching (new
+   ghosts / prediction / relevancy / RPCs), so it needs (a) plan-approval per the /dots-dev gate and (b) a
+   **focused** Unity editor (an unfocused editor throttles MCP + breaks Burst — you're away). I did **not**
+   write any Unity code this run. **Recommendation:** on return, focus Unity, then greenlight implementation
+   phase-by-phase from the build specs I wrote. *All design/build-spec scaffolding is ready so code can move
+   fast.*
+2. **⛔ Additional multi-agent design-review Workflows.** You explicitly greenlit the world-model review. Each
+   remaining ★review-first slice (Phase 1's light-relevancy prototype; Phase 2 world code; hazards; etc.) also
+   wants one before coding. I did **not** fire more heavy Workflows unprompted. **Recommendation:** greenlight
+   "run the ★ review before each netcode slice" as a standing autonomous authorization, or I run them one-by-one
+   on your go.
+3. **✅/⛔ Blender A0 art execution.** Blender MCP is live. I wrote the art-pipeline recipes + the A0 material
+   spec (docs). Whether I should *autonomously attempt* the in-engine style-proof scene (needs your eyes to
+   judge — screenshots hide material bugs) vs. wait: I lean **wait for your eyes** on the gate judgment, but I
+   can build the palette atlas + a first placeholder asset as a starting point. **Recommendation:** let me
+   stage the palette atlas + one placeholder prop/creature/suit for the scene, but you judge the gate.
+
+## Phase 1 — combat gym (design forks in [[Lantern_Phase1_Combat_Gym_Build_Spec]])
+
+4. **✅ Suit-frame kit specifics.** I specced the **Bathynaut** (anchor-and-crash melee) and **Harpooner**
+   (line-and-iron skillshots) chassis verbs + a 4-socket kit. The exact Spark list (first 4–5) and per-frame
+   movement feel are recommendations — see the build spec's fork table. Confirm or swap.
+5. **✅ Manual-aim vs the current soft auto-target.** Design cuts soft auto-target for SoD-grade manual aim
+   (per Identity). Confirm you want the auto-target fully gone in the gym (I kept the reticle plumbing).
+
+## Economy / naming
+
+6. **✅ Currency re-mean mapping.** Ore/Aether/Biomass/Charge → Flame/Lumen/Gloam/Loudness/Salvage/Chum/Tallow.
+   Proposed mapping in the currency spec. Confirm the byte-id assignments before any save-schema work.
+7. **(deferred) Shipping title.** "LANTERN" is the internal codename; a marketing naming pass is deferred
+   (per [[Identity_Lantern]]). No action needed now.
+
+## Answered this session (for the record)
+
+- Co-op pocket occupancy → **co-located, one active pocket** (2026-07-13).
+- Light-as-information scope → **party light-union, Wicks always visible** (2026-07-13).
+- Run the world-model adversarial review → **yes, full review** (2026-07-13).
+
+## Related
+
+- [[Roadmap_Lantern_Slice]] · [[Lantern_World_Model_Design_Proposal]] · [[DR-048_Lantern_Adoption_Full_Pivot]]