🤫 The Protocol Briefing — PCHP, end to end

What's covered

1 · The consent gap & the ingestion boundary

2 · Roles & the trust boundary

3 · The six-phase handshake

4 · HCT (shipped) vs CRT/DAT (proposed)

5 · Scope grammar & the sealed envelope

6 · The transparency log

7 · Where PCHP sits vs TLS, x402, PACT, OAuth

8 · The threat model

9 · Conformance levels, stated honestly

10 · The Apple Silicon / MLX reference implementation

11 · Native mobile: Swift, Kotlin, and the device-SDK layer

12 · Governance, license, and lineage

13 · Private Agent One — the first implementation

Sources

On our site

The full PCHP specification (pchp/2026-07-12) — the normative source every claim in this film is checked against.
The Hussh Protocol — the consumer-facing overview.
PCHP goes public — the launch reel.
PCHP, donated to the world — the donation announcement.
The Handoff (RFC-001) — the five-stage handoff event between two Ones.

On the wiki

PCHP — Personal Consent Handshake Protocol — the canonical internal reference, including shipped-vs-proposed implementation truth.
Nav — privacy guardian — the product direction this film's host embodies.
Three-layer architecture — where PCHP sits as the inner moat layer, under One and Fund A.

Prior art & standards this work builds on

Model Context Protocol (Anthropic) — the direct structural inspiration: date-based versioning, capability negotiation, an open governance process.
RFC 2119 / RFC 8174 (IETF) — the normative keyword conventions the spec is written in.
OAuth 2.1 & the IETF OAuth working group — the authorization primitives PCHP composes with (scopes, resource indicators, audience binding).
W3C WebAuthn / FIDO passkeys — the model for the target-profile owner-approval attestation.
The Kantara Initiative — early consent-receipt work that treated consent as a first-class, portable artifact.

This film describes a public request-for-comments specification (pchp/2026-07-12). Level 1 Baseline items (the six-phase handshake, HCT tokens, the scope grammar, the transparency log, global revocation, the zero-knowledge envelope) are shipped in the Hushh reference implementation. Level 2 High-assurance items (CRT/DAT Ed25519 tokens, tamper-evident logging, capability envelopes), and the Apple Silicon / MLX reference work, are proposed and directional — not general-availability claims. Benchmarks shown are from an internal development environment, not third-party audited. Hosts are AI-generated. 🤫 hushh research · PCHP