A map, not a manifesto
How I think
I trace the tension to its root, then build the system that releases it. This is the system I run my own work on: a personal AI operating system I built and live inside every day. It is the same thing I build for teams, tested on the hardest client I have.
- 01
Sense
What actually happened?
Signals come in first: the calendar, the inbox, the project boards, what shipped and what stalled. Before I decide anything I want the day as it was, not as I planned it.
- 02
Route
Who should do this, if anyone?
Every task gets one of four answers: just answer it, hand it to one accountable worker, fan it out to a small team, or don't bother. The last one is the answer a builder forgets most.
- 03
Test the plan
Does the plan hold?
Anything bigger than a couple of hours gets its assumptions written down and checked against research before a line gets built. Most bad builds were bad plans first.
- 04
Build behind gates
Is it true, or does it just look true?
Three stop conditions, in order: does my check lie (truncated output, wrong host, a count I guessed)? Is my evidence live, from this session, or remembered? Did I verify before I spoke, or while I spoke?
- 05
Receipts
Can someone else confirm it?
A claim cites the file and line, or the command that proved it. "Done" means the behavior was observed, not that the code compiles.
- 06
Rhythm
What changed since last time?
Morning, midday, and evening check-ins; a weekly review; a quarterly one. Each is short, and each asks what moved, what stuck, and what to drop.
- 07
Memory
What should never have to be learned twice?
Corrections become rules, and rules get pruned. Repeated friction is treated as a leak to fix: a missing skill, missing knowledge, or a missing handoff. It is not a reason to build more machinery.
- loop
Back to Sense
The map is a loop. What memory keeps changes what I notice next, which is the whole point of a body that learns: the next symptom gets traced faster than the last.
Try it
The tension mapper
Describe what's eating your team's hours. Get the likely root, not the symptom.
See it running
The AI agents
Four production agents built on this map. They answer this site's front door.