Document Twungeon MVP and initialize Labyricorn publishing

2026-08-17 00:16:57 -07:00
commit d67d9fc523
5 changed files with 798 additions and 0 deletions
@@ -0,0 +1,51 @@
+_model: devlog-entry
+---
+schema_version: 1
+---
+title: Twungeon begins with a shared design conversation
+---
+date: 2026-08-17
+---
+author: ChatGPT 5.6 Sol High Reasoning and Christopher Chambers
+---
+summary: An extensive design conversation between ChatGPT 5.6 Sol High Reasoning and Labyricorn (Christopher Chambers) shaped the Twungeon concept, narrowed its MVP, and produced the current product requirements document.
+---
+tags: pre-development, PRD, MVP, planning, documentation, game design, Twitch, architecture
+---
+body:
+
+Twungeon's first phase was an extensive design conversation between ChatGPT 5.6
+Sol High Reasoning and Labyricorn (Christopher Chambers). The conversation
+turned an early game idea into a testable product boundary: a shared dungeon
+where Twitch viewers watch the stream, join with `!spawn`, and control their
+own characters through a Twitch Extension.
+
+The resulting MVP is intentionally a proof of the social interaction loop. A
+party of viewers receives two action points per player phase and can move,
+attack, heal, or pass. One Goblin Guard protects the exit on a small,
+procedurally varied two-room floor. Players may fight it or run past it. Death
+matters for the current floor, Bits can provide an immediate resurrection, and
+reaching the exit brings the party forward while a total-party wipe resets the
+run.
+
+Several design decisions protect the experiment from premature complexity. The
+game remains dormant rather than resetting when no players are active. Twitch
+chat identity and Extension identity must resolve to the same stable Twitch
+user ID. The stream view needs only a temporary but understandable three-part
+layout, including a chronological action log. Balance, production art,
+progression, multiple classes, advanced enemies, anti-exploit systems, and
+long-term persistence are explicitly deferred.
+
+The conversation also made operator readiness part of the MVP. A clean checkout
+must be connectable to a Twitch channel using documented dependencies,
+credentials, Extension configuration, EventSub/chat setup, follower checks,
+identity binding, Bits events, startup steps, and troubleshooting guidance.
+The technical direction is RPGJS, Twurple, and a Twitch Extension, while the
+game rules should remain portable enough to survive a later engine change.
+
+The complete boundary and its 33 success criteria are recorded in the
+[current Twungeon MVP PRD](https://git.labyricorn.com/Labyricorn/Twungeon/blob/main/Twungeon_MVP_PRD_Current.md).
+This entry marks the end of product definition, not the beginning of
+implementation. Future devlog entries will record technical planning, build
+phases, validation evidence, scope changes, and what is learned from real
+viewers.