Every product surface, clickable.

Not a shrunk phone: three faces only (Glance, Act, Capture), no keyboard, no Search, no You. Digital-crown-first approve, voice-only capture, undo-on-deny by a second tap. Companion to Mobile V2, unscheduled.

Relay as a native Slack app, not a dashboard link-out: inline approve/deny on real messages, /relay capture, forwarded-message and reaction capture, resurfacing that lands where the team already looks. Reuses the MCP response-card component inside Slack's own attachment chrome.

The agent's own chat window as the surface — no separate Relay UI. A full claim → load → capture → pending-approvals transcript rendered with the exact MCP response-card component, switchable across Claude / ChatGPT / Cursor-style chrome to show the card travels unchanged.

Relay's own first-party conversational surface, not cards rendered by someone else's chat client. Same morning-brief → capture → claim loop as the Chat concept, but with fully designed app cards (working approve/deny) instead of a raw tool-call block, and it can approve a connection request directly, which the Chat concept's guest agents deliberately can't.

Chat with your agent, land on a prompt and settings, relay_send it, then pull the Code straight into a ComfyUI workflow. A working prototype, not a mockup: Relay In + typed Relay Field nodes parse a tagged-on ```relay-fields JSON block off the relay's markdown content — zero backend changes needed. Getting generated images back out is explicitly parked pending binary/object relay support.

Display direction for DEC-025 lazy mint: a Code exists only where someone deliberately handed context over, so most objects have none. Four laws (mark presence never absence · one teal moment per object · the title never changes rank · absence is addressable not annotated), relay detail in both states with an annotation overlay, the mint moment as a live event, a mixed list with a circulation filter, and the four rejected drafts drawn so they are not re-proposed. Brief: BRIEF.code-presence.md. Ratifying it unblocks the relay-app REFERENCE rewrite that gates Train 3.

The member-facing half of the billing lifecycle, on the shipped rail (Billing under Account): plan and seats, usage against the plan contract, invoices and receipts, payment method. Built around the three states the platform actually resolves — active, past_due (retrying, full access retained), unpaid (dunning exhausted, effective tier drops to the Free contract). Switch state and the usage ceilings move to Free with over-limit treatment, the alert band offers the hosted invoice, the document row flips to Pay invoice; nothing is deleted and billing stays reachable throughout. Reactivation is webhook-confirmed, never client-claimed. Deep-linkable: ?state=retrying / ?state=paused. Operator counterpart: Console — Finance lifecycle.

Clickable prototype for SPEC-address-custody-v1 with the rulings applied: strict scoping (contract-consistent views), per-membership contact-address mapping, the claim simulator with governance fallbacks, the org-tagged bell with guided switching, one-tap Home, and Pass → between joined workspaces with the per-object timeline carrying provenance across the wall — data crosses org walls only as a relay. Opens the in-shell version (real sidebar/topbar chrome); the standalone walkthrough lives beside it in the area index.

Board-level surface, tier-1/finance gated. Instruments the four milestone-gated tranches (T1 Protect → T2 Sustain → T3 Team, the round floor → T4 Scale) instead of rendering a wall of zeros. Every figure carries a provenance chip (source + as-of) across five source states — live, manual, stale, not instrumented, not computable — so measured-zero and never-wired can't be confused. Roadmap is one source, two renders: board view keeps dates, the investor render drops them at render time and reports its withheld-row count. A fourth screen adds the one column the Investor track screen doesn't carry — onboarding enrollment — because activation rate is a T4 gate signal and an investor enrolled in First Relay sits in its denominator; register, compliance and audit stay owned there. Concept only; no build until the canonical source is settled and approved.

Error statuses in the shell: tier chips (critical/warning active counts, pulsing dot on critical) on every screen + a bell with the per-admin unseen count and notification panel — fed by platform_alerts (categories incl. the new client + public from the error-triage pipeline). Interactive: fire client/boot/public spikes and watch the shell escalate; mark-seen (per-admin cursor) vs resolve (global) modeled as the backend does it.

Tier-1 operator surface for the investor lens, inside the operator shell: register with opaque pack IDs (never a name or firm in a URL), NDA version + ToS acceptance, compliance flagging access without a current signature, and grant/revoke audit where revoke names the Cloudflare Access step it does not reach. The Lens & gate tab carries the argument: EAPA can't be made optional in the gate component, because the gate only renders what /api/legal/pending returns — skipping it client-side leaves gate_needed() true at seven server call sites and traps the user with nothing to sign. Proposes applicability as a third axis beside version and enforcement mode. Draft — awaiting approval, nothing built. Spec: relay-platform docs/SPEC.investor-track.md.

Parallel v3.5 console build focused on the Finance group: commitment lifecycle (5 states, committed-vs-realized $), seat↔member true-up with the 402 confirm, trials with discount-at-conversion, Seats & Segments (free / EAP-open / EAP-grace / paid-full / paid-discounted cost-vs-revenue split, margin flips to net burn when only unpaid segments are selected, sortable + CSV export), P4/P5 stubs. Mirrors the membership-billing lifecycle shipped to relay-platform. New: the Gateway panel — connection health and console-managed config, built adapter-shaped so a Launchpad product on another processor inherits it. Three scenarios, all real failure modes: healthy, webhooks stale (six days of silence against 41 live subscriptions — the one check that catches an outage rather than a misconfiguration, and it reads processor_events, not the API), and test key in prod. Secrets are reported present-or-not, never shown or editable. Deep-linkable: ?gw=stale / ?gw=testkey.

The internal, team-facing onboarding component — distinct from the app's own user-onboarding line above. Dashed mono eyebrow, italic accent headline, flat cards, step checklist. Shown here with placeholder data; real per-person instances are gated on resources.relayctx.com/onboarding/<person>. First built for the initial brand & product hire.

The organizing layer at 390px, designed at 390 rather than collapsed to it: lens and library segments at the top, shelf list with visible predicates, rows with origin markers and unread dots, and everything secondary in bottom sheets — filters, view-as, and the object sheet answering why you can see it (attribution basis: self / custody / grant) and why it is on this shelf (matched vs added) with the properties that decide it. Primary actions at the thumb; counts read “N you can see”. Console governance sibling: console-v35/org-ia.html.

The multi-hat framing made touchable. A working week’s context laid out once — 20 objects across four hats (employer, two clients, personal) — where positions never move: switching a hat seals or unseals, switching a lens emphasises or recedes. The demonstration is that zero edges cross a hat boundary, asserted in the data and shown in the readout, so separation is structural rather than a read-time filter. “Reveal what’s sealed” distinguishes what the owner can see from what an agent in that hat can. Argues hats are walls and lenses are windows, states what “ties it all together” is allowed to mean, and answers the single-point-of-trust objection with the zero-knowledge posture. Companion to relay-board/docs/strategy/framing-substrate-vs-transport.md.

The 2026-08-10 direction calls landed in the app shell: Files is a rail section, not a Catalog tab — it sits directly after Overview (recommended placement, not final) and owns the content area, drawing its own tree beside the rail. The old SHELVES/LIBRARIES rail groups are gone, and the group that mislabelled the four lenses “Shelves” now reads Lenses, inside Files where it belongs. The files-v3.html GitHub shell carried across whole: library selector where the branch picker sits, “Go to file” + T as the search spine, a shelf tree that proves depth 3 (Auth & identity › On mobile › Warm), Last change as a supersession note, History with envelope diffs, and Edit that names the next version before you type. The cross-type Objects table moved in from Catalog as “All objects” — same table, every row and count per-viewer now. Runs on the catalog-shelves seeded corpus and grants, so the two prototypes describe the same workspace. Deep links: ?as · ?lib · ?shelf · ?obj&view=history · ?view=all · ?q.

v1 drew Drive folders; v2 proved the set model but as a four-pane inspector — right semantics, lost shell. v3 is the shell the brief asked for: library selector where the branch picker sits, “Go to file” + T as the search spine, a shelf tree, and a listing whose second column is Last change — a supersession, not a commit. History opens the version chain; a click diffs two versions under an envelope header. Deliberately not GitHub: colour never carries type, no lock/shield glyphs, no export affordance. The set model survives intact — predicate under the breadcrumb, added chips, curator-only excluded rows, every count post-filter — and Edit on a claimed object names the version first: “claimed by 2 people. Editing creates v7.” Folded into the app as app-v35/files.html. Deep links: ?as=sam · ?lib=me · ?shelf=decisions · ?obj=o1&view=history · ?q=acme.

Where v1 drew folders — a place an object sits in — this draws libraries and shelves: sets an object belongs to, populated by a rule, augmented by hand, and filtered per viewer. Adds the four things v1 had no slot for: a library rail putting personal and org IA side by side; lens separation (Catalog and Workspace live, Graph and Journey greyed); membership origin, so rule-matched, hand-added and excluded are always legible; and a "view as" switch that changes the same org shelf between Owner, Member and Viewer — the projection made visible. Every count is post-filter. Foundation plan: relay-board/docs/product/organizing-layer.md.

Drive-shaped folders for relay objects, not Windows directories — the third projection of the corpus alongside List (search) and Graph (Context Map). Folders are loose, shallow buckets an object lives in one of; search sits inside the view as the spine, scoped to the current folder with a visible widen; labels cut across folders; a large share of the fixture corpus is deliberately unfiled, with no counts or nags on it. "Shared with me" holds received relays as a peer of the tree. Shows the integrity moment (editing claimed context supersedes, never mutates) and a Git-familiar unified diff across a version chain. Brief: BRIEF.cloud-files.md.

The v3.6 refinement aligned to what shipped in relay-app (claude/context-map-graph-view-xh81fx): the persistent rail's feed rows tint when they touch the selection, the type chips and new status chips (Open/Received/Locked, pre-filter counts) really filter the canvas, and the control strip carries the Views menu with the default star (RCTX-592) — a bare Graph open lands on the starred view, explicit links always win.

Merges v2 + v2-1 + v2-2: density regimes at 40/400/5k objects, size-by-degree, label LOD + collision, workspace gravity, stream capsules, ego-focus, Arrange lenses (Force/Time/Orbit/Heat) with a list-twin per lens. Vanilla JS, self-contained like v1. Ported from the frozen prototype branch (PR #185, relay KTVANV) — not yet ratified against v1, see MEMORY.md.

From v2-3: the journey view (handoff moment, Owner lens) plus remaining edge cases — 3+ hop truncation, tombstone mid-chain, revoked upstream, re-homing, personal→org promotion, same-object dedupe. Ported from the frozen prototype branch (PR #185, relay KTVANV).

Motion on the gc-* grammar: one live SVG canvas with arrange-lens morphs (Force/Time/Orbit/Owner), node arrival with a #00D9C8 ring, edge draw settling to the law dash arrays, focus dim, hot breathe, journey seam glint. Ported from the frozen prototype branch (relay FMZRNG).

The shell laws as a working prototype at full scale: one document that folds from the 220↔56px desktop rail to an off-canvas drawer at ≤860px — same groups, same stripe, no bottom tabs. Real Transfers list with DEC-025 cards (Code as head and the one teal moment; head closes up when unshared), a two-row control budget with everything else in a transform-only filter sheet, and a console twin sharing the same CSS where dense tables become cards on a phone. Reference implementation for the component-kit brief.

The universal rail (brand-mark collapse, active stripe, shipped group structure), app/console/mobile temperaments with a working drawer demo, the @relay/ui primitives inventory, and the seven shell laws. Ported from the frozen prototype branch (relay FMZRNG).

Every surface served without a session — error pages, maintenance, link-expiry, claim gates — as one category on one chrome: the public .shell (mark → status strip → headline → body → actions → support ref) with a live state switcher and the /api/frontend-error triage beacon (category public, PB-… refs). New public-bound views start here.