Worthbound Mobile-First MVP Rescope
Worthbound Mobile-First MVP Rescope
Section titled “Worthbound Mobile-First MVP Rescope”Status
Section titled “Status”Canonical Production File
Version: 0.1
Authority Level: Production
Priority: Immediate
Purpose: Re-scope Worthbound into a mobile-first MVP with one board, one loop, four archetypes, and minimal systemic surface area
1. Purpose
Section titled “1. Purpose”This file formally re-scopes Worthbound from a broader financial life RPG vision into a constrained mobile-first MVP.
The purpose of this re-scope is:
- reduce architectural drift
- prevent universe-scale overbuilding
- shorten time to first playable
- focus the product around one proven loop
- align design, implementation, and publishing choices with a realistic first release
This file overrides any earlier assumption that the MVP includes expansive world progression, large content breadth, or deep simulation layers.
2. Re-Scoped Product Statement
Section titled “2. Re-Scoped Product Statement”Worthbound MVP is a mobile-first single-player financial life RPG built around:
- one board
- one repeatable loop
- four archetypes
- a simple event system
- a simple opportunity system
- basic insurance
- a clear passive-income win condition
This MVP is intended to prove:
- the loop is engaging
- the archetypes feel distinct
- financial progression feels meaningful
- protection affects outcomes
- the game is readable and satisfying on mobile
3. Core MVP Law
Section titled “3. Core MVP Law”The Worthbound MVP must obey this law:
One board. One hand-friendly loop. One clear path from paycheck dependence to passive-income escape.
Any feature that does not directly strengthen this law should be removed from MVP scope.
4. Primary Platform
Section titled “4. Primary Platform”Primary Target
Section titled “Primary Target”Mobile-first
Recommended Launch Focus
Section titled “Recommended Launch Focus”Android first
Secondary Possibilities
Section titled “Secondary Possibilities”- iOS later
- desktop test build if useful internally
- web only if it meaningfully helps testing
Platform Implication
Section titled “Platform Implication”All MVP decisions must assume:
- smaller screen
- simpler HUD
- fewer simultaneous systems visible
- shorter turns
- stronger clarity requirements
- tap-first interaction design
Worthbound MVP is not being built as a desktop-first deep simulation.
5. MVP Product Shape
Section titled “5. MVP Product Shape”The MVP is a compact strategy game with one board and one cycle-based loop.
The Board
Section titled “The Board”The player progresses on a single board, lane, map, or turn track.
The board exists to:
- frame the cycle rhythm
- present progression clearly
- organize events and opportunities
- support mobile readability
The MVP does not require multiple boards, multiple worlds, or multi-layer progression structures.
The Loop
Section titled “The Loop”Each cycle, the player:
- receives salary and passive income
- pays fixed expenses
- resolves one event
- chooses whether to take one opportunity or protection action
- updates cash, assets, passive income, and risk state
- continues until win or collapse
This is the MVP loop.
6. Included Features
Section titled “6. Included Features”The MVP includes:
- 1 board
- 1 repeatable progression loop
- 4 playable archetypes
- salary and expense tracking
- cash balance
- simple debt pressure
- passive income
- event cards / event outcomes
- opportunity choices
- basic insurance choices
- simple win condition
- simple fail states
- mobile-friendly UI/HUD
These features define the minimum real product.
7. MVP Archetypes
Section titled “7. MVP Archetypes”The MVP playable archetypes are:
- Skilled Worker
- Professional
- Corporate Climber
- Entrepreneur
These four are chosen because they provide:
- blue-collar and white-collar contrast
- stable and volatile play patterns
- clear difference in income, pressure, and opportunity profile
- strong balance diversity without excessive content burden
The full canon may still recognize six archetypes, but only four are in MVP scope.
8. Event System Scope
Section titled “8. Event System Scope”The MVP event system must be simple, readable, and consequential.
Event Design Goals
Section titled “Event Design Goals”- one event resolved per cycle
- clear immediate impact
- visible relationship to risk and preparation
- low reading burden
- strong emotional legibility
Recommended MVP Event Categories
Section titled “Recommended MVP Event Categories”- expense spike
- income interruption
- bonus or promotion
- repair bill
- family expense
- market dip
- opportunity windfall
- protection-saved loss
Events should test the player’s structure without becoming bureaucratic or overly text-heavy.
9. Opportunity System Scope
Section titled “9. Opportunity System Scope”The MVP opportunity system must present a small set of legible, strategically different choices.
Recommended MVP Opportunity Types
Section titled “Recommended MVP Opportunity Types”- side hustle
- small investment
- practical asset
- business-like asset
- debt reduction
- protection upgrade
Design Rule
Section titled “Design Rule”The player should usually evaluate only a small number of opportunities at a time.
The opportunity system is not a broad marketplace simulator in MVP.
10. Insurance Scope
Section titled “10. Insurance Scope”Insurance remains part of Worthbound’s identity, but it must be simplified for MVP.
MVP Insurance Rule
Section titled “MVP Insurance Rule”Insurance is included as a basic protection system, not a complex policy simulator.
Recommended MVP Coverage Model
Section titled “Recommended MVP Coverage Model”- No Cover
- Basic Cover
- Full Cover
Recommended MVP Insurance Categories
Section titled “Recommended MVP Insurance Categories”- Health Protection
- Income Protection
- Asset Protection
The MVP may defer or simplify life-insurance-specific mechanics if they introduce too much systemic burden.
11. Beneficiary / Legacy Scope
Section titled “11. Beneficiary / Legacy Scope”Beneficiary and legacy mechanics are no longer treated as a full-system MVP requirement.
MVP Rule
Section titled “MVP Rule”Do not build a deep beneficiary or estate system in the first mobile MVP.
Allowed MVP Simplification
Section titled “Allowed MVP Simplification”If needed, use a single lightweight abstraction such as:
- household protection
- family stability bonus
- continuity modifier
Deferred Scope
Section titled “Deferred Scope”The following are post-MVP unless a very simple form proves essential:
- named beneficiaries
- estate transfer logic
- layered continuity systems
- legacy chapter unlocks
12. Win Condition
Section titled “12. Win Condition”The MVP win condition is:
Passive Income >= Total Expenses
This is sufficient for the first release.
The MVP does not require:
- multi-world ascension
- chapter transitions
- dynasty progression
- broad post-win progression systems
The win condition should feel clear, visible, and motivating.
13. Loss / Failure Condition
Section titled “13. Loss / Failure Condition”The MVP should use simple, legible failure states.
Recommended examples:
- cash collapse below recovery threshold
- unresolved debt spiral
- repeated inability to pay mandatory expenses
- catastrophic unprotected interruption with no recovery path
The fail state must be understandable and attributable to player structure, not hidden math.
14. UX Scope
Section titled “14. UX Scope”The MVP UX must be optimized for mobile readability.
Required Qualities
Section titled “Required Qualities”- clear numbers
- few competing panels
- large tap targets
- low jargon
- short decision windows
- simple end-of-cycle summary
Anti-Patterns to Avoid
Section titled “Anti-Patterns to Avoid”- dashboard overload
- too many small stats at once
- insurance-policy-style menus
- deeply nested decision trees
- long event text blocks
The MVP should feel premium and clean, not dense and clerical.
15. Excluded From MVP
Section titled “15. Excluded From MVP”The following are explicitly out of scope for the mobile-first MVP:
- multiple boards or worlds
- universe-scale progression
- deep legacy systems
- full beneficiary architecture
- advanced tax simulation
- broad content trees
- complex portfolio management
- multiplayer
- social systems
- match-3 side mode
- large narrative campaign layers
- desktop-first UI assumptions
- live generative AI features
These exclusions are intentional and protective.
16. Technical Implications
Section titled “16. Technical Implications”The mobile-first MVP should favor:
- simple local save state
- data-driven content
- lightweight architecture
- fast iteration
- low-service dependency
Recommended technical posture:
- no required backend at first
- JSON or lightweight local data for content
- minimal infrastructure
- add cloud systems only if proven necessary later
17. Production Rule
Section titled “17. Production Rule”When choosing between:
- more features and
- a faster, tighter, clearer playable MVP
the MVP wins.
When choosing between:
- realism and
- clarity on mobile
clarity wins.
When choosing between:
- future universe ideas and
- current proof of fun
proof of fun wins.
18. Working Summary
Section titled “18. Working Summary”Worthbound MVP is not a large financial-life universe.
It is a focused mobile-first strategy RPG built to prove one core loop:
- earn
- pay
- endure
- choose
- build
- protect
- escape
That is the product now.