Enter the books you love.
Updated: July 16, 2026 02:00 UTC • New: dice test suite (207 tests), server error handling fix, web app expanded to 70KB
| Delivery Item | Status | Completion | Notes |
|---|---|---|---|
| AI DM Service (LLM orchestration + streaming) | ✅ Built | 4 modules (1,191 lines): context-manager, dm-service (18.5KB), llm-provider (21.8KB), prompts. Mock/dev error handling improved (commit 1f35464). |
|
| Rule Engine (D&D 5e core) | ✅ Built | 7 modules: combat, dice, stats, classes, races, character-sheet. Full 5e SRD coverage. Has test suite. | |
| Dice Service | ⚠️ Partial | 4 modules (899 lines): types, random, service, index. Comprehensive test suite added (207 tests, commit 73f04b1). Dice roller UI built (dice-roller.js, 441 lines). Still missing video animations. |
|
| Character Creation & Management | ✅ Built | Model, service, portrait gen. Narrative onboarding flow. Portrait gen needs image API wired up. | |
| Scene Engine + Continuity Validator | ✅ Built | Exit pressure ramps, completion tracking, 4-action system per spec. | |
| Web App (PWA) | ⚠️ Partial | Vanilla HTML frontend (index.html 70.9KB + create.html 22KB). Dice roller UI + 3D physics (dice-roller.js 18.5KB). PWA manifest + service worker done. Not React/framework. | |
| Adventure Content (3 books) | ✅ Built | Dracula (25 scenes), Frankenstein (25 scenes), Sherlock Holmes (25 scenes). Full narrative bug hunt completed — 101 bugs found, 75+ fixed across all 75 scenes. 4 review files on file. Commit ffacd7d. |
|
| TTS Voice Service | 🔨 Building | tts-service.js (408 lines) + index.js (40 lines). TTS service code built. Needs API key and end-to-end test. | |
| Session Management + Message Router | ✅ Built | Persistence + message routing working. | |
| Auth + API Server | ✅ Built | Fastify server (952 lines), token auth, SSE streaming, WebSocket support. Error responses improved for dev/mock mode (commit 1f35464). |
|
| Phase 1 + Phase 2 Test Suites | ✅ Built | 3 test suites (50KB total): phase1.test.js (19KB), phase2.test.js (12KB), dice.test.js (19KB, 207 tests). Commit 73f04b1. |
|
| Coin/XP Scoring Engine | 🔨 Building | coin-engine module (225 lines). Core scoring logic built. Needs AI DM creativity assessment integration. | |
| Combat Manager | ✅ Built | combat-manager.js (438 lines). Initiative, multi-foe encounters, action economy. Integrated with rule engine. | |
| Dynamic Difficulty | 🔨 Building | dynamic-difficulty.js (219 lines). Rubber-band scaling logic built. Needs tuning with playtest data. | |
| Inventory System | 🔨 Building | inventory.js (240 lines). Item tracking, equipment slots. Needs Shoppe marketplace integration. |
| Delivery Item | Status | Completion | Notes |
|---|---|---|---|
| Hosting — Render.com | ✅ Configured | render.yaml + Dockerfile ready. Deploy pending. | |
| Telegram Bot | ⏸️ HELD | Bot built (9KB). READY to deploy. HELD — Lawman to greenlight beta roll-out. | |
| GitHub Repository | ✅ Ready | PAT configured. Code ready to push. | |
| Image Generation Pipeline | ❌ Not Started | Image directory empty. Needs xAI Grok Imagine or equivalent integration. | |
| Voice / TTS Infrastructure | 🔨 Building | TTS service code built (tts-service.js, 408 lines). Needs provider API key and end-to-end integration test. |
| Delivery Item | Status | Completion | Notes |
|---|---|---|---|
| End-to-End Smoke Test | 🔨 In Progress | Partial: signup → NDA → questionnaire → character creation → Dracula Scene 1 all functional. Inventory init fixed (commit 475bc20). Error handling improved (commit 1f35464). Remaining: full adventure playthroughs, session rejoin, spectator mode. |
|
| Narrative Bug Hunting | ✅ Complete | Full audit of all 3 adventures (75 scenes, 15 acts). 101 bugs found: 29 HIGH, 31 MEDIUM fixed. Exit labels, NPC tracking, item tracking, discovery texts, banned keywords all reviewed. 4 review files (787 lines). Commit ffacd7d. |
|
| Beta Signup + Token System | ✅ Built | beta-signups.json + beta-tokens.json + auth/token-store.js all in place. | |
| Telegram Beta Deployment | ⏸️ HELD | Waiting for Lawman's go-ahead. Ask him when ready. |
Three empty directories remain between "code exists" and "playable beta":
src/image/ — No image generation pipeline. Needs Grok Imagine or equivalent.src/frontend/ — Empty. Current web app is vanilla HTML, not the spec'd React framework.src/blockchain/ — Empty placeholder. Phase 3 blockchain integration (NFTs, $BINDING token).data/dice-videos/ — Empty. No dice-roll animation videos recorded.Note: src/voice/ is no longer empty — TTS service code has been built (448 lines). Needs API key to activate.
ffacd7d.The Binding is an AI-powered platform that transforms any book into a live, playable role-playing experience. Users select a book (Dracula, Treasure Island, Gone with the Wind — anything), create a character, and play through the story with an AI Dungeon Master that narrates, adjudicates rules, generates scene images, and speaks in character.
The platform runs cross-platform (mobile, tablet, desktop) and integrates deeply with the Paxeer blockchain for character ownership, a marketplace economy, and community-driven content creation.
The core insight: Every book ever written is an unplayed adventure. The Binding makes them playable.
The Binding is designed to be a flagship consumer application on the Paxeer network — the kind of product that brings mainstream users onto the chain without them needing to understand blockchain mechanics.
| Benefit | Details |
|---|---|
| New wallet creation | Every player who earns $BINDING needs a Paxeer wallet. Projected: 10,000–50,000 new wallets in Year 1. |
| On-chain activity | Character NFTs, $BINDING token, achievement badges, Shoppe marketplace trades, seasonal items — all on Paxeer. Consistent daily on-chain volume. |
| Gas fee revenue | NFT minting, $BINDING conversions, marketplace trades, metadata updates generate gas. Batched transactions keep it efficient. |
| USDC/PAX liquidity | Users purchase with PAX or swap to USDC for marketplace transactions. Drives DEX volume. |
| Ecosystem credibility | A polished, mainstream consumer app proves Paxeer can host production applications — not just DeFi. |
| Segment | Size | Why They Care |
|---|---|---|
| Tabletop RPG players | 50M+ globally | AI DM available 24/7, no scheduling, infinite content, real coin rewards |
| Book readers / BookTok | 200M+ active | “Play through your favorite book” — earn coins while you do it |
| Interactive fiction fans | 30M+ (growing 15% YoY) | AI-driven, every choice matters, replayable, competitive leaderboards |
| Casual mobile gamers | 2B+ globally | Low barrier, narrative-driven, session-based, earn real value |
| Crypto/Web3 curious | 50M+ active wallets | Earn $BINDING by playing, not buying. Meme coin with a real use case. |
| Product | What They Do | The Binding’s Advantage |
|---|---|---|
| AI Dungeon | Text-based AI adventure | No book content, no visuals, no voice, no rules engine, no blockchain, no coin economy, no replayability system |
| D&D Beyond | Digital D&D tools | Requires a human DM and a group. No AI narrative. No coin rewards. No adaptive difficulty. |
| Choice of Games | Interactive fiction | Scripted, not AI-driven. No replayability. No real value earned from play. |
| Replika / Character.ai | AI conversation | Not gameified. No rules, no dice, no progression, no coins, no competition. |
The Binding sits in white space — no existing product combines AI narration + game rules + visual generation + voice + book content + blockchain ownership + intelligence-rewarded coin economy + adaptive replayability + seasonal competition.
| Revenue Stream | Description | Model |
|---|---|---|
| Adventurer’s License | One-time unlock after 5-hour free trial | $1.99 |
| Guild Pass Subscription | Full library, all voices, exclusive cosmetics | $9.99/mo |
| Shoppe Marketplace | NFT item trading between players | Platform fee on each trade |
| Seasonal Cosmetics | Limited-edition items, dice sets, portraits | Direct purchase |
| Adventure Module Sales | Creator-authored adventures | Purchase + creator royalties on resale |
| $BINDING Economy | 0.01% of all revenue feeds the $BINDING liquidity pool | Drives token value for holders |
| Metric | Year 1 | Year 2 | Year 3 |
|---|---|---|---|
| Registered users | 50,000 | 200,000 | 750,000 |
| Paid users (Adventurer’s License) | 20,000 | 80,000 | 300,000 |
| Guild Pass subscribers | 5,000 | 25,000 | 100,000 |
| Monthly recurring revenue | $50,000 | $300,000 | $1,200,000 |
| Shoppe marketplace + cosmetics | $20K/mo | $100K/mo | $400K/mo |
| $BINDING pool contribution | $1K/mo | $5K/mo | $20K/mo |
| Total annual revenue | $840,000 | $4,800,000 | $19,200,000 |
| Asset | Contract Type | Details |
|---|---|---|
| $BINDING Token | ERC-20 | Platform meme coin. Only mintable through gameplay. Tier-weighted conversion from in-game coins. |
| Character NFTs | ERC-721 (dynamic) | Stats, level, equipment, portrait, achievements, tier badges. Updates as character evolves. |
| Guild Pass NFT | ERC-721 (dynamic) | Subscription token. Tiered: Adventurer → Hero → Legend → Mythic. |
| Shoppe Marketplace | Custom | Listings, purchases, royalties, escrow. NFT item trading between players. |
| Tier Badge NFTs | ERC-1155 (soulbound) | Non-transferable. Earned per adventure per season. Displayed on profile. |
| Achievement Badges | ERC-1155 (soulbound) | Non-transferable. Earned through gameplay milestones. |
| Seasonal Leaderboard | On-chain + off-chain | 6-month seasons. Top performers earn bonus $BINDING + exclusive badges. |
| Adventure Module NFTs | ERC-1155 | Purchasable content. Creator royalties on resale (5%). |
| Dice Set NFTs | ERC-1155 | Collectible cosmetic dice. Limited seasonal drops. |
| Shoppe Item NFTs | ERC-721 | Found treasures. Cosmetic + gameplay bonus + tradeable. Seasonal scarcity. |
The platform is designed around a “generous free, irresistible premium” philosophy. No paywalls. Players sign up free, get a 5-hour full-featured trial, then pay $1.99 to unlock permanently. A $9.99/mo Guild Pass subscription provides the full library, all voices, and exclusive cosmetics.
The coin and $BINDING economy creates a play-to-earn layer that doesn’t feel like crypto — players earn coins for playing well, convert them to $BINDING at tier-weighted rates, and spend them in The Shoppe. The only way to get $BINDING is to play. No ICO. No presale. No VC allocation. Just play.
Seasonal leaderboards, limited-edition Shoppe items, and tier badges create engagement loops that drive retention without predatory mechanics. All monetization layers are designed to feel like value, not gates.
| Phase | Goal | Timeline | Team Size |
|---|---|---|---|
| Phase 1 — Core Engine | One playable adventure end-to-end with coin scoring | 4–5 months | 2–3 engineers |
| Phase 2 — Full Experience + Campaign Mode | Multi-adventure, voice, monetization, Shoppe, multi-player D&D | 3–4 months | 3–5 people |
| Phase 3 — Blockchain & Competition | $BINDING token, NFTs, marketplace, leaderboards, seasonal economy | 3–4 months | 4–5 people |
| Phase 4 — Scale | Creator tools, licensed IPs, advanced features | Ongoing (month 11+) | 5+ |
| TOTAL TO FULL LAUNCH | 10–13 months | 2–6 people |
| Deliverable | Effort | Details |
|---|---|---|
| AI DM service (LLM orchestration + streaming) | 4–6 weeks | Context management, 4-suggestion generation, scene narration, NPC dialogue, creative score assessment |
| Rule engine (D&D 5e core) | 3–4 weeks | Standard + Story Mode. Combat, skill checks, saving throws, leveling. Rubber-band difficulty scaling. |
| Coin/XP scoring engine | 2–3 weeks | Intelligence-weighted scoring, theoretical max per adventure, bell curve distribution, hybrid real-time + chapter-breakdown rewards |
| Dice service with animations | 2–3 weeks | 7 die types, 30+ videos, shake detection, fair random |
| Character creation & management | 2 weeks | Narrative onboarding, stats, inventory, portrait, player profile tracking (play style) |
| Adventure engine (scene graph) | 3–4 weeks | Scene navigation, quest tracking, journal, save/load, curated backbone structure |
| Web app (PWA) | 3–4 weeks | React frontend, responsive, WebSocket real-time sync, coin/tier display |
| 3 adventures: Dracula, Frankenstein, Holmes | 6–8 weeks | 75 curated scenes (25 each), NPC pools, encounters, Layer 1 backbone. Full narrative bug hunt — 101 bugs found, 75+ fixed. Commit ffacd7d. |
| Basic voice (1 DM voice) | 1 week | Single TTS voice, text NPCs |
| PHASE 1 TOTAL | 18–24 weeks | ~4–6 months |
Phase 1 Deliverable: Working PWA. User signs up, creates a character, plays through Dracula, Frankenstein, or Sherlock Holmes with AI DM, dice rolls, coin scoring, tier award, basic voice, and scene images. All 3 adventures have been narrative-audited end-to-end (101 bugs found and fixed). Player can see their coin breakdown and tier after each chapter.
| Deliverable | Effort | Details |
|---|---|---|
| All 6 DM voices + NPC voice differentiation | 2–3 weeks | 8–10 preset voice profiles, persistent NPC assignments |
| Player voice input (STT) | 1 week | Web Speech API + Whisper fallback |
| Image pipeline (pre-gen + real-time) | 3–4 weeks | Adventure art, real-time scene images, caching |
| Replayability engine (Layer 2 + 3) | 3–4 weeks | Procedural sub-plot generation, surface variation, adaptive player profiling |
| Quest Mode + Explorer Mode | 3–4 weeks | Story rails vs. sandbox with narrative gravity |
| The Shoppe (basic) | 2–3 weeks | Item display, treasure drops, in-game coin purchasing, inventory management |
| Adventure journal + session recap | 2 weeks | Auto-generated journal, cinematic recap, play style summary |
| 5-hour trial + $1.99 payment | 2 weeks | Clock mechanics, crypto/fiat payment |
| 3 additional adventures (6 total) | 3–4 weeks | Treasure Island, Odyssey, Time Machine (Sherlock Holmes already built in Phase 1) |
| Mobile wrappers (Capacitor) | 2 weeks | iOS + Android, App Store prep |
| Multi-player session management | 2–3 weeks | Join codes, lobby, session rooms, player arrays (extends Phase 1 abstractions) |
| General-purpose AI DM mode | 3–4 weeks | Open-ended improvisation, on-the-fly encounters, world-building. Extends adventure-mode AI DM. |
| Monster stat blocks + initiative | 2 weeks | Data layer for monster stats, initiative tracker, multi-foe combat (extends rule engine) |
| DM whisper system | 1 week | Private messages to individual players (message router already supports targets) |
| Theater of the mind | 1–2 weeks | Verbal spatial descriptions, no grid. Prompt engineering on existing AI DM. |
| Session persistence | 2 weeks | Save/resume across sessions. World state already at session level from Phase 1. |
| PHASE 2 TOTAL | 12–18 weeks | ~3–5 months |
| Deliverable | Effort | Details |
|---|---|---|
| $BINDING ERC-20 token | 3–4 weeks | Token contract, minting logic (gameplay-only mint source), tier-weighted conversion service, wallet integration |
| Seasonal leaderboard system | 3–4 weeks | 6-month seasons, leaderboard resets, seasonal coin budgets, top-performer bonus $BINDING distribution |
| Shoppe marketplace (full) | 4–5 weeks | NFT item listings, purchases, royalties, escrow, seasonal item rotation, lifetime tier discounts |
| $BINDING liquidity pool | 1–2 weeks | DEX integration on Paxeer, revenue-to-pool drip mechanism, deflationary curve implementation |
| Guild Pass subscription + NFT minting | 3–4 weeks | Dynamic NFT contract, tier progression |
| Character NFTs on Paxeer | 2–3 weeks | ERC-721, dynamic metadata, coin/tier data embedded |
| Tier badge + Achievement NFTs | 2 weeks | ERC-1155 soulbound. Per-adventure per-season tier badges. |
| Friend list + party multiplayer | 4–6 weeks | Real-time shared sessions, party chat |
| 15+ adventures total | Ongoing | Content pipeline scaling |
| PHASE 3 TOTAL | 16–22 weeks | ~4–5 months |
| Phase | Monthly Cost | Notes |
|---|---|---|
| Phase 1 (development) | $200–500 | API calls for testing, dev hosting |
| Phase 2 (beta, ~1K users) | $1,000–3,000 | LLM + image gen + TTS scaling |
| Phase 3 (launch, ~5K users) | $4,000–9,000 | Full infrastructure + blockchain deployment + $BINDING liquidity seeding |
| Phase 4 (growth, 50K+ users) | $15,000–40,000 | Auto-scaling, CDN, DEX liquidity |
| Total infrastructure to launch | ~$30K–$80K | Over 9–12 months |
| Role | Phase 1 | Phase 2 | Phase 3 |
|---|---|---|---|
| Full-stack engineer (lead) | 1 | 1 | 1 |
| Full-stack engineer | 0–1 | 1 | 1 |
| AI/ML engineer | 0–1 | 1 | 1 |
| Blockchain engineer | — | 0–1 | 1 |
| Designer | contract | 1 | 1 |
| Content/game designer | 0–1 | 0–1 | 1 |
| TOTAL | 2–3 | 3–5 | 4–6 |
| Component | Contract Type | Phase |
|---|---|---|
| $BINDING Token | ERC-20 (gameplay-only mint) | Phase 3 |
| Character NFTs | ERC-721 (dynamic metadata) | Phase 3 |
| Guild Pass NFT | ERC-721 (dynamic, tiered) | Phase 3 |
| Shoppe Marketplace | Custom (listings, escrow, royalties, seasonal rotation) | Phase 3 |
| Tier Badge NFTs | ERC-1155 (soulbound, per-adventure per-season) | Phase 3 |
| Achievement Badges | ERC-1155 (soulbound) | Phase 3 |
| Shoppe Item NFTs | ERC-721 (cosmetic + gameplay bonus + tradeable) | Phase 3 |
| Adventure Module NFTs | ERC-1155 | Phase 3 |
| Dice Set NFTs | ERC-1155 | Phase 3 |
| $BINDING Liquidity Pool | DEX pair on Paxeer | Phase 3 |
| All gameplay + coin scoring | Off-chain (events queue to blockchain async) | Phase 1+ |
| Time to full launch | 9–12 months |
| Infrastructure cost to launch | ~$30K–$80K |
| Team size at launch | 2–6 people |
| Year 1 projected revenue | $840,000 |
| Year 3 projected revenue | $19,200,000 |
| New Paxeer wallets (Year 1) | 10,000–50,000 |
| $BINDING mint source | Gameplay only (no ICO, no presale, no airdrop) |
| Season length | 6 months with leaderboard reset |
| Adventures at launch | 15+ |
Confirmed design decisions for The Binding's core gameplay systems. These represent the product vision as agreed between the founding team.
Every adventure has a theoretical maximum coin pool — a fixed number based on story length and difficulty. Coins are awarded based on how intelligently you play, not just whether you win.
| Design Element | Decision |
|---|---|
| Scoring method | Hybrid — real-time subtle notifications during play + full breakdown at end of each chapter |
| What earns coins | Intelligence-weighted: creativity, problem-solving, investigation, roleplay, combat efficiency |
| Distribution | Standard bell curve — only 0.01% of players ever max out a single adventure |
| Theoretical max | Fixed per adventure, based on story length + difficulty level |
| Post-chapter summary | “You earned 340/500 coins. Creative Problem Solving (+120), Investigation (+90), Combat (+80), Roleplay (+50)” |
The scoring rubric must be generous rather than stingy — better to reward too often than too rarely at launch. Players should understand what gets rewarded and learn to play better over time.
| Tier | Requirement | Expected Rarity |
|---|---|---|
| Bronze | Complete the adventure | ~95% of players |
| Silver | Earn 60%+ of max coins | ~60% of players |
| Gold | Earn 85%+ of max coins | ~15% of players |
| Platinum | Earn 95%+ of max coins AND finish in top 10% of completion time | ~1% of players |
Key design note: Speed requirement applies ONLY to Platinum tier. Platinum means you played near-perfectly AND efficiently. That’s mastery — the screenshot people share, the badge that makes someone say “how did you do that?”
Coins earned in any adventure are fungible — 1 Dracula coin = 1 Frankenstein coin = 1 Sherlock Holmes coin. Your lifetime balance carries across all adventures, The Shoppe, the meme coin exchange, and your player profile.
| Tier Earned | Conversion Rate | Example: 1,000 coins becomes |
|---|---|---|
| Bronze | 1x | 1.00 $BINDING |
| Silver | 1.5x | 1.50 $BINDING |
| Gold | 2.5x | 2.50 $BINDING |
| Platinum | 5x | 5.00 $BINDING |
| Lifetime Average Tier | Shoppe Discount |
|---|---|
| Bronze average | Full price |
| Silver average | 10% off |
| Gold average | 25% off |
| Platinum average | 40% off + access to exclusive items |
The tier-weighted conversion kills the exploit where someone creates 50 accounts and farms the easiest adventure on the lowest difficulty. Bronze conversion at 1x means that strategy generates almost nothing. The system rewards quality over quantity.
$BINDING is the platform’s meme coin. The only way to earn $BINDING is to play well in The Binding. No ICO. No presale. No airdrop farming. No VC allocation.
| Component | What Happens |
|---|---|
| New Adventures | 2–3 new books drop per season. New stories = new coin pools = fresh leaderboard |
| Season Leaderboard | Resets every 6 months. Top performers get bonus $BINDING + exclusive NFT badges |
| Coin Pool Budget | Each season has a defined minting budget. Controls inflation. |
| The Shoppe | Seasonal items rotate in and out. Creates scarcity and urgency. |
| Legacy Bonus | Players from earlier seasons get a permanent +% on all future conversions. Loyalty rewarded. |
| Era | Seasons | Theme | Economy |
|---|---|---|---|
| Era 1: Founders | S1–S5 | Build core community, 5 adventures, prove the model | Small coin pool, high value per coin. Best Legacy Bonus for early players |
| Era 2: Growth | S6–S15 | Scale to thousands of players, 20+ adventures, marketplace opens | Growing pool, $BINDING becomes tradeable, Shoppe revenue kicks in |
| Era 3: Maturity | S16–S30 | Peak player count, competitive seasons, multiplayer adventures | Stable pool, inflation managed by seasonal caps |
| Era 4: Legacy | S31–S40 | The game is a classic, community-driven content, potential DAO governance | Pool stabilizes, long-term holders rewarded |
| Era | Revenue to $BINDING Pool | Why |
|---|---|---|
| Era 1 | 0.05% | Higher % to bootstrap value. Early coins need to feel worth earning. |
| Era 2 | 0.03% | More players = more total revenue, so % can drop while absolute $ grows. |
| Era 3 | 0.01% | Stable, predictable, sustainable. |
| Era 4 | 0.005% | Pool is self-sustaining, revenue goes to operations + community. |
Control Mechanisms: The season structure gives three powerful levers to prevent the coin economy from spiraling: (1) Seasonal coin budgets cap $BINDING minting per season. (2) Leaderboard resets every 6 months prevent permanent accumulation spirals. (3) Era transitions every ~2.5 years are built-in checkpoints to adjust conversion rates, revenue %, and minting caps.
The same adventure should feel different every time you play it. The story beats stay fixed, but everything between the beats gets reshuffled.
| Layer | What Changes | Quality Control |
|---|---|---|
| Layer 1: Curated Backbone | 20–30 hand-crafted scenes per adventure. Dependency graph. Tested. | Guaranteed quality — the skeleton never breaks. |
| Layer 2: Procedural Connective Tissue | AI-generated transitions, side encounters, sub-plots, NPC moments. | Starts with curated templates, learns player style, shifts toward free generation over time. |
| Layer 3: Surface Variation | NPC personality, dialogue flavor, item descriptions, environmental details. | Easy for LLMs to do well. Always different, never changes structure. |
The AI DM builds a Player Profile as you play — tracking combat affinity, diplomacy, investigation, creativity, risk tolerance, and compassion. It uses this profile to:
The adaptation is invisible. Players should think “this adventure is really varied,” not “the game is testing me.”
At the end of each adventure, players see a summary: “Your play style: Investigator. The game noticed you prefer exploring before fighting.” An optional deep profile view shows full style breakdown for hardcore players.
Players find treasures during adventures — items, artifacts, relics. These items have three properties:
| Property | Details |
|---|---|
| Cosmetic | Displays on your player profile. Shows off your collection. |
| Gameplay Bonus | Small cross-adventure utility. Found Dracula’s Signet Ring? Small bonus in vampire-themed adventures. Meaningful but not game-breaking. |
| Tradeable NFT | Real on-chain asset. Sell to other players in The Shoppe marketplace. The Binding takes a small fee on each trade. |
Anti-pay-to-win guardrail: No item should be powerful enough that buying it replaces playing well. The Shoppe rewards collection and curation, not spending power.
Seasonal scarcity: Items rotate in and out each season. If you were there, you got it. If not, there’s next season.
The difficulty rubber-bands around the player’s level with deliberate power windows — periods where you’re overpowered followed by a challenge spike.
| Fight Type | Frequency | Purpose |
|---|---|---|
| Standard challenge | 70% of fights | Scales closely to your level. Constant engagement. |
| Power window | 20% of fights | Below your level. You feel like a badass. Satisfying. |
| Challenge spike | 10% of fights | Above your level. You need to think creatively. Humbling. |
The AI DM controls the pacing — it knows when to let you feel powerful and when to humble you. This is narrative difficulty design, not just math.
Your character level determines the adventure’s baseline difficulty before you start. A Level 1 player gets an easier Dracula than a Level 10 player — same story, same beats, but enemies scaled, puzzles harder, DCs higher.
The difficulty is invisible. No numbers, no sliders. The AI DM narratively explains why this version is harder: “Word has reached you that this particular incarnation of the Count has grown more cunning. His servants are more numerous, his traps more elaborate.”
Difficulty is story, not a number. A player who thinks “this Dracula is really hard this time” is more engaged than one who thinks “the game scaled enemies to my level.”
The Binding will expand from book-based single-player adventures into a full AI Dungeon Master replacement for standard D&D 5e play. The same engine powers both modes.
| Mode | Description | Players | Content |
|---|---|---|---|
| Adventure Mode | Play through a book (Dracula, Treasure Island, etc.) | Single player | Curated scene graph + adaptive replayability |
| Campaign Mode | Standard D&D with an AI DM — open-ended, improvisational | 2–6 players | AI-generated on the fly, guided by DM prompts |
The multi-player D&D mode is essentially The Binding without the book constraint. Same engine, same AI DM, same rules — just open-ended instead of curated. This doubles the addressable market: “play through books” becomes “your personal D&D DM that’s always available.”
Five architectural patterns are baked into Phase 1 so that Phase 2 (Campaign Mode) is purely additive — no rewrites. Two weeks of architectural discipline in Phase 1 saves 3–4 months of rewriting in Phase 2.
| Pattern | Phase 1 (Now) | Phase 2 (Campaign Mode) | Savings |
|---|---|---|---|
| Session as container | Session holds a player array (length 1) | Add players to the array (length 2–6) | 3–4 weeks saved |
| Player-tagged actions | Every action includes playerId | AI DM processes actions from multiple player IDs | 4–6 weeks saved |
| Shared + private state | World state + private state exist (all visible to 1 player) | Router filters private state per player | 2–3 weeks saved |
| Message router | DmMessage has targets array (length 1) | Router broadcasts shared, whispers private | 2–3 weeks saved |
| Player-agnostic rules | Rule engine accepts arrays of actors | Works for 1 player or 6, zero changes | 0 (already done) |
Net result: Phase 1 takes ~2 extra weeks to build with these abstractions. Phase 2 saves 11–16 weeks of rewriting. The ROI is 5:1 — the best investment in the entire project.
Decided with Lawman: 2026-07-11
Core Principle: The DM never advances a scene unless the player chooses to move on OR the story forces it. Scenes have real weight — the player should feel like they’re in a place, not scrolling past it.
Every scene has a manifest — a checklist of discoverable content:
[EXPLORED: item1, item2] — what the player just discovered| Completion | Pressure Level | What the Player Experiences |
|---|---|---|
| 0–25% | Background | Exit is one of 4 actions, not highlighted. Rich scene descriptions. |
| 25–50% | Gentle nudge | DM weaves in environmental cues. “The coachman coughs outside.” |
| 50–75% | Strong push | World closes in. “The candles burn lower. The coachman calls — he won’t wait.” |
| 75–100% | Story-driven | Hard exit after 4 turns. “The innkeeper locks the door. Time to go.” |
This replaces the old approach where the DM just cycled through canned responses and forced scene transitions.
Decided: 2026-07-11. Phase 2 next, Phase 3 after testing Phase 2 with users.
~2 hours of work. Natural fit for the product.
| Component | Details |
|---|---|
| Session model | Already supports players array (built from Day 1) |
| Player roles | Need: role field on player (host vs spectator) |
| Spectator UI | Need: spectator suggestion panel (visible only to spectators) |
| Host UI | Host sees suggestions as a “community hints” overlay |
| Messaging | Spectators get their own SSE stream with spectator-only messages |
Why this first: Books have one protagonist. This respects the source material and makes the experience feel intentional rather than chaotic.
Needs more design work. Rule engine already supports this.
| Component | Details |
|---|---|
| Character creation | Need: flow for each player joining |
| Turn management | Need: whose turn is it? |
| Information sharing | Need: shared vs private info (whisper system already in MessageRouter) |
| Multi-participant combat | Need: combat encounters with multiple participants |
| Co-op adventures | Need: content written for 2–6 players |
Why later: More complex, more engaging, but needs significant design work on how turns work in a narrative context.
The Binding is a browser-based Progressive Web App (PWA) that streams AI narration, renders dice animations, plays voice audio, and loads scene images in real time. This spec covers the minimum and recommended hardware, browser support, network requirements, and data usage for each phase of the platform.
| Category | Minimum | Recommended | Notes |
|---|---|---|---|
| Smartphone | iPhone SE (2020) / Android 10+ with 3GB RAM | iPhone 13+ / Pixel 7+ / Samsung S22+ | Primary target — 70%+ of players expected on mobile |
| Tablet | iPad (8th gen) / Android tablet with 4GB RAM | iPad Air+ / Samsung Tab S8+ | Best landscape experience for campaign play |
| Desktop | Any machine from 2018+ with 4GB RAM | Modern laptop/desktop with 8GB RAM | Chrome, Edge, Firefox, or Safari |
| Chromebook | Any Chromebook with Chrome 100+ | Recent Chromebook with 4GB+ RAM | Fully supported — runs as PWA |
| Browser | Minimum Version | Support Level |
|---|---|---|
| Chrome / Chromium | v100+ | Full — primary development target |
| Safari (iOS/macOS) | v16+ | Full — voice input uses Web Speech API |
| Firefox | v100+ | Full — all features supported |
| Edge | v100+ | Full — Chromium-based, identical to Chrome |
| Samsung Internet | v17+ | Full — popular on Android devices |
| Opera Mini | — | Not supported — lacks WebSocket/SSE support |
Why PWA? No app store install required. Players open a URL and play. The PWA caches assets (dice animations, UI, fonts) for instant reload and partial offline support. Voice and AI features require an active connection.
| Feature | Min Bandwidth | Recommended | Latency Tolerance | Data per Session (1hr) |
|---|---|---|---|---|
| Text-only gameplay | 64 Kbps | 1 Mbps+ | < 2000ms RTT | 0.5–1 MB |
| + Voice output (DM speaks) | 128 Kbps | 2 Mbps+ | < 1500ms RTT | 2–5 MB |
| + Voice input (player speaks) | 256 Kbps | 3 Mbps+ | < 1500ms RTT | 3–7 MB |
| + Scene images | 1 Mbps | 5 Mbps+ | < 3000ms RTT | 10–30 MB |
| + Multiplayer (spectator join) | 1 Mbps | 5 Mbps+ | < 2000ms RTT | 5–15 MB |
| Full experience (all features) | 2 Mbps | 10 Mbps+ | < 1500ms RTT | 15–50 MB |
Mobile data note: A 1-hour text-only session uses roughly 1 MB — about the same as loading a news article. Voice adds 2–5 MB. Scene images are the heaviest feature (10–30 MB/hour). Players on limited data plans can disable image generation in settings.
| Metric | Target | How We Achieve It |
|---|---|---|
| First contentful paint | < 1.5s | PWA precaching, minimal JS bundle, static shell |
| Text response time | < 500ms | Server-sent events (SSE), streaming LLM responses |
| Voice response time | < 2s | Streaming TTS, audio starts playing before generation completes |
| Dice animation | 60fps, no jank | Pre-baked lottie sprites, GPU-accelerated transforms |
| Image generation | Background, non-blocking | Images load asynchronously — gameplay never waits for art |
| Page interaction (TTI) | < 2s on 3G | Code splitting, lazy-loaded modules, minimal initial bundle |
| Feature | Requirement | Details |
|---|---|---|
| Speaker / headphones | Required for voice features | DM voice, NPC voices, ambient audio, dice sound effects |
| Microphone | Optional | For voice input (player speaks actions). Falls back to text if unavailable or denied. |
| Audio codec support | MP3 / AAC | All modern browsers support both. OGG fallback for Firefox. |
| Item | Size | Details |
|---|---|---|
| PWA cache (initial) | 5–15 MB | App shell, UI assets, fonts, dice animation sprites |
| Cached scene images | Up to 100 MB | Optional — player can clear cache in settings |
| Session data (localStorage) | < 1 MB | Session ID, rejoin code, player preferences, settings |
| Total recommended free space | 150 MB | Comfortable headroom for all cached content |
| Input Method | Support |
|---|---|
| Touch | Primary — tap suggested actions, swipe to scroll, long-press for context |
| Keyboard | Full — tab navigation, enter to submit, number keys (1–4) to select actions |
| Voice | Optional — Web Speech API for input, TTS for output. Graceful fallback to text. |
| Screen readers | Planned — ARIA labels on all interactive elements, semantic HTML throughout |
DRAC-7A3K).| Phase | Expected Load | Infrastructure |
|---|---|---|
| Phase 1 (beta) | 50–200 concurrent sessions | Single Render instance (free tier), in-memory sessions |
| Phase 2 (launch) | 500–2,000 concurrent | Render standard tier, Redis session store, CDN for static assets |
| Phase 3 (growth) | 5,000–20,000 concurrent | Multi-instance Render, Redis cluster, Paxeer Cloud frontend, database persistence |
| Phase 4 (scale) | 50,000+ concurrent | Auto-scaling compute, global CDN, Paxeer-native frontend, sharded session stores |
Every layer is designed to scale independently. The frontend moves to Paxeer Cloud. The session store moves from in-memory to Redis to a database. The coin ledger moves from in-memory to Paxeer smart contracts. The DM brain stays on a compute instance — it's the only layer that truly needs a server.
The Binding is a hybrid application: the game engine runs on a traditional server, and the economy/assets live on the Paxeer blockchain. This is the same architecture every major web3 game uses. A blockchain cannot run a game server, call AI APIs, or serve web pages — but it is the best place to own assets, process payments, and store player reputation.
A blockchain is a ledger, not a computer. The game runs on a computer. The rewards live on the ledger.
| Layer | Where It Lives | What It Does |
|---|---|---|
| Game Engine | Render.com (Node.js server) | Fastify API server, session management, rule engine (D&D 5e dice math, combat, stats), scene engine, continuity validation |
| AI Dungeon Master | Render.com → OpenAI API | Orchestrates player action → context assembly → LLM call → narrative response + 4 suggested actions. Manages hot/warm/cold context tiers for 50+ hour adventures. |
| Frontend (PWA) | Render.com (same server) | Responsive HTML/CSS/JS served as static files. Service worker for offline shell. Polling-based real-time sync. Works on any device with a browser. |
| Player Wallets | Paxeer Network (chain 125) | PAX balance, token holdings, transaction history. MetaMask or any EVM wallet. |
| Character NFTs | Paxeer Network (ERC-721) | Dynamic NFTs that update as characters level up. Stats, portrait, achievements, tier badges on-chain. |
| $BINDING Token | Paxeer Network (ERC-20) | Platform meme coin. Only minted through gameplay. Tier-weighted conversion from in-game coins. |
| Achievement Badges | Paxeer Network (ERC-1155) | Soulbound (non-transferable) tokens earned through gameplay milestones. |
| Marketplace | Paxeer Network (custom contract) | NFT trading between players: adventures, dice sets, cosmetics. Royalties to creators. |
| Need | Why Blockchain Can't Do It | Where It Actually Runs |
|---|---|---|
| AI narration | Smart contracts cannot call external APIs (no HTTP requests from EVM) | Server → OpenAI API |
| Session state | On-chain storage costs gas per write. A 2-hour session = hundreds of state changes = hundreds of gas fees. | Server memory (in-memory, zero cost, instant) |
| Web pages | A blockchain stores data, it does not serve HTML to browsers | Server static file hosting |
| Dice rolling | On-chain randomness requires VRF oracles — expensive, slow, unnecessary for a single-player game | Server-side cryptographic random |
The game is deployed and running on Render.com. This is the simplest, lowest-cost setup for a Paxeer network beta test.
| Component | Service | Monthly Cost | Status |
|---|---|---|---|
| Game server + frontend | Render Starter plan | $7/mo | Needs upgrade from free tier (free tier spins down after 15 min idle — first visitor waits 30-60s) |
| LLM API (AI DM) | OpenAI GPT-4o-mini | $5–10/mo | Needs API key added as env var on Render |
| Total for beta | $12–17/mo | Handles hundreds of playthroughs |
LLM cost breakdown: GPT-4o-mini costs $0.15 per million input tokens. A full Dracula playthrough (~30K tokens) costs about $0.01. One hundred playthroughs cost roughly $1. This is the cheapest model that produces quality narrative. GPT-4o (better quality) costs 10x more — about $0.15 per playthrough. We recommend starting with mini for beta and upgrading to GPT-4o for launch.
| Testing Phase | What Players Need | What We Need |
|---|---|---|
| Phase 1 Beta (now) | Just a URL. Open in any browser. No wallet needed. No install. | Render paid tier + OpenAI API key |
| Phase 2 Beta (wallet connect) | Paxeer wallet (MetaMask) + small PAX balance for gas | Wallet connection UI + smart contract for coin payouts |
| Phase 3 Launch (full on-chain) | Paxeer wallet + PAX for transactions | Deployed smart contracts (NFTs, marketplace, $BINDING token) |
LLM_API_KEY env var on Render.| Concern | How It's Handled |
|---|---|
| No PII on-chain | Player names, emails, and game actions never touch the blockchain. Only wallet addresses and token balances are public. |
| HTTPS everywhere | All API traffic encrypted in transit. Render provides TLS certificates automatically. |
| Session isolation | Each game session is fully isolated. No data leaks between sessions or players. |
| LLM data handling | Player actions are sent to OpenAI for narration. No player identity data is included. Conversation history is ephemeral. |
| Smart contract safety | Contracts use OpenZeppelin standards. All contracts audited before mainnet. Agent wallet has spend limits enforced at the network layer. |
| Rejoin code security | Short-lived, session-scoped codes. Rate limiting prevents brute force. |
| Stage | Users | Infrastructure | Cost |
|---|---|---|---|
| Beta (now) | 50–200 Paxeer testers | Single Render instance, in-memory sessions | $12–17/mo |
| Launch | 500–2,000 concurrent | Render standard tier, Redis for sessions, CDN for static assets | $50–100/mo |
| Growth | 5,000–20,000 concurrent | Multi-instance, Redis cluster, Paxeer Cloud frontend | $200–500/mo |
| Scale | 50,000+ concurrent | Auto-scaling compute, global CDN, sharded sessions | $1,000–3,000/mo |
The game engine is the only layer that needs a server. Everything else — frontend, assets, economy — can move to decentralized infrastructure over time. The architecture is designed so each layer scales independently.
Real-time 3D physics-based dice. Click any die to roll it — the die tumbles with gravity, bounces off the table, and settles on a random result.
Click any die to roll with real-time 3D physics. The die tumbles with gravity, bounces off the table, and settles on a random result. Tap the overlay to dismiss after the number appears.