thought leadership
A Public /writing: Ownership, Reputation, and a Machine-Readable Home for the Thesis
I did not add /writing to decorate the site. I added it because ideas that live only in chat threads, deck margins, and rented feeds do not compound—they decay. A public, canonical surface on a domain I control is the smallest honest unit of reputation on the open web: here is the thesis, here is how it evolved, and here is how it ties to the work.
Rented audience is a bad data model
Every third-party platform optimizes for its own retention curve, not your narrative spine. LinkedIn rewards velocity. Medium buries you next to listicles. Shared docs are for collaboration, not for clarity at a distance—a stranger, a partner, or an agent that needs to know what I actually believe about agentic infrastructure without parsing twelve versions of a strategy memo. When the distribution layer owns the URL, you are always one algorithm tweak away from explaining yourself twice.
What /writing is
It is a home for long-range argument: case studies, hot takes, and operator notes that would otherwise get trapped in the wrong container. It sits next to the rest of couch.cx so the through-line is obvious: strategy is not a slide; it is a published edge in the same graph as the work. That is the RAPP lens too—technology strategy and transformation that has to be legible to executives, builders, and increasingly to the systems that sit between them.
Machine-readable is not a buzzword here
I care whether a page can be quoted, linked, and reasoned about by humans and by agents. That is the same instinct behind caring about DESIGN.md, Stitch, and brand velocity, and behind the bet in why I back agentic infrastructure: the surface is part of the stack. When the thesis is published in one place, it becomes referenceable infrastructure for everything else I ship.
Bottom line
/writing exists so the ideas are owned, durable, and portable—not so I can collect applause on someone else’s rails. If you are building in public, start by owning the URL.
Where to go next
If you want the same argument in a different key: Ship the note (what publishing here does for the build), or build skills, not agent armies for the operator stack underneath the prose.