Skip to content
Hussh
Connect MCP

One — the personal agent platform

Hussh'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.

Product

TL;DR: One is Hussh's personal-agent platform direction: the relationship layer where the user owns context, grants consent, and summons specialists such as Kai, Nav, and KYC.

Status as of 2026-05-19: see body.

Relations

What One is

A personal agent platform: the user's context becomes useful only through consented specialists and clear receipts. One is the relationship layer; PCHP is the consent protocol underneath; specialists such as Kai, Nav, and KYC do bounded jobs instead of collapsing into one generic assistant.

The naming discipline is deliberate. As of mid-2026 the agentic-product market is racing to ship "an AI assistant" or "a personal agent." The risk for Hussh is that One becomes a generic noun, the platform name disappears, and the brand collapses into another assistant SKU. The capitalized One plus named specialists gives users, builders, and partners a vocabulary for separate responsibilities.

Specialist model

One should feel simple to the user, but the system underneath should stay separated by responsibility.

  • Kai — finance and investor specialist. Warm, present, brief. Assembles financial context, portfolio/import state, market questions, and decision receipts.
  • Nav — privacy and consent guardian direction. Precise, composed, audit-grade. Makes scope, exposure, revocation, and audit legible.
  • KYC — identity and verification specialist lane. It should not be erased into Kai or Nav when identity proof is the real job.

The split is on purpose:

The specialist that helps you and the guardian that protects you should not be the same unchecked authority.

What One is not

  • Not a chatbot. The interaction surface is voice plus glanceable cards, not a chat log.
  • Not an LLM router. Models are interchangeable underneath (BYOA); the user never picks one.
  • Not a data lake. The user owns the vault context; partners do not receive broad memory mirrors.
  • Not an SSO. PCHP is a consent protocol, not an identity provider.

Brand discipline

"One" is always capitalized in Hussh product contexts. The numeral "one" used non-product-wise is the only allowed lowercase.

Repo truth and north-star boundary

  • Current implementation truth: internal engineering evidence treats One as the approved top personal-agent direction, while the mature current runtime remains Kai-first unless a checked route, manifest, test, or deploy artifact proves a specific One surface.
  • North-star direction: One owns the relationship and summons specialists such as Kai, Nav, and KYC through scoped consent and policy boundaries.
  • Not shipped / not implied: this page does not imply full One/Nav default runtime, raw vault export, partner memory mirroring, or any enterprise-platform implementation detail.
  • Evidence boundary: backed by internal Hussh architecture and agent-ontology notes current as of 2026-05-19.

Sources

  • Kai — current mature finance specialist under One.
  • Nav — privacy and consent guardian direction.
  • PCHP — consent, scope, export, and audit protocol.
  • Three-layer architecture — protocol/platform/fund framing.
  • Internal Hussh architecture notes — One/Kai/Nav/KYC hierarchy and view-catalog boundary, current as of 2026-05-19.
  • Internal Hussh brand invariants — capitalization and product-name discipline.