docs: add alpha production readiness plan#159
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 32fafeb9ad
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".
| | Mission risk is legible | Mission card shows expected TIME exposure, reward range, hazards, and recommended role. | Mission data, Mission Board UI | Player enters Gate without understanding risk. | Mission card screenshot and attempt payload. | | ||
| | Gate is short but consequential | Player can verify signal, extract, or push to elite encounter. | Fusion simulation, objective validation, mission state | Gate feels like random combat with no choice. | One partial extract and one full clear smoke. | | ||
| | Outcome has memory | Report shows reward, TIME, body condition, relationship, memory, ledger, and next step. | Nakama ledger, memory, UI report | Player cannot say what changed. | Outcome report screenshot after success and failure. | | ||
| | Body death is not normal respawn | Death screen explains body loss, carryover, cost, and next eligible body. | Reihabitation flow, Body Hall, ledger | Tester says "I respawned." | Controlled death smoke or mocked death state. | |
There was a problem hiding this comment.
Require real body-death flow in acceptance checks
Do not allow a mocked death state to satisfy this row, because the vertical slice requires actual death -> reinhabitation behavior (including cost/carryover handling) as a core loop feature. Keeping mocked death state as an acceptable verification path can mark alpha as ready even when the real server-authoritative death transition is unimplemented, which creates a false readiness signal and pushes a high-risk integration gap into later milestones.
Useful? React with 👍 / 👎.
Summary
Local review
Verification
npx markdownlint-cli2 "docs/design/26-alpha-game-design-document.md" "docs/design/27-alpha-level-design.md" "docs/design/28-character-body-and-roster-design.md" "docs/design/29-alpha-questline-and-encounter-design.md" "docs/design/30-alpha-ux-flow.md" "docs/design/31-alpha-economy-balance-and-playtest-plan.md" "docs/design/32-alpha-art-audio-and-content-direction.md" "docs/design/33-alpha-production-backlog.md" "docs/design/34-alpha-acceptance-matrix.md" "docs/design/35-alpha-content-and-copy-pack.md" "docs/design/12-game-design-document.md" "docs/design/03-systems-index.md" "docs/design/02-vertical-slice-spec.md" "docs/SUMMARY.md" "ROADMAP.md" "CHANGELOG.md"git diff --checkNote
communication with agent failed; content checks passed before commit.