About HoopGram
Sovereignty Roadmap: Now, Gaps, and Destination
Fourteen domains, each marked with what's reclaimed, what's missing, and where it ends.
Read this map through four tests — source, migrate, audit, unplug; we only describe as current what is implemented, and honestly label the rest as a gap and a destination.
The sovereignty roadmap
| Domain | Returned or foundational today | Partial-sovereignty gap | Destination |
|---|---|---|---|
| Memory and knowledge | Local state and a sovereignty export lane are implemented. | An independent implementation still needs to prove open reading and migration. | Memory remains with the same person across model, machine, or company changes. |
| Files and storage | Local file state enters the export contract. | Important entry paths such as phone photos still need work. | Open formats, complete export, and restore in any compatible implementation. |
| Audit and migration | Path-whitelisted restore and post-restore service checks provide a foundation. | Rebirth in an independent implementation and automatic drills remain unproven. | Validate, restore, and migrate without the HoopGram factory. |
| A self-hosted mail foundation exists. | Sending may still depend on a relay or provider, and native phone experience needs proof. | Portable data, replaceable providers, and no locked sending path. | |
| Contacts and calendar | A local source of truth exists. | Native-device sync and the unplugged experience remain incomplete. | Open-protocol device sync and complete migration. |
| Network | Personal-node networking is implemented. | Portable configuration and provider replacement need continuing proof. | Network entry belongs to the owner, not a VPN company. |
| Identity and name | Login and node naming have a local foundation. | The identity root is not owner-held and the default name still depends on a HoopGram domain. | Owner-held root key, owner domain, revocable devices, and stable identity across machines. |
| AI brain | Memory and permissions can stay home while external models supply cognition. | A single model pool or interface creates dependence, and local fallback remains limited. | Replaceable providers, owner BYO, local offline fallback, and a new brain without a new person. |
| Money | A self-custodied on-chain wallet and permission gate provide a foundation. | Fiat and external payment networks cannot honestly be represented as fully reclaimed. | Owner custody where possible and explicit disclosure where dependence remains. |
| Phone number and SMS | A capability-interface foundation exists. | Numbers remain in carrier systems and have limited unplug ability. | Replaceable providers, portable records, and identity that is not rooted in a phone number. |
| Hardware | The machine can migrate, while its physical host may still be rented from a cloud vendor. | A cloud landlord still controls the physical layer. | The same Hoop can live in an owner box, home server, or any compatible machine. |
| Social graph | We do not claim a centralized social graph has been reclaimed. | Relationships living only in a platform database cannot be unplugged. | Hoops connect through a public protocol instead of another central platform. |
| Passwords and passkeys | We do not currently claim they are reclaimed. | This remains a major identity-sovereignty gap. | Owner custody, agent unreadability by default, recovery, and migration. |
| Browser bookmarks and history | A browsing-capability foundation exists. | A local source of truth and portable format are unfinished. | Browsing records stay owner-side and migrate across implementations in open formats. |
Three things we acknowledge publicly
- Export, recovery, and audit are a sovereignty foundation, but only an independent implementation and real drills can prove this is more than one company's self-description.
- An owner-held identity root, owner domain, second backup destination, and replaceable brain are central to surviving the removal of HoopGram.
- Some powers remain constrained by carriers, fiat networks, or physical hardware; we disclose that instead of calling access ownership.