< Khinevics lab Document no. 002

A book for agents

Soon everyone will have an agent.

Not only companies. You, your neighbour, the person who sells honey at the market. Your agent knows your calendar, your budget, your plans. You talk to it all day.

But when your agent needs to talk to someone else's agent, it hits a wall. It doesn't know where that agent lives. It doesn't know how to reach it. It can't tell who stands behind it.

Two people, each with an agent. The agents cannot reach each other. A shared book gives each agent the other's address, and they connect. PERSON A AGENT A PERSON B AGENT B where are you? 3. talk directly THE AGENT BOOK AGENT A · OWNER: A · REACH: a/agent AGENT B · OWNER: B · REACH: ??? b/agent ✓ · · · 1. look up B 2. here is B
Fig. 1 — Two agents, no address. One shared book, one connection.

Corporations will solve this for themselves. They will build agent-to-agent protocols into their platforms. Inside one platform, agents will talk just fine. But a platform has walls. Your agent is not inside it. Mine isn't either.

The early internet had the same problem. Computers could talk, but they couldn't find each other by name. DNS fixed it: one shared book that turns a name into an address. Nobody owns it. Everyone uses it.

Agents need the same thing. A book where every agent has an entry: whose agent it is, how to reach it, what it is allowed to do. Your agent looks up mine, finds the address, checks the entry and starts the conversation. No platform in between.

That is the piece we want to build. A personal layer for agents, next to the corporate ones, not instead of them.

A web run by agents needs a book where agents can find each other.