Routes

Ideas, desires, constraints, obstacles, and forks right up until the end of the road.

Four stations on one path: fork, obstacle, sign, bridge.

The decision is yours. Do you want to be happy or sad? You can choose how you want to be, the mind and spirit you want to embody.

Every journey has three kinds of moments.

Forks split the path. Obstacles block it. Signs tell you whether you are on course. Sometimes there is a fourth: the bridge you leave for the next traveller.

Fork

When two paths diverge, what determines which one you take?

Not instinct. Not convenience.

The decision process decides. A fork is where principles earn their keep. Without them, mood decides. With them, design decides.

The critical path is the shortest route to value. At every fork, the question is: which path keeps me on it?

• Priorities — what you stop doing matters more than what you start
• Decision Journal — trace reasoning and outcome
• First Principles — strip to what must be true

Obstacle

The real constraint is rarely what it appears to be.

The SIO framework names it: Situation (what is), Intention (what should be true), Obstacle (what blocks). Most people stop at the surface obstacle. The work is finding the obstacle behind the obstacle.

• Problem Solving — structured approaches to what blocks you
• Control System — engineer the response, don't rely on willpower
• Antifragile — obstacles that make the system stronger

Sign

The feedback you're getting IS the map.

A sign is data. The scoreboard reads the signs. The routing algorithm decides what to do with them.

When you feel lost, do not push harder. Read the instruments.

• Reality — what the numbers say
• The North Star — the signal you navigate toward
• Flow State — the sign that says you're in the zone

Bridge

What you leave for the next traveller.

The Legacy Rule: when you finish a job, improve the template for the next agent.

A bridge is a standard that saves the next person a detour. It can be a protocol that automates a manual step. It can be a decision trace that explains why and what.

• Standards — proven patterns that compound
• Protocols — shared practice that fires automatically
• Naming Standards — the bridge between intent and implementation

The Spine

Any structured process is a route through the maze. A product spec, a business plan, a commissioning protocol — each one is a sequence of forks, obstacles, signs, and bridges. The same four elements appear at every scale: a telco carrier selection algorithm, a manufacturing routing sheet, a physical AI commerce flow, a work delegation matrix.

Route Element	In a Structured Process	What It Tests
Fork	Phase boundaries where classification determines the path	Do you know what kind of problem this is?
Obstacle	Diagnostic gates — what failed, why, and what to do about it	Can you name the obstacle behind the obstacle?
Sign	Quality gates — pass/fail with evidence	Are you still on the critical path?
Bridge	The improved template left for the next traveller	Did the journey compound into a better starting point?

The North Star is what makes the signs readable. Without a fixed reference, every quality gate is a local check — it tells you the step passed, not whether you're heading somewhere worth going. The balanced ledger strips the noise: five things you can impact, everything else is a glory metric.

The Navigation Loop

How to run it in practice:

QUESTIONS → PROBLEM SOLVING → DECISIONS → ACTION → FEEDBACK

Questions — What am I trying to understand? · Questions

Problem Solving — What is the most important problem now? · Problem Solving

Decisions — Given constraints, what will I do next? · Decisions

Alignment — Are we committed to the same thing? · Meetings

Feedback — What happened vs what we expected? · Scoreboard

The Maze

Every route leads somewhere. The collection of all routes is the decision maze — life as a game worth playing, from cradle to grave. Each fork, obstacle, sign, and bridge is a game mechanic. The quality of the maze design determines whether the journey extracts or compounds.

• The Game — Where all routes converge into the decision maze
• Incentive Engineering — The discipline of designing routes that reward the right moves

Dig Deeper

• Mantra — Routing prompts for each kind of moment
• Critical Path — The shortest route from here to value
• Routing Algorithm — How demand gets matched to capacity
• Navigation — Value, belief, and control systems
• The What-Next Algorithm — The meta article connecting routing, the VVFL, and decision traces across every domain
• Essential Algorithm — The canonical INTENT → ROUTE → SETTLE → FEEDBACK pattern these four moments map to
• Telco MEV — Fork = which carrier; sign = QoS threshold; bridge = decision trace that compounds routing intelligence
• Manufacturing Routing — Fork = which work center; obstacle = capacity bottleneck; bridge = improved routing code
• Intercognitive Protocol — Fork = which robot; obstacle = no shared identity without the standard; bridge = open protocol any future robot inherits
• Work Charts — Fork = human or AI; sign = commissioning level; bridge = improved template left for the next agent

Context

• Deterministic vs Probabilistic — Fork is probabilistic choice, bridge is deterministic legacy
• The Game — The decision maze that all routes feed
• Navigation — The instruments for the journey
• The North Star — The fixed reference that makes signs readable
• The Ledger — The balanced scorecard of what you can impact
• Prompts — The schema that holds under pressure
• Mantra — The prompt that fires at each moment
• Decision Making — How forks get resolved

Questions

When you reach a fork, are you deciding by principle or by convenience?

• Which obstacle in your path is a symptom of a deeper obstacle?
• What sign are you currently ignoring because the message is uncomfortable?
• What bridge have you crossed that someone else built — and what bridge are you building?