Mantra
You prompt the machine. The mantra prompts you.
Same mechanism, both directions. You give an AI context and intention so it acts aligned. A mantra gives you context and intention so you act aligned. A pepeha — declaring your mountain, your river, your people — is the deepest prompt. You declare what grounds you before you act.
Under cognitive load, pressure, fatigue — the trigger fails. That's why you need both: the mantra (intention) and the system (enforcement).
A mantra is a Zeigarnik device. It opens a loop — "Act on principles, not emotion" — that stays active in working memory until you either follow it or consciously override it. Mantras counter biases by keeping System 2 alive when System 1 wants to take over.
The Route
Every journey has three kinds of moments: forks, obstacles, and signs. When you reach one, you need a prompt ready.
A mantra is a routing instruction. Same structure as a headline, a skill description, or a telco routing rule: a title (the phrase), a trigger context (when to use it), and a destination (what system it activates). The table below is the routing table. No overlap between mantras, maximum signal per mantra, route the right response to the right situation.
Routing Table
| When | Mantra | System It Activates |
|---|---|---|
| At a fork | Act on principles, not emotion | Decision filter |
| Reading a sign | What's the most important question? | Existence questions |
| Off course | Measure what matters | Performance scoreboard |
| Facing an obstacle | Ship, then iterate | VVFL loop |
| Scattered | One task, full attention | Flow state |
| Ego rising | Make others the star | Character |
| On the critical path | Comfort kills creativity | Potential |
| Money warping | Money is a poor measure of wealth | Financialization |
| Alone | The journey is plural | Players |
| Anxious | Confidence is having systems to find a way | Control system |
| Leaving a legacy | Improve the template for the next traveller | Standards that compound |
| Building a bridge | Make forgetting impossible | Protocols that fire automatically |
The best mantra is the one you don't need because the system already handles it. That's why :::tip Mantra blocks appear on pages throughout the site — mantras in context, where they're needed, not in a list you'll never revisit under load.
The Cascade
| Level | Mechanism | Fails When |
|---|---|---|
| Mantra | You remember the phrase | Cognitive load, fatigue, emotion |
| Rule | Context loaded, you apply it | Pressure, context overflow |
| Hook | Fires automatically on event | System misconfigured |
| System | Environment prevents the error | Never (if designed right) |
Mantras set the intention — the setpoint. Systems enforce it — the controller. A PID loop needs both. Without the setpoint, the system has nothing to control toward. Without the system, the setpoint is just a wish. The goal is flow — where neither is conscious.
The Upgrade Path
| From | To |
|---|---|
| Remembering a phrase | Phrase embedded in environment |
| Willpower under pressure | Protocol that fires automatically |
| Personal discipline | Shared standard that compounds |
| "I should remember to..." | Platform that makes forgetting impossible |
Watch your thoughts, they become words. Watch your words, they become actions. Watch your actions, they become habits. Watch your habits, they become character. Watch your character, for it becomes your destiny.
This is the propagation chain. You get what you propagate. The mantra is where the chain starts — the inner of inner loops. Positive pictures, positive prompts, positive propagation. Vicious and virtuous cycles run on the same engine. The mantra chooses which one.
Five Headlines
Five questions. Each one a prompt that resets your orientation. Simple enough to remember under pressure. Deep enough to restructure a business. The Tight Five is a pepeha for any domain.
| # | Headline Prompt | Hidden Depth | When You Need It |
|---|---|---|---|
| 1 | Why does this matter? | Purpose | Lost in activity without direction |
| 2 | What truths guide you? | Principles | Decision feels arbitrary |
| 3 | What do you control? | Platform | Overwhelmed by what you can't change |
| 4 | What do you see others don't? | Perspective | Competing without differentiation |
| 5 | How do you know it's working? | Performance | Busy but not progressing |
When you know your mountain, your river, your waka, your people, and your fruit — you don't need someone else to tell you what matters.
Context
- Prompts — The schema, instances, and agent prompt
- Routes — Forks, obstacles, signs, bridges
- First Principles — Under pressure, reason from what's true
- Flow State — Where mantras become unnecessary
- Control System — Engineering what mantras try to do
- Routing Algorithm — Every mantra is a Fast Pipe: a pre-routed response for a known pattern
- Critical Path — The shortest route to value
- Behavioural Biases — What mantras counter
- Protocols — When mantras graduate to shared practice
- Pepeha — The deepest prompt: identity grounded in belonging
- Gratitude — The signal that confirms your prompt landed
Questions
If the mantra prompts you the same way you prompt the machine, what's your system prompt?
- When you reach a fork, which mantra fires first — and is it the right one for this kind of fork?
- When a mantra fails under pressure, is the problem the mantra or the absence of the system behind it?
- What distinguishes a mantra you've internalized from one you merely remember?
- If your pepeha declares what grounds you, what happens to people who've never been asked to declare it?