Labyricorn/Twungeon
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Approve MVP technical and acceptance plans

Browse Source
This commit is contained in:
Labyricorn
2026-08-17 01:08:23 -07:00
parent b08fea918c
commit f3688cd62b
10 changed files with 1929 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.labyricorn/project/contents.lr
+12 -5
View File
@@ -18,7 +18,7 @@ repository_url: https://git.labyricorn.com/Labyricorn/Twungeon
---
default_branch: main
---
tags: Twitch, Twitch Extension, RPGJS, Twurple, TypeScript, game design, pre-development, PRD, MVP, planning, architecture, documentation
tags: Twitch, Twitch Extension, RPGJS, Twurple, TypeScript, game design, pre-development, PRD, MVP, planning, architecture, acceptance testing, documentation
---
body:
@@ -45,8 +45,15 @@ Twurple for Twitch integration, and a Twitch Extension for player controls.
The design keeps Twungeon's game rules separate from RPGJS where practical so
the prototype can be replaced without discarding the validated concept.
The current source of truth is the
The product source of truth is the
[Twungeon MVP Product Requirements Document](https://git.labyricorn.com/Labyricorn/Twungeon/blob/main/Twungeon_MVP_PRD_Current.md).
The project is in pre-development: the PRD and MVP definition are complete,
and this repository will document the transition through technical planning,
implementation, testing, release preparation, and maintenance.
The approved
[technical specification](https://git.labyricorn.com/Labyricorn/Twungeon/blob/main/Twungeon_MVP_Technical_Specification.md)
defines the authoritative architecture and game behavior. The
[acceptance-test and build checklist](https://git.labyricorn.com/Labyricorn/Twungeon/blob/main/Twungeon_MVP_Acceptance_Test_and_Build_Checklist.md)
sequences implementation and maps evidence to all 33 MVP success criteria.
The project remains in pre-implementation planning. These documents establish
the build baseline, but they do not claim that runtime behavior, Twitch
integration, or viewer validation is complete. Future records will document
implementation, testing, release preparation, and maintenance as they occur.