When another agent — corporate, government, friendly, or hostile — wants something from yours, it does not get in without consent, scope, and a receipt. The Handoff is that meeting. It is open, not owned.
Beneath every handoff is the Personal Consent Handshake Protocol — PCHP, or hu_ssh for short. It is, deliberately, the human equivalent of SSH: the secure shell engineers have trusted for thirty years to connect machines without exposing the secrets that make them work. It runs the same four phases, every time.
Who are you, really? Not what you claim. What you can prove.
What, specifically, do you want? For how long? For what purpose? When does consent expire?
You get exactly what was negotiated. No more, no less, scoped to the moment.
Both sides sign a receipt. Both keep a copy. Both can be held to it later.
PCHP is not a walled garden. It is a consent layer that composes over the open agent rails — adding identity, scope, and a receipt to each.
MCPModel Context ProtocolHow an agent reaches tools and data. PCHP wraps each access in consent and writes it to the ledger.
A2AAgent-to-AgentHow two agents talk. The handoff is the PCHP handshake when two Ones meet.
AP2Agent PaymentsHow agents pay. PCHP gates the settlement and records it on both ledgers.
UCPOpen commerce railsHow agents transact. PCHP scopes what is shared, with the receipt on your ledger.
RFC-001 is published under an open license — any product may implement it. No patent is claimed on the core handshake. We want others to build to the standard. That is how a category spreads.
The protocol is open. The reference work is public. Bring your own agent.
One is a product of Hushh Technologies Corporation (brand: 🤫 “hussh”), an independent company. One runs on third-party silicon, systems, and cloud; all company names are used solely to describe the platforms on which One software runs. Hushh Technologies is not affiliated with, endorsed by, sponsored by, or partnered with any company named.