Skip to content

Where things live

Repositories

Repo What's in it
relay-platform (christensen-digital/relay-platform) Backend API, MCP server, and data layer. All platform issues, MCP tool specs, and server-side work lives here.
relay-app (christensen-digital/relay-app) The product frontend — app, console, and user-facing surfaces. relay-app.css is the token source of truth for the app.
relay-creative (christensen-digital/relay-creative) Working layer for all creative — brand, copy, decks, email, social, briefs, _vocab, and the HTML prototypes.
relay-kb (christensen-digital/relay-kb) This KB — MkDocs + Material, themed to v3.4.

Inside relay-creative

Folder Contents
brand/ Design system, tokens, brand guide, logo/favicon
copy/ Positioning, website copy, one-pager
briefs/ Design & campaign briefs, SPEC files
_vocab/ Voice & vocabulary (_VOCAB.md)
decks/ email/ social/ Presentations, email templates, social
_archive/ Superseded materials

Final deliverables move to Google Drive — relay-creative is the working layer, not the archive of record.

Document surface boundaries

Three planning/reference surfaces exist — each has a distinct job and things should not bleed across them.

Surface What goes here What doesn't
relay-kb (this KB) Canon, vocabulary, how work ships, MCP tool reference, team orientation Sprint plans, board materials, product specs
relay-board (Figma product board) Streams, objects, sprint planning, design work Writing, reference docs, canon
Master Plan (Google Drive) Strategic direction, financial model, pitch materials Day-to-day reference, team KB

Board ≠ docs

Materials created for the relay-board (Figma product board) do not go in relay-kb. The board is a planning surface; this KB is a reference surface. If it changes every sprint, it's board material — not KB content.

Reference pages in this KB

  • MCP tools — the agent-facing tool surface: directory-default (host profile) vs connection-gated, relay_search vs relay_lookup, vocabulary, and known residue.

Working product specs (not in this KB)

Per the boundary above, evolving product specs stay in their working layers — this is just the map:

  • Orchestrate / choreographer, context-weight score, and the session-handoff package specs live in the Master Plan product/ working layer (Director workspace) and, where implemented, in relay-platform docs/.
  • They're working/board material — referenced here, never copied in.

Served by Cloudflare Pages from the prototype branch of relay-creative as pure static files (no build step). index.html is the gallery index; _redirects (Cloudflare-native) maps clean URLs to versioned files.

  • Maintenance: relay-creative/MAINTENANCE.md — URL conventions, when a prototype ships, section rules, archive handling.
  • URL conventions: current pages get clean URLs (/web/app); archived pages are version-suffixed (/web/app-v34); explorations are namespaced (/web/explore/minimal).

Shared working directory

The local relay-creative checkout is sometimes shared between people/agents. It commonly sits on the prototype branch with uncommitted work in flight — check git status and git branch before you start, and don't switch branches out from under someone.

Sites & domains

Surface Where
relayctx.com Public marketing site. IBM Plex Sans font (marketing only).
prototype.relayctx.com Internal prototype gallery (above).
kb.relayctx.com This KB (gated).

This KB

Built from relay-kb by its own Cloudflare Pages project — fully decoupled from the prototype deploy. Source in docs-src/, build with mkdocs build → site/. See the repo README for the exact Cloudflare settings.