The Routing Algorithm
What if flow state, telco pricing, and agent architecture are the same optimization?
Every routing problem has three states: overflow, throughput, and idle. The optimization is always the same — maximize time in throughput, minimize the other two. This pattern repeats at every scale from a single person to a global marketplace.
The Pattern
| Scale | Signal | Pipe | Capacity | Throughput | Overflow | Idle |
|---|---|---|---|---|---|---|
| Person | Attention | Mindset | Capability | Flow state | Anxiety | Boredom |
| Mantra | Intention | Trigger context | Working memory | Right response | Wrong mantra fires | No mantra fires |
| Agent | Tokens | Skill procedure | Context window | Signal-to-noise | Token waste | Unused capability |
| Team | Work | Role/position | Team capacity | Throughput | Burnout | Bench |
| Telco | Calls/data | Network route | Bandwidth | Calls/second | Dropped calls | Idle infra |
| Market | Demand | Price | Supply | Cleared transactions | Unmet demand (peak) | Unsold inventory (off-peak) |
| Org | Jobs | Work chart | Agent+skill pool | Value delivered | Overloaded teams | Mismatched talent |
Read any row. The structure is identical. A person in anxiety is a network dropping packets is a market with unmet demand. A person in boredom is idle infrastructure is unsold inventory. The flow channel, the full pipe, the cleared market — same state, different substrate.
Three Layers
At every scale, routing has three layers. They map directly to human and AI architecture.
| Layer | Person | AI Agent | Team |
|---|---|---|---|
| Mode | Mindset (archetype) | System prompt | Position/role |
| Router | Mantra | Skill procedure | Process/protocol |
| Executor | Capability | Tools | Platform |
The mode layer selects WHAT mode to operate in. The router layer determines HOW to handle the signal. The executor layer provides WITH WHAT to act.
Decision fatigue is what happens when too many signals hit the routing layer simultaneously. The fix is pre-routing: habits, protocols, system prompts that handle known patterns automatically. This frees the routing layer for novel signals — the ones that actually need judgment.
Archetypes are mode switches. A Dreamer routes differently than an Engineer. The wisdom is knowing which mode the situation demands — which is exactly what Situational Wisdom encodes.
The Compound
When routing works, capacity grows. You handle more signal. Capacity grows again.
capability → handle harder challenges → stay in flow → capability grows
capacity → route more traffic → earn margin → fund more capacity
value → earn trust → win harder work → build deeper capability
This IS the VVFL's inner loop with rate added. The Tight Five inner loop sets direction. The flow channel sets rate. Together they determine whether the loop compounds or breaks.
The natural progression is always the same: match demand to capacity at the edge of capability, stay there, grow. Whether you're a person seeking flow, a network engineer tuning routes, or a marketplace clearing prices — the algorithm is one algorithm.
Two Pipes
Every routing system has two pipes. One is fast, cheap, and massive. The other is slow, expensive, and scarce.
| Dimension | Fast Pipe (System 1) | Slow Pipe (System 2) |
|---|---|---|
| Capacity | Massive | Limited |
| Energy cost | Near zero | Massive |
| Person | Habit, mantra, trained response | Deliberate reasoning |
| Agent | Cached skill, system prompt | Novel problem-solving |
| Org | Standard operating procedure | Strategic decision |
| Telco | Pre-routed traffic | Exception handling |
Every mantra built is a new Fast Pipe. Every protocol documented is bandwidth freed. Every skill automated is Slow Pipe capacity returned to the frontier.
The archetype layer is the controller asking one question: does a Fast Pipe exist for this signal? If yes, route there. If no, engage the Slow Pipe — but start building the Fast Pipe for next time.
The compound: each new Fast Pipe frees Slow Pipe capacity for harder problems. Harder problems solved become new Fast Pipes. The routing system upgrades itself.
Two Coordinates
Strip everything else away. A person has two coordinates.
| Coordinate | Nature | What It Controls | Measure |
|---|---|---|---|
| Time | Fixed constraint | Pipe diameter | Bandwidth — hours available |
| State of Mind | Variable signal | Signal quality | SNR — intention vs noise |
Time is the constraint you cannot negotiate. State of mind is the variable you can.
A person in the wrong archetype for the task = high bandwidth, low signal. A person in flow = high bandwidth, high signal. Same time. Different throughput.
"Time and state of mind is all that we are" is not philosophy. It is the spec. Everything else — capability, energy, attention, output — derives from these two.
Two Instruments
Two coordinates need two instruments.
| Instrument | Coordinate | What It Does | VVFL Position |
|---|---|---|---|
| Prompt Deck | Time | Builds Fast Pipes through compression | Build |
| Time + Mind | State of Mind | Measures routing quality via alignment scoring | Measure |
Together they close the loop:
Build pipes → Measure flow → Find leaks → Build better pipes
This is the VVFL applied to personal bandwidth. Setpoint = Tight Five. Gauge = alignment score. Controller = Sunday archetype review.
Compression is pre-routing. When the Prompt Deck compresses a domain into five headlines, it builds a Fast Pipe for every decision in that domain. The Time+Mind instrument measures whether signals actually flow through those pipes — or leak into the Slow Pipe through drift.
Decision Traces
A routing algorithm produces a chain of decisions. The most valuable output isn't the route — it's the trace showing WHY the route was chosen.
A problem solved is a problem forgotten. Organizations that don't persist decision traces repeat mistakes when personnel change. The fix isn't better memory — it's better recording.
| Layer | Instrument | What It Persists |
|---|---|---|
| Personal | Decision journal | Prior → action → outcome → updated prior |
| Organizational | Context graph | Entities, decision events, reasoning links |
| Infrastructure | Telco MEV algorithm | Route selection, exception handling, precedent |
The telco MEV algorithm proved this. When a carrier got blocklisted, the trace recorded the QoS failure, the threshold breached, the alternative selected. That trace became queryable precedent. Decision traces were worth more than the routes themselves.
Context graphs make "why" a first-class data type. Link decisions to each other and you get a graph that scales judgment without scaling headcount. The decision journal is the personal version. The context graph is the organizational one. Same pattern, different substrate — like everything on this page.
Context
- Flow State — The throughput state for a person
- Situational Wisdom — The diagram that encodes mode selection
- Archetypes — Mode switches for the routing layer
- Mantra — Pre-routed responses for known patterns
- Tight Five — The inner loop that sets direction
- VVFL Loop — The operating system this routing pattern serves
- Time and Energy — The scarce resource being routed
- Work Charts — Routing at the org scale
- Prompt Deck — Builds Fast Pipes through compression
- Time + Mind — Measures routing quality through alignment scoring
- Telco MEV — The proof: routing intelligence as compound asset
- Decision Journal — The personal context graph
Questions
What's the one routing decision that would unlock the most capacity right now?
- Where are you in overflow — too many signals, not enough pipe — and what known patterns could you pre-route?
- Where are you idle — capability going unused — and what demand could you route to it?
- When you switch archetypes mid-task, what signal triggered the mode change — and was it the right one?
- What percentage of your weekly decisions still run through the Slow Pipe — and which one would you automate first?
- What decision trace from last month would have saved you time this week if you could query it?