Worthbound Core Design Law

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/02-Design-Pillars.md
09-Production/00-Mobile-First-MVP-Rescope.md

1. Purpose

This file defines the compact governing laws that all Worthbound systems, archetypes, balance decisions, content structures, and implementation choices must obey.

The Constitution defines the broad foundation.
This file defines the reusable operational laws.

For the current project phase, these laws are applied to the mobile-first MVP.

2. Law of Financial Life Paths

In Worthbound, the player is not choosing the highest-paying option.

The player is choosing a financial life path.

A financial life path is defined by:

earning pattern
obligation pattern
risk exposure
opportunity access
protection sensitivity
likely route to freedom

This law means archetypes must be designed as distinct life-navigation stories rather than shallow role labels.

Operational Consequence

Any archetype that differs only by salary number is incomplete.

3. Law of Asymmetric Viability

Worthbound does not balance through sameness.

Different archetypes may have:

different income levels
different expense burdens
different household pressures
different fragility points
different opportunity lanes
different upside ceilings

These differences are allowed and required.

Balance means that each path remains viable through a different form of mastery.

Operational Consequence

No path may secretly become “the smart player’s obvious choice” without counterweight.

4. Law of Salary Insufficiency

Salary alone must never represent true victory.

A large paycheck may improve options, but it may also introduce:

larger obligations
stronger lifestyle inflation
tax complexity
pressure to maintain appearances
more expensive mistakes

Worthbound must repeatedly reveal that income without ownership is unstable.

This law is especially important for high-income archetypes.

Operational Consequence

High-income lanes must include meaningful leakage, pressure, or fragility.

5. Law of Ownership Conversion

The player’s long-term strength comes from converting active income into owned systems.

These systems may include:

cash reserves
productive assets
protected assets
passive income generators

Worthbound must reward the movement from:

earned income to
durable ownership

Operational Consequence

Core progression should repeatedly ask: “What did the player build that now works for them?”

6. Law of Pressure Revelation

Pressure is not a punishment layer.
Pressure is the layer that reveals whether the player’s life system is sound.

Pressure may take the form of:

bills
dependent burdens
interruptions
emergencies
market downturns
household expense spikes
career instability

The purpose of pressure is to expose truth:

weak reserves
overdependence on salary
lack of protection
poor liquidity
unmanaged lifestyle creep

Operational Consequence

Events and obligations must test systems rather than act as random cruelty.

7. Law of Protection as Freedom

Protection is not merely defensive.

Insurance and related protection systems must:

reduce catastrophic downside
preserve momentum
reduce collapse risk
support strategic risk-taking

The player should experience protection as:

resilience
breathing room
option preservation
confidence to act

This law is a central differentiator of Worthbound. :contentReference[oaicite:10]{index="10"}

Operational Consequence

Any protection system that only feels like a passive tax is incorrectly designed.

8. Law of Consequence-Based Teaching

Worthbound teaches through consequences, not lectures.

The player should learn by experiencing:

salary pressure
obligation drag
compounding discipline
interruption risk
insurance relief
ownership momentum

The strongest lessons occur when the player says:

“That looked good, but it trapped me.”
“That small asset changed everything.”
“I survived because I planned.”

Operational Consequence

Whenever possible, replace explanation with system feedback.

9. Law of Legible Complexity

Worthbound may be strategically deep, but it must remain readable.

Complexity is acceptable only when it creates meaningful decisions.
Complexity is unacceptable when it creates clerical drag.

This applies especially to:

insurance
debt
taxes
opportunity comparison
event consequences

Worthbound should abstract aggressively wherever realism threatens playability. :contentReference[oaicite:12]{index="12"}

Operational Consequence

When forced to choose, preserve strategic clarity over technical simulation.

10. Law of Distinct Win Stories

Every archetype must have a different path to strength.

Examples:

disciplined compounding
practical side income
stable cashflow conversion
high-upside deal control
volatility management

A path is well designed when the player can describe its win story in one sentence.

Examples:

“I built steadily from practical cashflow.”
“I turned stability into assets.”
“I beat income volatility with reserves and protection.”
“I stopped lifestyle bleed and converted big income into ownership.” :contentReference[oaicite:13]{index="13"}

Operational Consequence

If multiple archetypes feel like the same game with different numbers, redesign them.

11. Law of Anti-Spreadsheet Feel

Worthbound must never feel like software first and game second.

The game should feel:

structured
tactile
human
strategic
emotionally legible
premium

It should not feel:

bureaucratic
form-like
overloaded with tiny numeric administration
visually dead

Operational Consequence

Presentation, language, and flow must transform financial logic into game logic.

12. Law of Mobile Constraint

The MVP must respect the realities of mobile play.

This means:

fewer simultaneous decisions
shorter turns
simpler information density
strong readability at a glance
limited panel complexity
tap-friendly interaction

Operational Consequence

Any design that requires a desktop-scale dashboard should be reduced or removed from MVP.

13. Law of Main-Product Priority

Worthbound is a mobile-first financial life RPG first.

Other modes may support the ecosystem later, including possible match-based side modes, but no secondary mode may distort:

the architecture
the balancing priorities
the UX model
the implementation roadmap of the main product

Operational Consequence

Whenever resource tension appears, the main RPG loop wins.

14. Law of Canon Before Prompt

The Master Ledger is the governing memory of the project.

Architectured prompts exist to execute, expand, or scaffold from canon.
They do not replace canon.

The correct order is:

architecture
canonical file
architectured prompt
implementation

Operational Consequence

If a prompt is being asked to invent foundational truth, the canon is underdeveloped.

15. Law of Escape Threshold

The primary progression threshold of Worthbound MVP is structural freedom.

That threshold is reached when:

Passive Income >= Total Expenses

This is the primary MVP victory condition.

It should feel like:

relief
mastery
structural change
earned freedom :contentReference[oaicite:14]{index="14"}

Operational Consequence

Economy, pacing, rewards, and UI should all make this threshold visible.

16. Law of One-Board Focus

The current MVP is governed by this rule:

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

This law exists to prevent:

multi-board scope creep
oversized systemic branching
universe-scale assumptions
mobile UX overload

Operational Consequence

If a mechanic does not strengthen the one-board loop, it does not belong in MVP.

17. Law of Expansion Fidelity

Future features may deepen the game, but they must not betray the foundation.

Expansion is valid when it:

reinforces life-path mastery
deepens protection and risk strategy
expands viable strategy
preserves approachability
strengthens the premium feel

Expansion is invalid when it:

introduces bureaucracy
replaces asymmetry with homogenization
confuses the core loop
rewards optics over ownership
weakens mobile readability

18. Summary

Worthbound is governed by these core truths:

players choose financial life paths, not merely salaries
balance is asymmetric viability
salary alone is insufficient
progression comes from ownership conversion
pressure reveals system truth
protection creates freedom
teaching happens through consequence
complexity must remain legible
each archetype needs a distinct win story
the game must not feel like a spreadsheet
the MVP must respect mobile constraint
the main RPG product comes first
canon comes before prompting
passive-income escape is the core threshold
the MVP is one board and one strong loop

These laws should be treated as reusable operating doctrine across the entire Master Ledger.