One Lens — Curator model for ads and content
One Lens — the Curator-model agent in One that mediates ads and content on the user's terms. Free as trust-builder; PCHP handshake API revenue is Phase 2; no Hushh-branded ad marketplace.
TL;DR: One Lens is the Curator-model agent in One that mediates ads and content for the user — suppresses adversarial ones, curates wanted ones, audits every decision through PCHP consent receipts. Three-way fork resolved: Pure Shield (sub-only blocker) and Marketplace (consent-mediated ad network) both rejected; Curator chosen. Free as trust-builder; revenue comes from the PCHP brand-side handshake API infrastructure (Phase 2, gated on 10K+ engaged users + legal review). No Hushh-branded ad marketplace. No token rewards. No impression-weighted ad spend revenue.
Status as of 2026-05-10: see body.
Relations
- One - platform Lens would run inside.
- PCHP - consent primitive for attention requests and audit.
- BYOA - open model/API/system posture.
- Personal Operating Layer - iOS-platform-aligned positioning.
- Distribution memo - private supporting artifact not public-linked.
- Market memo - private supporting artifact not public-linked.
- One Lens - Three-Way Fork - chosen/rejected architecture fork diagram.
Why this concept exists
Modern consumers experience advertising as adversarial — interruption, surveillance-grade tracking, and dark-pattern personalization optimized for the advertiser's funnel, not the user's life. Existing responses fall into two failed categories:
- Pure ad-blockers (uBlock, Brave's shields). Subtractive only — they suppress, but don't help the user discover better signal.
- Personalized-ad networks (Google, Meta, Amazon DSP). Additive but advertiser-funded — the user is the product.
One Lens is a third path: a personal agent that mediates content and commercial messages on the user's terms, with no advertiser money flowing into Hussh's economics, and with consent semantics enforced by PCHP.
The three-way fork — chosen path is Curator
Three architectures were considered:
| Model | What it is | Why rejected (or chosen) |
|---|---|---|
| Pure Shield | Subscription-only blocker — suppress ads, surface nothing | Subtractive only; doesn't earn the right to be the consent layer |
| Curator (chosen) | Agent-mediated suppression and surfacing on the user's behalf, no advertiser money flow | Aligns with consent-first thesis; user pays nothing initially; revenue path is PCHP infrastructure, not ad spend |
| Marketplace | Consent-mediated ad network with brand payment to Hussh | Rejected — Hussh-branded ad marketplace contradicts "your data, your business" and creates the same monetization gravity that ruined Google/Meta |
One Lens ships under the Curator model. The decision is structural — there is no v2 path from Curator to Marketplace without violating the non-negotiables.
Architecture
One Lens runs as an agent on top of the One platform, using the same PCHP consent primitives every other agent uses. It does three things:
- Suppress. Blocks intrusive ads, trackers, and dark-pattern UX on consented surfaces (web, email newsletters, push notifications, in-app feeds where extension surfaces permit).
- Curate. Surfaces commercial messages and content the user actually wants — based on intent the user has expressed, not on tracking they didn't consent to. The user can ask Kai "find me deals on hiking gear" and Lens curates inbound from any source the user has connected.
- Audit. Every suppression, every surface, and every consented commercial message is in the user's Transparency Log. The user can ask Lens "why did you show me this" and get a real answer with a real consent receipt.
What's free, what's paid, what isn't there
- Free. Lens ships free as a trust-builder. The user pays nothing for suppression or curation. This is non-negotiable; charging for ad-blocking would put Hussh on the same side of the table as the parties Lens is mediating against.
- Paid (later). Hussh's revenue comes from the PCHP handshake API infrastructure — brand-side endpoints that let advertisers and publishers request consented attention from a user, mediated by the user's agent, with auditable receipts. This is Phase 2 and explicitly gated on 10K+ engaged users on Lens plus legal review by our legal counsel.
- Never. No Hushh-branded ad marketplace. No token / cryptocurrency rewards model. No standalone browser. No impression-weighted ad-spend revenue. No "free with ads" tier.
Why "One Lens"
Working name. The metaphor is right — Lens shapes what the user sees without becoming the thing being seen. One (the platform) gives Lens the consent substrate; Lens gives One its first user-facing reason to enforce that substrate aggressively. Naming may evolve before launch but the metaphor should not.
Counterarguments worth arguing with
- "Pure Shield is simpler and sells today." Response: simpler, yes; but a sub-only blocker is a feature, not a moat. Brave proved the model works at small scale and stalls when it tries to grow into more. Curator is the larger thesis.
- "You're leaving advertising money on the table." Response: yes, intentionally. The PCHP infrastructure-revenue path is harder to build but doesn't drag the company into the surveillance economy. The DRIP-ON-grade discipline of refusing the easy revenue is the differentiator.
- "PCHP brand-side endpoint is the marketplace by another name." Response: it is the protocol under which any party can request user attention with cryptographic consent. Hushh does not publish the inventory, does not match buyers to sellers, and does not take a cut on impression spend. The protocol is open for any third party to use; Hushh's revenue is on the API tier, not the transactions.
What this is not
- Not shipped. Curator is the architecture choice; the agent is unbuilt as of 2026-05-10.
- Not a denial that brand-side PCHP endpoints will eventually exist. They will — Phase 2 — gated on user adoption and legal review.
- Not a competitor to existing ad-blockers in the value-proposition sense. The pitch is consent infrastructure, not feature parity.
- Not an Apple-endorsed product. One Lens runs on top of One, which is an iOS-platform-aligned product per the Personal Operating Layer thesis.
Architecture alignment/status refresh
- Current repo truth: One Lens is north-star UX framing unless checked UI/runtime proof exists for a specific surface.
- North-star direction: One mediates context and attention through consented specialist workflows.
- Not shipped / not implied: One Lens is not an ad marketplace, CRM data lake, or partner-owned profile mirror.
- Source posture: internal references back this frame; public prose should avoid repo-relative paths and private partner labels.