Skip to content

Process & workflows

How creative and design work moves through the team. Some of this is observed from the repos; gaps are flagged — fill them in as the team confirms.

Brief → spec → ship

Work starts as a brief, hardens into a spec, then ships as prototypes or deliverables.

  • Briefs live in relay-creative/briefs/ (BRIEF.*). They set scope and intent — e.g. BRIEF.design-v34.md.
  • A brief gets promoted to a SPEC (SPEC.*) once locked, with checklist and acceptance criteria — e.g. BRIEF.design-v34 → SPEC.design-v34.
  • Deliverable-specific briefs live with the deliverable (e.g. decks/john/relay-one-pager-brief.md), not in briefs/.

Shipping a prototype

Per relay-creative/MAINTENANCE.md:

  1. Build the file at a versioned path (web/app-v35.html).
  2. Add a card to index.html in the right section (is-new tag).
  3. Update _redirects so the clean URL points to the new version.
  4. When superseded, move the old card to Archive (is-archived) — don't delete old files; they stay at their versioned URL.

Changes land on the prototype branch via PRs (the deploy branch for prototype.relayctx.com).

Relay handoffs (dogfooding)

The team uses RelayCTX itself to pass working context. Handoffs are referenced by Code in briefs and commit messages (e.g. tokens corrected "from 3FBZGE handoff", brand brief "source CAZAZT"). When you pick up handed-off work, note the Code so the trail stays intact.

Pulses

Ongoing workstreams are tracked as Pulses (a persistent focus area + feed of Items). Example: the Voice & Vocabulary Pulse pc_97fd97b78f99. Add Items as work moves rather than restarting context each session.

V&V — Voice & Vocabulary sessions

Vocabulary is locked in numbered sessions and recorded in _vocab/_VOCAB.md, each tied to a Relay Code:

Session Scope Status
0 — Core vocabulary (14 terms) KD8684 ✓ Complete
1 — Product / App UI layer QZWMEB ✓ Complete
2 — Platform & API · 3 — Comms/Email · 4 — Brand/Marketing · 5 — Agent/AI — Pending
6 — Spaces layer — Gated on Spaces v1

All new copy must use the locked vocabulary — see Vocabulary.

Final deliverables

Polished, client-ready output moves to Google Drive. relay-creative is the working layer; Drive is the record.

To confirm with the team

Not yet documented here — fill in when settled:

  • Review/approval gates before something is "shipped" or moved to Drive.
  • Branch & PR conventions (naming, who reviews, merge rules).
  • Cadence (standups, planning) and where decisions get recorded.
  • Tool accounts and access (Figma, Pipedrive, Slack, Cloudflare).