Twungeon · Devlog
Twungeon adopts an acceptance-led MVP build plan
With the technical specification approved, Twungeon gained a sequenced ten-phase build checklist and 33 traceable acceptance tests that define the evidence required before the MVP can be called complete.
Twungeon's technical specification was approved as the implementation baseline, and planning moved into an acceptance-led build sequence. This remains a design and execution milestone: no runtime feature, Twitch integration, or viewer test is represented as complete merely because its checklist now exists.
The build plan organizes implementation into ten gated phases after the planning baseline. It begins with reproducible tooling and a framework-independent domain core, then adds dungeon generation, the local turn loop, Goblin behavior, player and floor lifecycles, production-shaped APIs and views, Twitch identity and chat, Bits resurrection, and finally independent setup and real-viewer validation. Each phase has a checkpoint intended to catch failures before work moves into a more expensive external integration layer.
The acceptance matrix assigns AT-001 through AT-033 directly to the PRD's 33 success criteria. It distinguishes automated domain evidence from browser, clean-install, live Twitch, multi-viewer, documentation, usability, and concept- validation evidence. A mock cannot close a live Twitch criterion, and a checked item can be reopened if later evidence invalidates it.
The plan also defines standard quality gates, evidence records, clean-checkout verification, change control, and the final MVP acceptance decision. Planning work is checked off where it is complete; every implementation and validation item starts unchecked.
The execution baseline is the Twungeon MVP Acceptance-Test and Build Checklist, used with the approved technical specification and the authoritative MVP PRD.
The repository baseline for this planning milestone is
commit f3688cd62bccc25c22a9780f65d719104989104f.