RelayCTX Marketing kit · stub
Stub · Draft

This is a skeleton, not copy. Every dashed box is a slot for product and marketing to fill. Lines marked placeholder are starting points, not proposals of record. Nothing here goes on a public surface until its claims clear copy/CATALOG.claims.md and the copy has had its voice pass. The product source is the PRD; where this page and the PRD disagree, the PRD wins.

Marketing kit · Relay for Chrome · v1 stub

Relay for Chrome, the launch kit.

A first-party Chrome extension that tells you when a relay arrives or needs you, without the app open. It launches with a toolbar count and desktop notifications, and nothing else. Everything below is the frame the launch copy fills in.

01 · Positioning

One line, then four jobs.

The MVP job is Aware. Act, Capture and Carry are later phases. They can appear in a roadmap line, but never in copy that reads as available today.

Positioning line · placeholder Know when a relay needs you, from any tab. Alternates to test: “Relay, in your toolbar.” · “Never miss a relay that’s waiting on you.” Pick one after the name ruling (D3).
Supporting sentence · placeholder Most AI work happens in a browser tab. Relay for Chrome sits beside it and tells you when a relay arrives or is waiting on you, so you don’t have to keep the app open. From PRD §1. The “addressed but not informed” gap is the reason this exists; say what it fixes, not how it polls.

Aware MVP · launch

A count on the toolbar icon and a desktop notification when something needs you: a relay received, a request to approve. Click it and the right page opens in Relay.

PRD §5 (P1). Read-only: every action still happens in the app.

Act Coming · P2

Placeholder. Approve or deny a request, snooze, or mark read from the notification or the popup, without opening Relay.

PRD §7 (RCTX-1433). Deferred.

Capture Coming · P3

Placeholder. Right-click to send a selection, page or link to Relay; save the current tab to a Stream or the library.

PRD §2. Needs optional per-site permissions (D4).

Carry Coming · P3

Placeholder. Relay any AI web chat, even where MCP isn’t available, and paste a Code into any chat to pick the context back up.

PRD §2, the strategic phase. Needs optional per-site permissions (D4).
02 · Chrome Web Store listing

The listing, field by field.

Unlisted first, for EAP, then public (PRD §5.7, §8). Draft against the store’s current field limits before submitting; the 132-character summary limit is the one that bites.

Name · working Relay for Chrome Working name from the PRD, published under relayctx. Not final until D3 is ruled. Also check the store’s branding rules for “for Chrome” naming before submitting.
Summary · placeholder · 122 / 132 characters Desktop notifications and a toolbar count for Relay. Know when a relay arrives or needs you, without keeping the app open. Recount after any edit. Describe the MVP only.
Description · skeleton Paragraph 1: what it is. [TODO: one or two sentences: the extension, who it’s for (people already using Relay), the one job it does.]

Paragraph 2: what you get. [TODO: toolbar count, desktop notifications for what needs you, the popup with the latest items, one click to open the item in Relay.]

Paragraph 3: what it asks for. [TODO: permissions in plain words: notifications, local storage, a once-a-minute check, and access to app.relayctx.com only. No separate sign-in: it uses the Relay sign-in already in the browser. No access to the sites you visit.]

Paragraph 4: what’s next. [TODO, optional: a single roadmap line for Act / Capture / Carry, clearly labelled as coming.]

Requirement line. [TODO: needs a Relay account; plan eligibility to be confirmed.] No numbers (poll intervals, timings, counts) unless they’re cleared in the claims ledger. “Instant” is not true until Web Push replaces polling (P1b, RCTX-1431).
Category · language · support URL · privacy URL [TODO] · English · [TODO: relay-support page] · [TODO: privacy policy URL] Support stub: relay-support docs/browser-extension.md (PRD §8).
Privacy-practices disclosure · skeleton Handles: notification titles and item metadata from the user’s own Relay account. Stores: no sign-in tokens (it uses the existing Relay session in the browser and can neither read nor copy it); only the ids of notifications already shown, locally, per browser profile, not synced. Sent anywhere else: [TODO: confirm none]. Sold or used for ads: [TODO: confirm no]. From PRD §8 and D5. Legal to confirm the wording before submission (open question 02).
03 · Asset shot-list

What to shoot, and at what size.

Sizes are the store’s standard slots; confirm them against the current store documentation before export. Use the v3.6 token set, a seeded demo account and fictional Codes only, with no real names, emails or organisations in any shot.

AssetSizeWhat it showsStatus
Icon128 × 128The Open Signal mark, legible at the toolbar’s small size. Needs a badge-state variant for store art only.TODO
Screenshot 11280 × 800A browser with an AI chat open, the toolbar badge showing a count, the popup open over it: the latest items with priority dots.TODO
Screenshot 21280 × 800A desktop notification: a relay received, with one line of context.TODO
Screenshot 31280 × 800A request waiting on you: the notification, then the Relay page it opens.TODO
Screenshot 41280 × 800Signed-out popup: “sign in to Relay in this browser”, one button that opens Relay. No separate sign-in.TODO
Screenshot 51280 × 800[Optional] Light and dark side by side, or the permissions summary.TODO
Small promo tile440 × 280Mark, name, positioning line. No screenshots inside the tile.TODO
Marquee tile1400 × 560[Optional, only if featured] Same system as the small tile.Later

Screens must show the MVP only: no Approve/Deny buttons, no right-click menu, no chat-page UI. Every state a shot can show, with its real copy, is drawn in the as-built surface record.

04 · Launch channels

Where it gets announced.

Order follows the listing: unlisted to EAP first, public later. Stealth still holds, so nothing public runs until EC declares stealth over.

05 · Open questions

What has to be ruled before this ships.

  1. Name and listing owner (D3). PRD recommendation: Relay for Chrome, published under relayctx; confirm before listing. Every headline on this page waits on it.
  2. Privacy disclosure. The store’s privacy-practices form and the listing’s privacy URL need final wording: what is handled (notification titles), where tokens live (local extension storage), and revocation on sign-out (D5). Owner: [TODO].
  3. Timing claims. The PRD targets delivery within the polling interval for the MVP, becoming instant after Web Push (P1b). No timing goes in copy until one is cleared in the claims ledger.
  4. Duplicate notifications (D2). If the app tab is open, or mobile push also fires, does the copy need to say which one wins? Probably not at launch; confirm with product.
  5. Edge. The PRD says Edge works as-is. Do we list on the Edge store at launch, or only say it works? [TODO]
  6. Plan eligibility. Every plan, or only some? Needed for the requirement line and the EAP email. [TODO]
06 · Rules for whoever fills it

Four rules.