Case Study · July 11, 2026 · 5 min read

Built by Its Own Rules

The strongest test of a system is whether its author will use it. This publication was built with the exact framework it teaches, AI-assisted and human-accountable. Here is how, including where I was breaking my own rules.

The strongest test of a system is whether its author will use it. Not describe it, not sell it, use it, on their own work, in public, where the gaps show.

So here is the most honest thing I can hand you: this publication, built with the exact system it teaches. Every claim in it, applied to itself.

What this is

Translational Intelligence is the capacity to turn new capability into durable advantage, again and again, as the technology moves. This site is that capacity made concrete. It has a system, a discipline, a role, and a destination. I did not only write about them. I built the thing you are reading by their rules, and this is the accounting.

Buy the record, build the intelligence

The stack is a live example of the discipline. I bought the commodity, the system of record, and I built the layer that is mine.

Bought the record, built the intelligence Two columns. Bought, the record: Astro and Keystatic, Beehiiv, Cloudflare Pages, GitHub, the frontier models. Built, the intelligence: the design system, the signature diagrams, the Artifact Library, the voice and the ethos, the connected argument. BOUGHT · THE RECORD BUILT · THE INTELLIGENCE Astro + Keystatic Beehiiv Cloudflare Pages GitHub The frontier models The design system The signature diagrams The Artifact Library The voice and the ethos The connected argument
The commodity, bought. The differentiation, built. The same discipline I write about, applied to the thing you are reading.

Astro and Keystatic hold the pages. Beehiiv sends the email. Cloudflare serves it, GitHub holds the source, and the frontier models do what frontier models do. None of that is where the advantage lives, and writing my own would have been vanity. What I built is the layer that is genuinely mine: the design language, a signature diagram in every piece, the Artifact Library, the voice, and the way every page links into one connected argument instead of a feed. No vendor could sell me that, because no vendor has my problem.

And it leans build more than the old wisdom would, on purpose. The ethos is that in this era the line has moved toward build, and that adoption is won by solving small. This site is a stack of small builds, each one shipped before the next was started.

There is no AI work product

Here is the part most publications about AI will not say out loud. This one is AI-assisted. I use AI to draft, to argue with, and to build the site itself.

And there is no AI work product, only AI-assisted human work product. I am the author of record. Every claim, every number, every diagram, I own completely, whether I, a colleague, or a model produced the first version. That is not a hedge or a disclaimer. It is the standard I ask you to hold, and I am holding this publication to it in the open. A standing note now sits on the About page, because I preach disclosing AI assistance where it is material, and for a publication about using AI well, it is material.

I do not automate the struggle

I do not use AI to skip the thinking. I use it to reach the hard part more often. The ideas start with me: an argument I have been circling, a contradiction I cannot yet resolve, a claim I suspect is true but cannot defend. Only then do I put the model to work, and I put it to work making the problem harder, not finishing it.

The Think-Harder Writing Workflow is not a theory I admire. It is the process that produced every piece here, this one included.

Where I was breaking my own rules

A case study that shows only the wins is exactly the premature coherence I warn about. So before I published this, I audited the site against its own written rules. Here is what I found.

Every Issue is supposed to carry its own signature diagram. When I ran this audit, the founding piece was the one exception. It has one now, added the same day I wrote this. A rule you write down only means something if the gaps get closed, not just noted.

I preach disclosing AI assistance where it is material, and until this study there was no disclosure anywhere on the site. That was a real gap in the thing I most insist on. It is why the About note now exists, and why this case study does.

The cadence labels, the Tuesday and Friday stamped on everything, had drifted from useful into decorative, so I cut them back to where they inform.

None of these are catastrophes, and that is the point. The value of holding yourself to a standard you wrote down is that the gaps come out small and findable, instead of large and hidden. A company that never audits itself against its own rules does not have fewer gaps. It just has not looked.

Monday morning

If you want to know whether a system is real, watch whether its author will apply it to themselves, in public, with the gaps left in.

Try the thing this piece just described. Take your own AI strategy, the version you would show your board, and audit it against the rules you have written down. If you have not written the rules down, that is the first gap, and it is the biggest one. Then fix the smallest thing you find this week. That is where it starts. It is where this started too.

Cheers,
-Titus

The next one

Get it in your inbox.

New Issues, FAQs, and Case Studies as they go out. Each one names something, explains something, or hands you something you can use on Monday. Subscribe, and I will send each as it goes out.

Prefer the tool you already think in? Here is how to read it in your chatbot.