Phosra Link × Chirp — end-to-end walkthrough

1 · Chirp before any parental controls

One family account with three profiles. Maya is 12, and her feed shows everything, including 16+ and 18+ posts.

Chirp sign-in page — **01Sign in to Chirp Chirp**The family account, `dana@chirp.test`.

02Pick a profile ChirpDana (parent), Leo (15) and Maya (12).

Maya's unrestricted feed — **03Maya's feed, unrestricted Chirp**All 12 posts, including two 18+ and two 16+. Click to see the full page.

2 · The parent's control panel

Guardian is where the parent sets the rule, once, per child: content rated up to 13+. Each child has a Chirp connection that starts as “Not connected”.

Guardian parent sign-in — **04Parent signs in to Guardian Guardian**Phosra never sees this login; it binds to the parent's existing session.

Guardian dashboard, not connected — **05Family controls Guardian**Maya and Leo, each with the rule “Content rating: up to 13+” and Chirp not yet connected.

3 · Connecting Chirp with Phosra Link

The parent clicks Connect Chirp for Maya. Everything in the dialog and popup is drawn by the Phosra SDKs, not by Guardian or Chirp.

Review the requested controls
Sign in to Chirp in a popup
Choose which Chirp profile is Maya
Chirp applies the rule and returns a signed receipt

Phosra Link consent dialog — **06Consent screen Phosra Link**Plain-language list of what will be requested: content rated for ages 13 and under. Nothing is granted by default.

08Choose Maya's profile Phosra LinkChirp lists only the account's child profiles. Phosra gets an opaque reference, never a name or birthday.

Platform reports controls active — **09Signed confirmation Phosra Link**Chirp applied the rule, read it back, and signed an `applied` receipt.

Guardian shows Active — **10Connection active Guardian**Maya: “Active · Chirp confirmed (signed)”. Status comes from the Link SDK's verified snapshot, not from the browser.

4 · The restriction in effect

Same site, same account, a few seconds later. Only Maya's profile changes.

Maya before12 postsratings 0 · 7 · 13 · 16 · 18

Maya after8 postsratings 0 · 7 · 13 only, plus a notice

Dana (parent)12 postsunchanged

Maya before — **03Maya, before Chirp**18+ red-band trailer, 16+ comedy clip, 16+ thriller marathon, and more.

Maya after — **11Maya, after Worker**“Managed with Phosra” notice; every 16+ and 18+ post is gone.

Dana unrestricted — **12Dana, unrestricted Chirp**The parent's own profile still sees 18+ and 16+ posts; the rule is per child.

5 · How the Cloudflare Worker does it (option 1)

In edge mode Chirp has no Phosra code. The Worker hosts Gatekeeper at /api/phosra/*, records what it enforces, and filters Chirp's responses with HTMLRewriter.

No Phosra code in the siteNo SDK, Phosra tables, background process or Phosra secret on Chirp's servers. Chirp only exposes who is signed in and each post's rating.
One integration, many sitesEverything site-specific is configuration; protocol, signing, retries and receipts are written once.
Upgrades without the siteNew Gatekeeper versions, credential rotation and new rule categories ship as a Worker deploy.
One gate in front of everythingIn production the origin accepts traffic only from the Worker, so every response a child receives is checked.

Want Chirp to enforce the rule in its own queries, with the Worker still owning everything Phosra? That is option 2.

Through the Worker — **11Maya through the Worker :3011 Worker**8 posts, notice says “Enforced at the edge by a Cloudflare Worker”.

Origin direct — **13Same session, origin directly :4011 origin**The unmodified site still serves all 12 posts. Left open only so this demo can show the difference: in production the origin is reachable only through the Worker (Cloudflare Tunnel, mTLS origin pulls or Access), so this bypass does not exist.

Filtered JSON feed — **14The JSON feed is filtered too Worker**`GET /api/timeline` as Maya: only ratings ≤ 13, with an `x-phosra-edge: content_rating<=13` header.

Phosra status — **15Gatekeeper status from the Worker Worker**`PLATFORM_READY`: credential, signing key, Trust List standing and database all verified at the edge.

6 · Native mode: the same rule, built into Chirp

With npm run demo:native, Chirp runs Gatekeeper itself (chirp/src/phosra.ts) and filters in its timeline query. Same parent flow, same result, plus Chirp can show the control in its own UI.

16Managed profile badge Chirp nativeMaya's profile card shows “🛡 Up to 13+”, read from the control Chirp applied.