Worthbound Design Pillars

Worthbound Design Pillars

Status

Canonical Core File
Version: 0.2
Authority Level: Core
Depends On:

• 00-Core/00-Worthbound-Design-Constitution.md
• 00-Core/01-Game-Identity.md
• 00-Core/Project-Stages.md
• 09-Production/00-Mobile-First-MVP-Rescope.md

---

1. Purpose

This file defines the non-negotiable design pillars of Worthbound.

These pillars are not marketing phrases.
They are working filters.

Every future mechanic, content set, UI decision, archetype, and implementation choice should be tested against these pillars.

If a feature violates these pillars, the feature is wrong, oversized, or misplaced.

For the current project phase, these pillars must be read through the lens of the mobile-first MVP.

---

2. Pillar 1 — Financial Life Paths, Not Flat Classes

Worthbound archetypes are not shallow role labels.

They are distinct financial life paths shaped by:

• income level
• obligations
• household pressure
• risk profile
• opportunity access
• lifestyle pressure
• insurance sensitivity
• likely path to freedom

The player is not choosing the “best-paying class.”
The player is choosing the kind of financial life they want to navigate.

Design Test

Ask:

• Does this archetype feel like a real financial life pattern?
• Does it create a distinct mastery story?
• Would this still feel meaningfully different if salary numbers were hidden?

If not, the design is too shallow.

---

3. Pillar 2 — Asymmetric but Fair

Worthbound is not balanced by sameness.

Different archetypes may have:

• different salaries
• different expenses
• different risks
• different opportunity lanes
• different fragility points

Balance means:

• different pressures
• different strengths
• different traps
• different escape routes
• equal viability through mastery

A high salary must never automatically mean easy mode.
A lower salary path must never automatically mean hopeless mode.

Design Test

Ask:

• Does this path win differently rather than merely more slowly?
• Does this advantage create a real counterweight?
• Is one lane secretly the default optimal choice?

If one path dominates too easily, balance law has failed.

---

4. Pillar 3 — Protection Is Gameplay, Not Decoration

Insurance and protection systems are not flavor taxes.

They must:

• reduce catastrophic downside
• preserve progress
• support continuity of a run
• unlock safer strategic action
• make preparation feel meaningful

Protection should create the feeling:

• “I survived because I planned.”
• “I could take this risk because I was covered.”
• “The setback hurt, but it did not erase me.” :contentReference[oaicite:2]{index="2"}

Design Test

Ask:

• Does protection change real outcomes?
• Does protection preserve momentum?
• Does the player feel the difference between protected and unprotected play?

If protection only acts as a passive cost, the system is badly designed.

---

5. Pillar 4 — Ownership Beats Optics

Worthbound should repeatedly reward structural ownership over surface performance.

The game should reveal that:

• status spending can trap high earners
• visible income is weaker than resilient cashflow
• small owned systems may outperform large performative lifestyles
• assets, reserves, and protection create real freedom

This pillar must be especially visible in archetypes with high earning potential and high lifestyle pressure.

Design Test

Ask:

• Does this feature reward real ownership or fake success?
• Does this choice increase resilience or merely appearance?
• Is the player being tempted into a meaningful trap?

If optics beat ownership too often, the identity is drifting.

---

6. Pillar 5 — Teach Through Consequence, Not Lecture

Worthbound should not feel like coursework.

The player learns because the system makes truth visible.

The strongest learning moments come from:

• salary failing to solve overspending
• a small asset changing the run
• insurance preventing collapse
• an interruption exposing fragility
• discipline outperforming status consumption

Design Test

Ask:

• Does the player discover the lesson through play?
• Is this mechanic emotionally legible?
• Is this teaching embedded in consequence rather than text explanation?

If the game must stop and lecture to make the point, the design is weak.

---

7. Pillar 6 — Approachable, Not Bureaucratic

Worthbound deals with serious financial ideas, but it must remain readable and playable.

The game must avoid:

• jargon overload
• policy-detail swamp
• spreadsheet-first interfaces
• front-loaded complexity
• realism that kills clarity

The player should feel:

• oriented
• capable
• challenged
• informed
• invited into mastery

Insurance, debt, assets, and opportunities should be simplified into strategic choices, not administrative chores. :contentReference[oaicite:5]{index="5"}

Design Test

Ask:

• Can the player understand the decision quickly?
• Is the complexity strategic rather than clerical?
• Does the interface feel like a game rather than a form?

If the system creates paperwork feelings, simplify it.

---

8. Pillar 7 — Mobile-First Readability

Worthbound MVP must feel strong on a phone screen.

This means:

• few competing panels
• strong visual hierarchy
• short readable turns
• large tap targets
• compact but meaningful information
• low friction between decisions

The mobile version must not feel like a desktop game compressed into a smaller rectangle.

Design Test

Ask:

• Can the core state be understood at a glance?
• Is the decision count appropriate for a small screen?
• Does this screen reduce or increase cognitive clutter?

If a feature needs a large dashboard to be usable, it is too heavy for MVP.

---

9. Pillar 8 — Every System Must Support the Core Loop

Worthbound is a cycle-based progression game.

That means every system must strengthen the loop:

1. receive income
2. pay obligations
3. resolve an event
4. evaluate opportunities or protection
5. make a strategic choice
6. advance toward escape

If a mechanic does not reinforce this cycle, it is a distraction. :contentReference[oaicite:6]{index="6"}

Design Test

Ask:

• Where does this mechanic live in the cycle?
• What decision does it deepen?
• How does it affect momentum, fragility, or freedom?

If the answer is unclear, the system is not integrated.

---

10. Pillar 9 — Pressure Must Be Real, But Never Pointless

Worthbound should feel tense, but not cruel.

Pressure is necessary because pressure reveals system strength.
But punishment without decision-value is bad design.

Setbacks should:

• test preparation
• reveal fragility
• encourage adaptation
• reward foresight
• preserve the possibility of recovery

Severe events should matter, but they should not feel arbitrary when good planning exists.

Design Test

Ask:

• Did the player have meaningful ways to prepare?
• Did the setback reveal a system weakness?
• Does recovery remain possible?

If the game feels randomly punitive, event design has failed.

---

11. Pillar 10 — Premium Clarity Over Raw Simulation

Worthbound must feel polished, modern, and premium.

This means:

• clear information hierarchy
• strong visual readability
• meaningful feedback
• elegant abstraction
• emotional consequence without excessive realism

The project should not chase simulation depth for its own sake.

The standard is: enough realism to feel true, enough abstraction to stay playable.

Design Test

Ask:

• Is this feature becoming more realistic at the cost of identity?
• Is this abstraction preserving the important truth?
• Does this improve the premium feel of the game?

If realism creates friction without stronger play, reduce it.

---

12. Pillar 11 — One Board, One Strong Loop

The current MVP is not being built as a broad financial universe.

The current MVP law is:

One board. One hand-friendly loop. One clear path to passive-income escape.

This pillar has veto power over:

• oversized system branching
• excessive content breadth
• multi-board assumptions
• universe-scale progression promises

Design Test

Ask:

• Does this strengthen the one-board loop?
• Does this improve mobile play clarity?
• Does this help players reach and understand the escape goal?

If not, it belongs outside MVP.

---

13. Pillar 12 — The Main Product Comes First

Worthbound is a mobile-first financial life RPG first.

Other modes may exist later, including the earlier match-based prototype direction, but they are secondary unless explicitly promoted later.

No side mode is allowed to distort the identity, resourcing, or architecture of the main product.

Design Test

Ask:

• Does this support the main financial life RPG?
• Is this side mode stealing design attention from the core loop?
• Does this make the main game clearer or weaker?

If a side mode begins to lead the product, priority has been lost.

---

14. Pillar 13 — Documents Are Primary, Prompts Are Secondary

The Master Ledger is the project’s external memory.

Canonical documents should define:

• terminology
• structure
• laws
• system logic
• implementation constraints

Architectured prompts are derived tools used to help UG build, expand, or implement from the canon.

Prompting should never replace architecture.
Prompts should execute architecture.

Design Test

Ask:

• Is the canon already clear enough to prompt from?
• Is the prompt derived from a governing file?
• Will the output strengthen the Master Ledger rather than bypass it?

If a prompt is doing foundational thinking that the canon has not yet locked, stop and architect first.

---

15. Pillar Summary

Worthbound stands on these pillars:

1. Financial life paths, not flat classes
2. Asymmetric but fair
3. Protection is gameplay, not decoration
4. Ownership beats optics
5. Teach through consequence, not lecture
6. Approachable, not bureaucratic
7. Mobile-first readability
8. Every system must support the core loop
9. Pressure must be real, but never pointless
10. Premium clarity over raw simulation
11. One board, one strong loop
12. The main product comes first
13. Documents are primary, prompts are secondary

---

16. Enforcement Rule

Whenever a feature is proposed, test it against these pillars before accepting it into canon.

If a feature is clever but violates the pillars, reject it.
If a feature is realistic but kills readability, simplify it.
If a feature is educational but not emotionally legible, redesign it.
If a feature adds complexity without deepening identity, cut it.

These pillars are design filters, not decorative statements.