Prototype Readiness and Shared-Benefit Assessment
Decision
The design contains enough material for an immediate paper playtest and enough system definition to begin a two-player Duet implementation. It is not yet ready for public release or award submission.
Existing gameplay loop
- A player chooses an action.
- Personal Tension and shared System Pressure change.
- Thresholds transform the board state.
- Players choose between individual control and cooperation.
- The game reaches a Control, Continuum, or System Collapse ending.
What is already specified
- Player count and setup
- Turn actions
- Personal Tension and shared System Pressure
- Pressure tests and Outbursts
- Trauma and Support tokens
- Three escalating board phases
- Six community-care interventions
- Neutral 16-card pressure/support module with two-path choices
- Competitive, cooperative, and collapse endings
- Debrief questions
- Safety and consent boundaries
Minimum Duet implementation decisions
| Gap | Minimum decision |
|---|---|
| Initial format | Implement two players first; evaluate four players later |
| Board mapping | Identify current Duet squares used for the Void and player sectors |
| Piece mapping | Map Prime, Warden, Guide, and Traveler to existing Duet pieces |
| State display | Display Tension, System Pressure, Trauma, Support, and current phase |
| Timing | Add a round counter and deterministic phase transitions |
| Consent | Provide an explicit accept/refuse interaction for Clinical Care |
| Shared funding | Let both players contribute Support to Care cards |
| Balance | Playtest thresholds of 6, 8, and 10 and all card costs; treat them as provisional |
| Evaluation | Collect anonymous program feedback, never mental-health profiles |
The first digital prototype should remain a two-player Duet scenario. Four-player support adds networking, interface, and balance complexity without improving the first test of the central mechanic.
Chris-driven direction now specified
The repository now contains a documented, reviewable hypothesis grounded in Chris Webby's public discography. The proposed layer adds Own Your Move, Call It Plainly, Crew Check, Receipts, Revision Cycle, and Independent Exit.
These mechanics are original Loptr Lab adaptations. The thematic connection is interpretive until Chris reviews it. No music, lyrics, likeness, voice model, or protected artwork is required to test them.
Shared goal
Build and test an accessible game in which players discover that managing individual behavior cannot repair a system that continually manufactures crisis.
Benefits by participant
| Participant | Legitimate benefit |
|---|---|
| Chris Webby | A separate, optional opportunity to review or participate on his own terms, without being presented as a clinician or asked to mediate another relationship |
| Loptr Lab | Evidence that Veiled Dominion can translate cultural narratives into playable systems |
| Duet | A scenario demonstrating dynamic rules, cooperation, accessibility, and facilitated play |
| Players | An experience showing how orderly systems can generate pressure and why escape without support is incomplete |
| Inpatient | A possible cultural extension based on participation and reflection rather than merchandise alone |
| Community partners | A reusable discussion tool shaped with them and credited through verifiable contribution |
Conditions for mutual benefit
- Usefulness, consent, and measurable impact precede award positioning.
- Interest, silence, or private review never implies affiliation.
- Chris makes an independent participation decision. Ren is not a participant in the continuing project.
- Rights, compensation, approval, withdrawal, and credit are negotiated before any artist participates or protected material is used.
- The prototype is presented as art and facilitated engagement, not therapy or clinical research.
- Award credit follows completed, verifiable work.
Readiness summary
- Paper playtest: ready
- Two-player Duet implementation: ready to begin
- Four-player digital implementation: defer until the core loop is validated
- Public release: not ready; requires testing, partners, permissions, and accessibility review
- Award submission: not ready; requires completed work and documented impact