The Three Flows
Everything you do follows five stages. Send a text. Pay for coffee. Check the weather. The pattern is the same.
INTENT → ROUTE → INFRASTRUCTURE → SETTLE → FEEDBACK
You want something. A system finds the path. Pipes carry it. Something confirms it's done. You learn whether it worked.
Three things move through this pattern. Everything else is a subset.
| Flow | What Moves | You Know It As | It Settles When |
|---|---|---|---|
| Messages | Information | Calls, texts, packets | Delivered and billed |
| Value | Money | Payments, transfers | Funds clear |
| Data | Measurement | Sensors, feeds, scores | Recorded and trusted |
The Five Stages
| Stage | Function | Question |
|---|---|---|
| Intent | What wants to move | What outcome do you seek? |
| Route | Path selection | What's the best way to get there? |
| Infrastructure | The pipes | What carries it? |
| Settle | Finality | When is it done? |
| Feedback | Loop closure | Did it work? What changed? |
The flow that skips feedback is the flow that drifts. A payment without confirmation. A sensor without calibration. A message into the void.
Messages
When you make a phone call, a telecom switch selects the cheapest path with acceptable quality. Fiber, wireless, or satellite carries the signal. A Call Detail Record logs duration, route, and cost. Quality metrics feed back — dropped calls trigger rerouting.
Every messaging platform follows this. Email, Slack, push notifications. The technology changes. The five stages don't.
Where it breaks: When routing optimises for cost over quality. When settlement is delayed (you hear the echo, the lag). When feedback is absent — the message sends but you never know if it arrived.
Value
When you tap your card, an acquirer routes the transaction through a card network to your bank. Rails carry the authorisation. Settlement confirms the money moved. Fees, exchange rates, and fraud signals feed back into the next transaction.
Cross-border payments expose the friction. A wire transfer through correspondent banks takes days because each hop is a separate intent-route-settle cycle with no shared feedback loop.
Where it breaks: When routing adds intermediaries who extract without adding signal. When settlement takes days instead of seconds. When feedback (your balance) lags behind reality.
Data
When a weather station measures temperature, edge processors filter noise and aggregate readings. Networks carry the signal to a database. The reading is timestamped and stored. Accuracy metrics determine whether to trust the sensor tomorrow.
Supply chains, IoT networks, and financial feeds all follow this. The data wants to move from where it's measured to where it's needed.
Where it breaks: When the sensor drifts but nobody recalibrates. When the route drops readings silently. When settlement means "stored" but not "verified."
Convergence
These three flows used to run on separate infrastructure. Telecom networks for messages. Banking rails for value. Proprietary systems for data.
They're merging.
MESSAGES ──┐
│
VALUE ─────┼──→ SHARED SETTLEMENT LAYER
│
DATA ──────┘
A solar panel measures output (data), reports to the grid (message), and gets paid per kilowatt-hour (value). Three flows, one device, one settlement event.
DePIN — decentralised physical infrastructure — is where this convergence becomes concrete. Devices prove work (data), get paid (value), and receive instructions (messages). Your base station becomes an economic actor. Your meter invoices in real-time.
What Changes
Speed compounds. When messages, value, and data share infrastructure, settlement collapses from days to seconds. A machine doesn't wait for a bank to open.
Feedback tightens. Separate systems mean separate feedback loops with different cadences. Unified settlement means one loop. Drift gets caught faster.
Platform is product. Jobs and Musk understood this — the platform isn't what you build on, it IS the product. Open infrastructure takes it further: permissionless, best instrument wins. Darwin at the pipes layer.
Truth emerges. Truth isn't declared. It's the feedback from action through shared infrastructure that anyone can verify. The same five stages apply:
| Stage | In Truth |
|---|---|
| Intent | A claim is made |
| Route | A protocol tests it |
| Infrastructure | Shared standards carry it |
| Settle | Evidence is recorded |
| Feedback | Convergence on what's real |
Context
- Tight Five — Five stages is a tight five: intent, route, infrastructure, settle, feedback
- Agency — Agency requires all three flows: messages to coordinate, value to transact, data to measure
- Data Flow — Right data, right moment
- Truth — Infrastructure for verification
- Feedback Loops — Flow is loop optimisation
- Payments Industry — Cross-border friction meets programmable rails
- DePIN — Physical infrastructure on cryptographic proof
- Agent Commerce — Settlement standards for autonomous actors
- Sui — Coordination at machine tempo
- Stablecoins — The settlement instrument
- Phygital Beings — Devices and agents as economic actors
- The Convergence — The full article
Questions
What breaks when a flow completes four stages but skips feedback?
- Which of the three flows do you interact with most — and where does it fail you?
- What happens to intermediaries when messages, value, and data share the same settlement layer?
- Where in your work do you see two of these flows converging already?
- A prompt deck follows the same five stages — headline (intent), question (route), depth link (infrastructure), decision (settle), outcome (feedback). What other instruments follow this pattern without naming it?