Start Here: What Survives When The Surface Changes?
A short front door to the publication: the lens, the instruments you can run now, and the reader paths.
Start here if AI makes you feel behind.
This publication runs on one question:
What survives when the surface changes?
Most AI commentary moves at the speed of the surface. Releases, benchmark jumps, tool launches, prompt tricks, funding rounds, arguments about who is suddenly ahead. Some of it matters. Track only that, and every release feels like a reset, every demo feels like a threat, and you redraw your map of the world every few weeks.
That churn is the surface. What follows is the lens I use to work out which parts of it will still matter, and the instruments that make it something you can run rather than something you agree with.
The Lens
Every system has a canopy and a substrate.
The canopy is the visible part. The demo, the interface, the prompt, the benchmark score, the dashboard, the model everyone is discussing this week.
The substrate is what still has a job when the canopy gets repriced. The data pipeline, the evaluation contract, the workflow it plugs into, the distribution channel, the trust, the failure memory, the recovery path, the decision rule.
Visibility and durability are separate properties. Treating them as one property is the expensive mistake, and it is the one I watch people make most often.
That is half the lens. The second half is the one that costs money when it gets left out.
Durable is not sufficient, because scarcity moves. When a layer commoditises, value migrates to whichever adjacent layer now resists commoditisation hardest. Usually that is the coordinating, verifying and selecting layer above it. When the binding scarcity is physical or institutional, compute, power, fabrication, regulatory access, it moves down instead. The bottleneck never disappears. It goes where resistance is highest, and assuming that is always upward, or always deeper, is how people end up owning something perfectly durable that nothing needs any more. A durable architecture the bottleneck has already moved away from is a melting ice cube.
So that one question has two halves. What kind of thing survives a repricing, and where is the scarcity heading right now. What you want to own is the durable thing at the moment the bottleneck is moving toward it.
The Test
Start by writing down which parts of your system you are calling substrate. Do this first, before you know what is coming, and be specific enough that somebody could later tell you that you were wrong.
The order is the whole test. Name the disturbance first and you will find yourself labelling whatever survived as substrate and whatever broke as canopy. Nothing stops you, the score comes out flattering, and it can never tell you that you got it wrong. A test you cannot fail is not measuring anything.
With your list committed, name the disturbance, precisely enough that somebody could disagree with you. An open-source model matches your benchmark and runs on commodity hardware. Your main channel stops favouring your format. The layer your product sits on ships your feature as a primitive.
Then count how much of what you built still has a job. That surviving fraction is the honest measure of durability, and it is the inverse of what I call your displacement rate. Something can look weak today and be very hard to displace. Something can look dominant and be a canopy bet waiting for the next shift to expose it.
Run one on your own work
The fastest way into any of this is to point it at something you own. Seven instruments are free and live right now, all of them on the instrument rack. Each runs in your browser and needs no account, and nothing you type leaves the page.
If you only open one, open the first.
The Potemkin Map. Score your AI loops on two questions. Could the success signal be faked, and is the first real failure terminal. It plots what you enter on those two axes and tells you which corner you cannot iterate your way out of.
The Marathon Calculator. Per-step reliability compounds over a long agent run. See the finish-rate gap, and the expected token cost of one finished task once the failed runs are priced in.
The Two-Rate Diagnostic. Name the AI layer your advantage runs through, then set your absorption rate against our dated read of that layer’s clock, and see how long the window stays open.
The Structure Spotter. Name the mathematical shape under a load-bearing assumption, such as a trade-off that is really a filter, or an independence that only holds on calm days. Name the shape and you inherit the test the field that met it first already built. It offers a candidate diagnosis, not a verdict.
The Multi-Agent Decision. Four questions per task, and a ranking of which jobs on your list actually earn a fleet. Most come back as one strong agent with an engineering envelope around it.
The Metric Validity Audit. Pick the number you trust most. Get a read on how that kind of number lies, and what to do about it.
The Shape Test. Is your growth curve compounding or just accumulating? Drag through your own series and watch the verdict arrive, later than you expect.
Ten minutes with any one of them gives you something about your own system that you did not have this morning.
Start with the problem you have
You do not have to read everything. Start from the problem you actually have.
I want the shortest version of the whole idea.
Read The Forest Floor Is The Product, then Your Tools Got Powerful. Get Boring.
The first is the cleanest statement of substrate against canopy. The second is what it looks like when you act on it.
I build with AI agents and I need them to be reliable.
Start with How Reliable Is Your AI Agent?, which is the piece the rest of this publication keeps returning to. Then Never Let Claude Code Tell You It’s Done for a walkthrough you can follow with your own hands, and The Seven-Layer Agent Audit, which hands you the seven questions and a scorecard to run them with.
That last one contains the clearest example of this lens costing me something. I wrote a script to run the seven questions automatically, then threw it away, because a script reads your file names rather than your setup and returns a confident verdict on any stack it does not recognise. The automation was canopy. The questions were substrate. I had built the wrong one first.
I am deciding what to build on, or what to standardise across a team.
Read Skills Are Package Management for Your AI.
Treat your skills, prompts and tools as dependencies with versions, owners and revocation, or accept that nobody can tell you what your agent is currently allowed to do.
I need to know whether my evaluation is telling me the truth.
Read Most Verification Is Just Bigger Classification, then Your Research Agent Cites Sources It Never Read.
If you want the sharpest version, Your AI Looks Best Where You Can Check It Least and its companion Potemkin Map deal with the loops where the evidence is written by the thing being evaluated.
I am thinking about my own job.
Read The Safe Parts of Your Job Are the First to Go, then The Difficulty You’re Escaping Was Making You.
I want the framework underneath all of it.
Read The Five Laws of Durable Systems.
Canopy and substrate is the entry point. The five laws are what the analysis actually runs on, including the one that says some of the hard parts of your system are waste and some are the mechanism producing the value, and that telling those apart is most of the job. A corollary that falls out of three of the five says any metric you optimise against degrades as a measure of the thing you cared about.
I also write about markets and capital allocation through the same lens. That is a genuine but secondary lane here. The main work is AI systems, agents, and the reliability of both.
What to expect
One structural lens at a time, written so you can use it. Sometimes that is an essay. Sometimes a walkthrough you follow with your own hands. Sometimes an instrument like the six above.
The aim is that the next time something looks impressive, you have a sharper set of questions ready.
What is the substrate here?
What happens to it when the ground moves?
Is the scarcity moving toward this, or away from it?
If You Only Remember One Thing
Ask what still has a job after the surface changes.
Then ask whether the scarcity is moving toward it, or away.