Skip to content

Worthbound Core Design Law

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

  • 00-Core/00-Worthbound-Design-Constitution.md
  • 00-Core/01-Game-Identity.md
  • 00-Core/02-Design-Pillars.md

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.

These laws are intended to be quoted, referenced, and applied repeatedly throughout the Master Ledger.


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.

Any archetype that differs only by salary number is incomplete.


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.

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


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.

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


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
  • continuity-preserving structures

Worthbound must reward the movement from:

  • earned income to
  • durable ownership

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


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 crises
  • career instability

The purpose of pressure is to expose truth:

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

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


Protection is not merely defensive.

Insurance and related protection systems must:

  • reduce catastrophic downside
  • preserve momentum
  • protect dependents
  • reduce forced liquidation
  • 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:3]{index="3"}

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


Worthbound is not only about what the player gains.
It is about what survives disruption.

Continuity means the player can build structures that resist collapse under severe events.

Continuity may preserve:

  • part of a portfolio
  • household stability
  • dependent progress
  • owned assets
  • strategic position
  • future opportunity

Severe setbacks must not always reset the player equally. Preparation must matter.


Beneficiaries must have mechanical relevance.

They are not narrative labels attached after the fact.
They are part of the player’s continuity architecture.

Beneficiary systems may:

  • receive protection payouts
  • preserve family or estate function
  • reduce collapse penalties
  • hold open future tracks
  • support legacy progression

This law prevents beneficiaries from becoming cosmetic flavor. :contentReference[oaicite:4]{index="4"}

If beneficiaries do not alter outcomes, the system is incomplete.


Worthbound teaches through consequences, not lectures.

The player should learn by experiencing:

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

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.”
  • “My family did not collapse because I protected them.”

Whenever possible, replace explanation with system feedback.


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:6]{index="6"}

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


Every archetype must have a different path to strength.

Examples:

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

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:7]{index="7"}

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


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

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


Worthbound is a financial life RPG first.

Other modes may support the ecosystem, 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

Whenever resource tension appears, the main RPG loop wins.


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:

  1. architecture
  2. canonical file
  3. architectured prompt
  4. implementation

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


The primary progression threshold of Worthbound is structural freedom.

That threshold is reached when:

Passive Income >= Total Expenses

This is not merely a score condition.
It is a life-state transition.

Crossing this threshold should feel like:

  • release
  • mastery
  • structural change
  • entry into a higher progression layer

This law must shape economy, pacing, reward, and presentation. :contentReference[oaicite:8]{index="8"}


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 continuity
  • 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 continuity systems

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
  • continuity matters
  • beneficiaries must matter
  • teaching happens through consequence
  • complexity must remain legible
  • each archetype needs a distinct win story
  • the game must not feel like a spreadsheet
  • the main RPG product comes first
  • canon comes before prompting
  • financial escape is a structural transition

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