About HoopGram
What Hoop, HoopGram, and Hoop Protocol Are (and Aren't)
Three names people conflate — each one's boundary, in three sentences.
Hoop
Hoop is your machine, and the AI that lives there and stays with you — a product, but yours.
It may run on many companies' servers, models, and networks, yet the root of its identity, memory, and choices should stay on this machine as much as possible.
The model can change, the machine can change, the provider can change; your identity, data, memory, and choices should continue to exist.
HoopGram
HoopGram is the company that builds Hoops — checkout and keyhole, never a handler of your Hoop's data.
It helps with purchase, delivery, support, and connection, but it is not the handler of your Hoop's data, nor your identity root.
You must be able to unplug HoopGram and still move forward with everything that is yours.
Hoop Protocol
Hoop Protocol is the public rulebook — anyone can implement it, anyone can leave HoopGram; the draft lives in its own repo.
It is a draft kept in an independent repository that anyone should be able to read, implement, test, and improve.
It turns leaving HoopGram into an implementable, verifiable choice, not just a promise.
Between the three
- HoopGram → Hoop buy, configure, support
- Hoop Protocol → Hoop follows its rules
- HoopGram → Hoop Protocol commits to it
Laid out from the Hoop Protocol repo's public-site-copy/00-triad (a proposal draft); the protocol repo's own public version will be authoritative once released.