Intent Mediation Platform

Where this came from

Twenty years of other people's broken machines, and an English degree that finally turned out to be the useful one.

Before

PHP, MySQL, and a second pair of eyes

Pair-programmed, shipped, maintained. The habits that stuck came from working beside somebody: say what you are about to do before you do it, and let the other person stop you. Every gate on this site is that habit, written down and given a mechanism.

Since 2006

South City Computer

Friendly honest advice, first from St. Louis and now from Puerto Morelos. Nearly seven thousand tickets, more than three thousand five hundred customers, eight years of the operating record still intact and since recovered into a database. Machines came in broken and went out working, which is a trade with no room for a confident story about what probably happened. It is still trading.

What the shop taught

Custody, consent, and not looking

Every machine had a physical place and a state you could read off a label from across the room. Nothing moved between stages without the guard for that stage clearing first. A customer approved the estimate before a card was charged. And when data had to be moved off a failing drive, it was moved as one folder named for the ticket — a technician never saw a filename. Not a policy. A procedure that made curiosity impossible.

Now

The same shop, for software

The custody model became the control plane. The consent step became the approval a plan needs before any build begins. Not looking in the sock drawer became the architecture: a document is decomposed on your own machine, and a model is shown structure rather than content. The procedure was always the valuable part. The code was the easy part.

The English degree

For thirty years it was the thing that came up at parties. Then the machines arrived that take language as their input, and it turned out the discipline that matters is the one that asks what a word actually refers to, whether two people using it mean the same thing, and what happens to an argument when they do not.

That is not a metaphor here. The vocabulary is a table. A word has a definition, a scope note, a status and a ratification. Two words for one thing is a defect a program reports. And whether models actually read a word the way it was intended was not assumed — it was measured, by putting the question to several of them and counting where they disagreed.

And the part that still seems unreasonable

After all of it — the shop, the tickets, the languages, the years — I can describe what I want in plain English and watch it get built, correctly, against a library I spent those years making honest.

That is what this is for sale as. Not a chatbot that writes code. A workshop where the words do the work and the machine is not allowed to guess.