Today a thousand companies each keep their own quiet copy of you. None of them showed it to you, none of them asked, and you cannot correct or delete any of it. The inversion is simple to state and hard to build: you keep one profile, you own it, and the world subscribes to the parts you grant.
Most of the machinery for that is already running. What was missing was anything showing it as one path, which is this page.
- 1
Name your agent
live todayA name that is yours, and an address other people's agents can reach.
The name normalises to a spaceID. The @ sigil means it can never collide with a route on this site, so the namespace stays clean without a reserved-word arms race.
- 2
Hold it
live todayThe name is recorded against your email while the rest is built.
A reservation, not a claim. There is no service yet that permanently binds a name to a person, and we are not going to use the word that implies one.
- 3
Your agent learns your world
live todayIt reads only the sources you connect, and shows you everything it worked out. Wrong? Change it. Do not like it? Delete it.
The Personal World Model. The agent searches public sources at your request, shows its plan, its reasoning and its sources as it goes, and is instructed that an empty section is a correct answer. Nothing is stored yet.
- 4
It becomes one profile you own
in designOne canonical profile instead of a thousand shadow copies held by a thousand companies who never showed you any of them.
The Personal Knowledge Model, expressed in the published vocabulary: 252 scopes across 7 roots, each carrying a tier that governs what may ever happen to it. Privacy preferences first, because that is the one thing every site already needs from you, then outward into the ordinary texture of a life.
- 5
Agents subscribe to it
live todayA hotel, a shop, a doctor's office asks for specific things for a stated reason. You grant or refuse each one, and you can take it back.
An agent fetches your model at /api/pkm/<your-name>. The public slice is served to anyone. Trusted and private scopes are not served there at all. They require a consented request through your own agent, and every access leaves a receipt.
Check it yourself
Stage five is the one people assume is a mock-up, so here is a real spaceID with a real model behind it, served right now:
curl https://hushh.ai/api/pkm/manishussh
The public slice, served to anyone who asks. Trusted and private scopes are absent from this response by design. That is the protocol working, not a gap.
What it is for: walking into a hotel
You walk into a hotel. Instead of a form, your agent hands theirs exactly what the stay needs: the room you like, the allergy that matters, the arrival time, and nothing else. The three most sensitive of those twenty are ticked one at a time, never bundled. The same shape works for a restaurant, a clinic, or a massage therapist: the check-in decides what they learn, and you decide the check-in.
hospitality.stay — “Look after me during my stay” — is a real entry in the published registry, carrying 20 scopes of which 3 must be ticked individually. It is one of eight purposes, drawn from the same 252-scope vocabulary every other surface uses. Not an illustration written for this page.
🤫