Products
One, Kai, Nav, PCHP, iBrokerage
11 pages
- One App Shell — unified dashboard and onboarding architectureThe One App Shell is the unified user experience container for the personal operating layer, consolidating setup workflows, connected systems, and agent sessions into a single, responsive web and mobile interface.
- Onepoint Agent — client-encrypted location-sharing surfaceThe Onepoint Agent is a recipient-scoped, client-encrypted foreground location-sharing platform surface. Plaintext coordinates are never stored on the server or transmitted in API responses, ensuring absolute user privacy.
- Email Agent — inbox specialist under OneEmail Specialist under One that processes inbox nudges, inline email chat, email receipts tracking, and secure A2A email delegation.
- Gmail Agent — receipts specialist under OneGmail Agent is the specialist under One that parses and stores purchase receipts, structures spending memory, and tracks sync status securely.
- One — the personal agent platformHussh's approved top personal-agent direction. One owns relationship framing and specialist handoffs; current shipped runtime remains Kai-first unless route, test, and deploy proof says otherwise.
- iBrokerage — first consumer productFirst consumer product direction on top of One/Kai/PCHP. Aha Moment language is an acceptance target; shipped claims require checked code, tests, and UAT evidence.
- Kai — finance specialist under OneCurrent mature finance, investor, portfolio import, market, RIA, voice/search/action, and decision-receipt specialist runtime under One. Kai does not own platform identity, consent policy, vault/deletion, or privacy authority.
- Nav — privacy guardianApproved privacy and consent guardian direction inside One. Treat Nav runtime claims as future or checked-surface language unless route, test, and deployment proof exists.
- PCHP — Personal Consent Handshake ProtocolHussh consent protocol implemented today through Consent Protocol, Developer API, hosted MCP consent/export, and audit flows; future UI and rules-engine surfaces remain separate until proven.
- PCHP Consent Handshake — SequenceMermaid sequence diagram of a PCHP-mediated read — CRT issuance, DAT derivation, ephemeral envelope, Transparency Log entry.
- PCHP v0 Token Format — JSON SchemaJSON Schema for PCHP v0 CRT + DAT wire format. Concept-stage; RFC reference, not implementation-stable.