Skip to main content
Back to all page templates

Page template

Belief story template

A public belief page that names a claim, countercase, evidence boundary and next move.

Pattern ID

belief-story

Implementation

Page-private template

Live examples

6

Where this page type is used and why

Use when a belief should be inspectable and revisable instead of being presented as doctrine.

/priorities/beliefs/money

Test whether one allocation builds capability and meaningful value.

Test whether one allocation turns a transferable claim into capability and meaningful value.

Proof signal: The allocation names beneficiary, downside, retained capability, evidence, and review.

Open live page · Implementation source

/priorities/beliefs/tokenomics

Test claims about AI abundance, money, scarcity, and allocation.

Unbundle the functions of money and name signals that could falsify an abundance claim.

Proof signal: The reader can distinguish changing payment rails from changing scarcity.

Open live page · Implementation source

/priorities/beliefs/optimism

Keep possibility alive through bounded action and honest evidence.

Treat optimism as a testable orientation rather than evidence that outcomes improved.

Proof signal: The belief exposes a consequence that could revise it.

Open live page · Implementation source

/priorities/beliefs/play

Use voluntary challenge and safe failure to learn one transferable lesson.

Reconsider play as a bounded practice for learning, flow, and transferable capability.

Proof signal: One game's rules and one safer, meaningful turn can be named.

Open live page · Implementation source

/priorities/beliefs/stewardship

Keep the beneficiary, consequential authority, constraints, evidence, and stop decision human-owned when AI multiplies capacity.

Name the beneficiary, retain consequential authority, constrain the system, test the outcome, and stop when harm appears.

Proof signal: A blank field in the AI Stewardship Test pauses granting more authority or access.

Open live page · Implementation source

/priorities/beliefs/intentions

Explain how intention becomes attention, action, feedback, and a sharper next intention.

Understand the Dreamineering loop before applying it to a venture route.

Proof signal: A reader can distinguish story, chart, tool, capability state, and venture route.

Open live page · Implementation source

Components used to assemble the UI pattern

  • BeliefArticleReturnNav
  • local belief article component
  • Section
  • Container

Public page contract registry · Primary implementation example

Presentation considerations

  • State the belief as a testable orientation, not proof that outcomes improved.
  • Keep the countercase close to the claim.
  • Route to the next useful instrument, not to a generic archive.

Alternative design choices