Products
One, Kai, Nav, PCHP, iBrokerage
8 pages
- 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.
- One App Shell — unified dashboard and onboarding architectureThe public concept and architectural guide for One's unified app shell, unified onboarding, and responsive bottom-navigation design.
- 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.
- 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.
- 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.
- 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.