New protocols for AI
I really like this provocation in Tina He’s 2026 open inquiries:
Where does value pool when everything interoperates? Who decides what gets included in the default spec? What becomes the DNS for agents —
the universal directory of capabilities, reputations, revocations? And critically, what’s the TLS-equivalent for intent, the cryptographic proof that an agent’s request actually represents a human’s will?
I say “provocation” with some precision: I am both dazzled and dismayed by Tina’s questions. By her whole post, actually. I suppose I always want to see a little “why” mixed in with the urgent “what” and “how”. The broad “why” of the AI industry (and affiliated enthusiasts) in early 2026 seems only to be “because we can; because it is upon us”. That’s not an uncommon response to technology, but naturally I’m interested in going a bit deeper.
Of course, one approach would be to answer the questions Tina is asking.
It’s a few years in the past now, but my experience specifying and building the protocol I called Spring ’83 remains very instructive. After laboring over this, my first spec, I wrote:
I really strongly recommend this exercise to anyone who feels dissatisfied with their options on the internet today. Give it a few evenings. Imagine something new; describe it as clearly as you can.
It just occurred to me —
Returning to the “why”, it would be exciting to see new protocols for AI systems and agents that aren’t only efficient but also deeply opinionated —
The AI industry is at this moment far more centralized than the computer industry at the dawn of the internet. That doesn’t bode well for interesting protocols … interesting topologies of power and access. But I don’t think it’s going to stay this way; certainly, I hope it doesn’t; and good, weird, persnickety protocols won’t only arise in response to the industry’s transformation —
P.S. I still love RFC 865, the Quote of the Day protocol.
To the blog home page