I read businesses at the layer underneath their strategy — and install the AI operating architecture that lets them run from what they actually are.
Dallas, Texas · Working with founders globally
One process. Three phases. The same engagement whether you are at half a million or thirty.
The audit and the install are not separable. The install only works if the audit is correct. The audit is only worth running if you intend to act on it. What scales between businesses is not the offer — it is the stakes. The price reflects what the correction is worth at the scale you operate.
Audit
Extended conversations with the founder. Interviews with the operators. Review of customer feedback where it exists. I am reading three surfaces simultaneously — listening for the divergences between what the company says it is, what its decisions reveal, and what the team actually experiences. The audit produces the first honest picture of the company's real structure.
Install
I build the AI operating architecture mapped to what the audit surfaces — not to the inherited org chart. Folder-based, plain markdown, version-controlled. Built on Interpretable Context Methodology. Delivered as a Git repository the company owns outright. No proprietary platform. No license fees. No lock-in.
Handoff
A live training session. A written playbook. Seven days of post-install support. The architecture is built to be left — if the install is correct, you won't need me afterward. That is the test of whether the work was real.
Strategy is downstream of what your company actually is.
Every business runs on an implicit theory of itself. What it is. What exists inside it. What the customer is actually buying. The founder almost never wrote this down. The team inherited it through observation. The customer experiences it as coherence or friction.
Most strategy work, most operations work, most consulting work, sits on top of this layer without ever touching it. The assumption is that the layer is settled — that everyone already agrees on what the company is, and the only remaining questions are tactical.
But the layer is rarely settled. The founder's theory of the company drifts as the company changes. The team operates from a different theory because they see the daily work, not the original vision. The customer is buying something the company doesn't quite know it's selling. Three different theories of the same business, each partially true, none complete, and nobody making the gap visible.
Strategy applied to the wrong picture compounds in the wrong direction. This practice works that layer first.
Engagements in progress and documented.
The architecture is built on Interpretable Context Methodology.
The technical foundation of every install comes from a published methodology called Interpretable Context Methodology — ICM. Formalized in a 2026 paper applying fifty years of Unix engineering principles to the problem of orchestrating AI agents.
The methodology's central claim is structural: folder structure is agent architecture. Instead of writing application code to coordinate multiple AI agents, you organize the prompts, context files, and reference material into a hierarchical folder system. The folder structure does the work a multi-agent framework would otherwise do in code.
I install ICM-based architecture because it is the cleanest available method for translating an audited substrate into an operating system. The folder hierarchy mirrors the corrected structure of the business. Every file is plain markdown — readable, editable, and inspectable by any operator on the team.
The paper proposes a five-layer context hierarchy — workspace identity, task routing, stage contracts, reference material, and working artifacts — delivered through a numbered folder structure rather than orchestration code. The result is a system where one agent, reading the right files at the right moment, does the work that would otherwise require a multi-agent framework.
The methodology is open source under the MIT license. It is the architectural foundation of every install I do, calibrated per engagement to the substrate surfaced in the audit.
What I am actually doing when I read a business.
A business is not what it says it is. It is what it actually moves through the world. What it absorbs from the people who pay it. What it leaves behind in the team that runs it.
When I read a company, I am not looking at strategy, branding, or operational efficiency — those are downstream. I am looking for the gap between what the company claims and what the company does. The phrase the founder reaches for when pressed. The workaround three operators all share but nobody documents. The thing the customer actually pays for, which is often not the thing on the invoice.
What I am listening for is what the business actually produces. Marketing copy can lie. Pitch decks can lie. But the work the company is actually producing, the customer it is actually keeping, the team that is actually operating — those things cannot lie. They are the substrate expressing itself.
The relief most founders describe after the audit is not because they were told something flattering. It is because somebody finally said the thing they had been carrying without language for.
This work fits a specific state — not a specific size, industry, or stage.
The work does not require a particular revenue level, industry, team size, or business model to land. It requires a particular state:
You have built something real. The work is happening. And somewhere underneath all of it, you have felt the frame slip — the quiet recognition that the company you have built no longer matches what it was always actually about.
You are about to hire someone you privately know is not right. You are about to launch something that doesn't quite fit. You can tell the difference between a consultant selling you a service and someone bringing you a perception, and you want the second. The price reflects what the correction is worth at the scale you are operating.
Who is doing this work.
Founder, Substrate
Dallas, Texas · 2026
I am the founder of Substrate, a practice for reading businesses at their structural layer and installing the AI operating architecture that lets them run from what they actually are.
Before this practice, I spent two years building AI-native workspace architectures across multiple ventures — including ongoing engagements with founders developing operating systems for their own companies. The methodology I install is one I arrived at in my own work before encountering the published research that formalized it.
I came to this work through a convergence of contemplative practice, philosophical study, and direct technical building. Most people who can read frames cannot build the technical systems that materialize them. Most people who build technical systems do not work at the frame level. Substrate is the practice where those two capacities meet.
How I work
A small number of engagements at any given time. Each one bespoke — the audit and architecture calibrated specifically to the company in front of me. The work scales by stakes, not by volume. The price reflects what the correction is worth at the scale you operate.
Where to find me
The thinking behind the work.
Long-form essays on the methodology, the structural questions that shape every engagement, and field notes from the architecture I am building inside my own companies. Updated cyclically as pieces become clear enough to publish.
The best pieces never touch the site.
The public essays are published here. The premium editions — the field manuals, the pieces on making AI pay, the long reads on perception and structure — go out only by email. Subscribe to get both: the free essays when they publish, and the premium pieces the site never sees. No cadence, no filler.
If the work fits, the right next step is a conversation.
I take a small number of engagements at any given time. If you have read this far and the work fits something you have been carrying, write to me. Tell me a little about your business in your own words — what it is, what it has become, where the friction is showing up. No deck, no proposal, no formal intake.
I am taking the next three engagements at zero fee in exchange for documented case studies.
Three founders. Three full engagements — audit, install, handoff. Real work, calibrated to your business, delivered to the same standard as a paid engagement. The architecture is yours to keep. The exchange is documentation rights.
What you commit to:
- The audit phase — four to six conversations over two to three weeks, plus access to the operators on your team.
- The install phase — four to six weeks of structured work to install the operating architecture.
- The handoff — a live training session and seven days of post-install support.
- Documentation rights — an anonymized case study published in the Reading Room six months after the engagement closes.
What I am selecting for: founders who have built something real, who can articulate where the friction is showing up, and who are willing to have their assumptions examined honestly.