Systems
Feedback loops can be vicious or virtuous. The same architecture amplifies both.
From systems thinking to thinking systems, it all comes down to charting the coordination of agents and instruments.
Systems exist to improve the flow of coordination. The test: does this make humans more capable together, or more dependent alone?
Navigation System
Every system — person, organization, economy — runs three interlocking loops:
| System | Question | Force | When Aligned | When Broken |
|---|---|---|---|---|
| Value | What grounds you? | Anchor | Clarity of purpose | Chasing wrong metrics |
| Belief | Where are you going? | Pull | Dreams attract capability | Delusion, can't execute |
| Control | How do you navigate? | Levers | Steer the ship | Rudderless inefficiency |
When all three harmonize, you experience flow. When one is off, you feel dis-ease — the signal to diagnose which loop needs attention.
Thinking Methods
How to process reality and make better decisions:
| Method | What It Does | When to Use |
|---|---|---|
| Systems Thinking | See feedback loops, find leverage | Side effects surprise you |
| First Principles | Strip to fundamentals, rebuild | Stuck in convention |
| Inversion | Ask "what would make this fail?" | Optimising the wrong thing |
| Matrix Thinking | Make gaps visible, cross-link | Need to audit completeness |
| Decision Frameworks | OODA, heuristics, algorithms | Complex choices under pressure |
Process Systems
How to document, measure, and improve how work gets done.
Four levels, from strategic to tactical:
| Level | Term | What it is |
|---|---|---|
| 1 | Standards | The ontology — why things relate |
| 2 | Process | The goal — what needs to happen (tacit) |
| 3 | Procedure | The rules — formalized logic (explicit) |
| 4 | Workflow | The execution — how it actually happened |
Full definitions: Naming Standards → Operations Hierarchy
The improvement loop applies at every level: document → measure → analyze → improve → standardize. Design the system so the right thing is the path of least resistance — that is the Pit of Success.
| Resource | What It Covers |
|---|---|
| Process Optimisation | Questioning → Problem Solving → Decisions → Improvement Method |
| Standards | How concepts structure into navigation and naming |
| Work Charts | Who does what — capability → demand mapping |
Learning Systems
How to acquire and compound knowledge:
| Resource | What It Covers |
|---|---|
| Meta Learning | Learn how to learn — awareness → capture → practice → teach |
| Knowledge Stack | Science → Principles → Protocols → Standards → Platform |
Technology Systems
How to build and leverage platform capability:
| Domain | Key Resources |
|---|---|
| AI | LLMs, Agents, Frameworks |
| DePIN | Architecture, Tokens, Industry Impact |
| Software | Tech Stack, Platform Engineering |
Context
- Standards — What systems standardize and scale
- Scoreboard — Where system outputs get measured
- Principles — Foundational truths (Value System)
- Platform — Tools and infrastructure (Control System)
- Navigation System — Value, belief, and control as the three loops
Questions
Which systems loop — value, belief, or control — breaks first when an organization scales?
- What is the minimum feedback loop complexity required to produce emergent behavior?
- If your thinking methods are tools, which tool are you reaching for by habit rather than by need?
- How do you distinguish a broken system from a system designed to produce exactly what it's producing?