Track alpha demo implementation umbrella

[JOY]

Source

• docs/design/128-alpha-route-camera-readability-and-screenshot-gates.md
• docs/design/127-alpha-location-naming-and-map-label-contract.md
• docs/design/26-alpha-game-design-document.md
• docs/design/47-alpha-execution-tracker.md
• docs/design/70-alpha-route-and-evidence-script.md
• docs/design/90-alpha-scene-blockout-object-list-and-shot-plan.md
• docs/design/112-alpha-map-implementation-slice-order-and-cut-plan.md
• docs/design/114-alpha-map-playtest-evidence-manifest.md
• docs/design/115-alpha-map-implementation-issue-split-and-agent-packets.md
• docs/design/123-alpha-full-route-evidence-pack-builder-brief.md
• docs/design/148-open-design-decision-backlog.md
• docs/setup/alpha-open-issue-handoff-coverage.md
• docs/setup/alpha-playable-loop-handoff-coverage.md
• docs/playtests/_templates/alpha-route-full-pass/README.md

Purpose

Track the remaining alpha demo implementation work that is currently described across ROADMAP, source design docs, decision backlog, and evidence templates.

This is a tracking issue only. Do not implement directly from #260.

Scope

• Core Loop V1 implementation across The Garden, Gate prep, Gate mission, outcome report, offline-agent return, and reinhabitation touchpoints.
• Alpha map implementation order: M0 scene skeleton, M1 Garden interaction layout, M2 Gate entry and first combat, M3 proof/extract/outcome return, M4 optional full-clear pressure, and M5 presentation pass.
• Full alpha route evidence: body identity, Garden orientation, focused NPC, facility action, Mission Board, Gate attempt, threshold safety, first combat, proof, extraction, outcome report, and Garden return consequence.
• Server authority boundaries for body, mission, combat, objective, reward, TIME, SECOND, inventory custody, memory, relationship, LLM output, and client UI.
• Player-facing evidence packs, scorecards, state excerpts, screenshots, console summaries, known gaps, and readiness verdicts.
• Route labels, map copy, and evidence notes must respect Dayton real-city usage and TIME-class geography decision rows before final player-facing wording is accepted.

Child Implementation And Evidence Issues

• Build M0 Garden to Gate route skeleton #280 Build M0 Garden to Gate route skeleton.
• Build M1 Garden interaction layout anchors #282 Build M1 Garden interaction layout anchors.
• Build M2 Gate entry and first combat lane #283 Build M2 Gate entry and first combat lane.
• Build M3 proof, extract, and outcome return path #284 Build M3 proof, extract, and outcome return path.
• Build M4 optional Toll Plaza full-clear pressure #285 Build M4 optional Toll Plaza full-clear pressure.
• Build M5 route presentation pass #286 Build M5 route presentation pass.
• Capture full alpha route evidence pack #287 Capture full alpha route evidence pack.

Connected System Issues

• Implement server-authoritative combat damage prototype #26 Combat authority.
• Build prototype reincarnation presentation flow #30 Body death and reinhabitation presentation.
• Add Gate outcome report ledgers for living roster consequence #137 Gate outcome report ledgers.
• Build Garden roster and Gate prep UI #138 Garden roster and Gate prep UI.
• Add focused NPC portrait and speaking animation to dialogue UI #139 Focused NPC portrait and speaking animation.
• Add AI NPC debug tools and Play Mode verification checklist #140 AI NPC debug tools.
• Convert prototype HUD and chat surfaces to production UGUI/TMP panels #141 Production UGUI/TMP HUD and chat.
• Implement offline-agent policy UI and return report #149 Offline-agent policy UI and return report.
• Add alpha inventory and equipment UI flow #218 Inventory and equipment UI.
• Add AI NPC believability smoke tests and evidence pack #251 AI NPC believability evidence.
• Implement Garden visible memory and personalization slice #256 Garden visible memory.
• Track expanded gameplay ledgers and reward authority #261 Reward ledger authority.
• [Animation] Data-driven body, weapon, and timing profile registry #278 Animation profile registry.
• Migrate runtime payloads to seven core stat contract #281 Seven core stat runtime contract.
• Track scoped NPC voice sessions and playback implementation lane #288 Scoped NPC voice sessions.
• Harden remaining inventory custody guards and audit safety #289 Inventory custody guards.

Readiness Gate

#260 is not ready until:

• M0-M3 can be walked or reviewed from evidence without hidden debug-only controls.
• Capture full alpha route evidence pack #287 full-route evidence pack is filled.
• Promotion gate notes from child evidence say whether each next slice is promoted, blocked, or mock-only, and whether Track alpha demo implementation umbrella #260 is ready, blocked, or internal-demo only.
• Body, mission, combat, objective, outcome, reward, ledger, memory, and Garden consequence states have excerpts or honest mock notes.
• Authority notes confirm no client-only reward, no client-only mission clear, no LLM state mutation, and no hidden debug dependency.
• Route labels and player-facing map copy follow the current Dayton and TIME-class geography decisions, or clearly mark unresolved wording as blocked.
• Known gaps are mapped to owner issues.
• M4 and M5 are labeled optional unless JOY changes alpha route scope.
• Unity validation happens in the integration workspace or a locked validation workspace only.

Notes

Use child issues for implementation. Use #260 to judge whether the overall alpha demo route is ready, internally demo-ready, or still blocked by missing evidence.

[JOY]

Tracking update, 2026-05-29:

Added #281 for migrating runtime payloads, Body Hall/HUD, skill requirements, inventory requirements, and AI/NPC context to the seven canonical core-stat contract.

Source doc:

• docs/design/117-alpha-core-stat-contract-and-migration-handoff.md

Important contract:

• Canonical stats: strength, dexterity, vitality, perception, intelligence, presence, luck.
• endurance and focus are legacy compatibility only.
• Do not expose focus or endurance as allocatable/player-facing core stats.

[JOY]

Tracking update, 2026-05-29:

Added #282 for the M1 Garden interaction layout lane.

Source docs:

• docs/design/118-alpha-m1-garden-interaction-layout-builder-brief.md
• docs/playtests/_templates/alpha-map-slice-M1/

Scope summary:

• Clinic / Body Hall pad
• Repair Row check pad
• Training Target pad
• Signal Mast sweep pad
• Memorial Rail or Notice Wall marker
• five focus NPC primary anchors
• five focus NPC dialogue parking spots
• pad overlap / clearance evidence