# GUIDE — Social Accounts

**Status:** law — v1, 2026-08-28
**Applies to:** every profile Relay holds on an external platform — X, LinkedIn, GitHub,
Bluesky, Instagram, YouTube, product directories — and every post published from one
**Parent:** [`GUIDE.voice.md`](GUIDE.voice.md) — the voice law applies wholesale here;
this file only adds what a profile surface needs on top
**Vocabulary canon:** [`../_vocab/_VOCAB.md`](../_vocab/_VOCAB.md)

A profile is the one surface where the whole brand has to survive in a name field, an avatar,
one line, and 160 characters — written once and then read for months. This file locks that
material so no account drifts on its own.

---

## The brand line

> **Context that moves.**

**Adopted by EC, 2026-08-28** — resolving the brand-line question open in the Relay Creative
stream since 2026-06-03 (item `DFF139`). Why this line holds where the candidates fell:

- **It is the canon, compressed.** `_VOCAB.md`'s memory framing is *"stores context so it can
  move — intentionally, on demand."* The line is that sentence at three words. Nothing to
  reconcile, ever.
- **It passes the v0.16 rubric** (*a thing that keeps going, the same thing on both sides of an
  interruption*). Present tense, ongoing. *"Context, carried."* fails it the way Changeover,
  Passit, and Ferry fell in the naming brief — a past participle names the completed pass, not
  the thing that keeps going. **Retired as a candidate.**
- **It stands alone.** Ada's `DFF139` finding was that the cover line needs setup. This one
  doesn't — no antecedent, no second beat required.
- **It contains no product name.** It survives the naming contingency
  (`../brand/BRIEF.name-alternatives.md`) unchanged.

Also retired: *"When you need it. Where you need it."* — an availability claim with no
mechanism in it; either half is true of any memory product.

### Setting the line

- Always exactly **`Context that moves.`** — sentence case, terminal period. It is a sentence.
- Never extended into a two-beat (*"Context that moves. When you need it."* adds availability,
  not a turn), never merged into a longer sentence, never hashtagged, never an exclamation.
- **One appearance per surface.** In a bio it is the close. In a post it is a signature used
  sparingly, not a stamp on every post.

### The line vs. the cover line — both live, different surfaces

`DFF139`'s tension resolves as a split, not a winner:

| Surface kind | Carries | Why |
|---|---|---|
| **Standalone** — bios, taglines, directory one-liners, boilerplate | **Context that moves.** | Must work with zero setup |
| **Cover** — banners, deck covers, pinned-image headlines | *The session ends. The context shouldn't.* | A cover has a reader mid-scroll; the two-beat earns its turn there |

Never both on the same surface — the two-beat budget in [`GUIDE.voice.md`](GUIDE.voice.md) is
one per surface, and the line counts as the display moment in a bio.

---

## Identity block

| Field | Value | Notes |
|---|---|---|
| Display name | **RelayCTX** | The registrable brand form. "Relay" alone is unownable in a name field; prose inside posts says Relay |
| Handle | **@relayctx** | Everywhere. If taken on a platform: `@relayctxcom` (domain echo). Never underscores, suffixed years, or per-platform variants |
| Avatar | Open Signal mark on an app-icon tile — `../brand/app-icon-teal.svg` / `app-icon-light.svg` | Platforms can't theme, so the tile carries the contrast the `currentColor` rule normally handles. Never the wordmark as an avatar |
| Banner | Neutral surface (ink `#111111` dark tile or true-neutral light), wordmark in Outfit 600, cover line in Cormorant Garamond | A cover surface — it carries the two-beat, per the split above. Teal as touch point only |
| Link | `https://relayctx.com` | The link field is the CTA; bios don't repeat the URL |
| Company / about fields | Relay Context Inc. | Legal name only where the field asks for one. Location where offered: Ontario, Canada |

---

## Bio copy — locked tiers

Defaults are law; alternates are the approved rotation. Anything else is new copy and clears
[`GUIDE.voice.md`](GUIDE.voice.md) + `check_vocab.py` before it ships.

| Tier | Fits | Copy | Chars |
|---|---|---|---|
| **Line only** | any single short field | Context that moves. | 19 |
| **One-liner** | ≤60 · directory taglines, LinkedIn tagline | The context layer for AI. Context that moves. | 45 |
| **Standard bio** | ≤160 · X, Bluesky, Instagram | Package the substance of where you are, relay it with a short Code, resume anywhere. You own what travels. Context that moves. | 126 |
| **Dev bio** | ≤160 · GitHub org | The context layer for AI. Package working context, relay it across sessions, tools, and agents. MCP-native. Context that moves. | 127 |

**Approved alternate (standard bio, two-beat build)** — only where the banner doesn't already
run the two-beat:

> The session ends. The context shouldn't. Package it, relay it with a Code, resume anywhere.
> You own what travels. Context that moves.

**About / description fields — two modes, gated on the stealth period:**

*Stealth (current — while relayctx.com is the stealth page).* One sentence, and it's done
(EC, 2026-08-28). ™ rides the first use of the wordmark, per the brand brief (first-use only).
The brand line is **not** repeated here — the tagline field above it already carries it, and
the line appears once per profile:

> RelayCTX™ is the context layer for AI.

Where a platform demands more than one sentence, the approved extended stealth:

> RelayCTX™ is the context layer for AI. We're in early access, working with a small group of
> teams and operators. If we've already talked, you've seen more than this page — an invite
> code fast-tracks your request. Relay Context Inc., Ontario. Get access at relayctx.com.

*Full (activates when the marketing site replaces the stealth page):*

> Relay is the context layer for AI. You package the substance of where you are — decisions,
> state, intent — and relay it with a short Code. A new session, a different tool, a teammate,
> an agent: work resumes where it left off. Context is stored so it can move — on demand, and
> you own it. Built by Relay Context Inc. Get access at relayctx.com.

**Boilerplate** (press, directories, app-store "about the developer"):

> Relay Context Inc. builds RelayCTX, the context layer for AI — infrastructure for portable,
> user-owned context that moves between sessions, tools, agents, and people via short Codes.
> Receiving is always free, export is always free, and your context is never hostage.

The closing commitments are the ratified public set (`pricing-commitments`, 2026-08-13) — they
ship verbatim or not at all.

**Personal profiles** (founder, team): own text first, the line last, same setting rules.

> Building RelayCTX. Context that moves.

---

## Posts

Marketing register per [`GUIDE.voice.md`](GUIDE.voice.md): headline + one or two sentences, one
display moment, mechanism first, close on the action. On top of the voice law:

- **CTAs:** `relay it →` · `Join Relay →` · `Get access →`. The Loop is the reward revealed
  after the action, never the ask.
- **Codes in posts:** set in code formatting where the platform allows. Never state a length.
  The Code is the seal, not the package — a post whose hero is the Code is selling the envelope.
- **The pinned post is the product.** Pin a post carrying a live broadcast Code (unlimited
  receives) so the profile itself demonstrates the pipe: read it, relay it in, you've used
  Relay. Verify the Code is still live before pinning; replace the post, don't edit it, when
  the Code rotates.
- **No announcement theatre.** Not "We're excited to announce" — state the mechanism and the
  date it ships. No hashtags as house style; the line is never one. No emoji in copy, no
  exclamation marks, no thread theatre.
- **Capability posts clear the feature index.** Nothing Built · dormant is posted as live
  (Teams, A2A, governance claims) — check
  `relay-board/docs/product/feature-index.md` before any "you can now" post.
- **Replies are not a support queue.** Point people at the real channel and stop; the
  define-by-exclusion sentence ("Not a support queue.") already exists for this.

---

## Naming contingency

The line contains no product name, and every bio names the product face exactly once. If the
naming brief (`../brand/BRIEF.name-alternatives.md`) lands a rename, only the **identity
block** changes — handles and display names then follow
`relay-board/rebrand/REFERENCE.rebrand-surface-index.md`. The copy tiers survive as written.

---

## Checklist

- [ ] Display name **RelayCTX**, handle **@relayctx** (or the one named fallback)
- [ ] Bio is a locked tier or has cleared voice law + `check_vocab.py`
- [ ] The line appears once, exactly as `Context that moves.`, as the close
- [ ] Banner (cover) and bio (standalone) don't both run the two-beat
- [ ] About runs the mode matching the stealth period (stealth now; full when the site flips)
- [ ] Link field carries the URL; legal name only in fields that ask
- [ ] Pinned Code verified live
- [ ] No Built · dormant capability posted as live