RelayCTX
Naming Exploration · 2026-07-22
Brand Identity · Contingency Exercise
Exploratory · RelayCTX is not renaming

If the name ever had to move, where would it go?

Not a rebrand in progress — a scouted contingency. This is the track the exploration ran: why look at all, where the obvious move (the relay-race baton) turns out to be a dead end, and what's left standing after that. Full detail in the source briefs, linked at the bottom.

Position 01

Starting line: RelayCTX.

The name, the verb ("relay a Code"), and the locked vocabulary system are all live and unchanged. Any alternative has to read as an evolution of this — not a detour to something unrelated.

Position 02

Why look at all — track pressure.

Two independent pressures, both real, neither an emergency.

6 products
named some variant of "Relay" in or adjacent to the AI space — 2 rated HIGH collision risk. See Competitive Landscape.
3 live products
already use "Baton" specifically in AI-agent tooling — the exact category RelayCTX competes in, surfaced this pass.
Position 03

The exchange zones.

Four directions scouted, each a different distance from the current name.

A

Relay-race vocabulary

One level more specific than "baton" — the exchange itself, not the object.

CHANGEOVEREXCHANGE ZONELEADOFF
B

Evolve "Relay" itself

Lowest-disruption path — keeps the verb, the vocab system, most of the brand intact.

RELAISRELAY LOOPGETRELAY
C

Continuity, softer than a race

Trades the sport image for the underlying promise — nothing gets dropped.

THROUGHLINECARRYOVERTHREADLINE
D

Passing / carrying, non-race

Carries something across a gap, on schedule, reliably — verbs naturally.

FERRY
×
Position 04

Baton — disqualified.

The obvious literal move. Checked first because the instinct is sound — the baton metaphor is already latent in the product. It doesn't survive contact with the category.

4 live collisions found
Baton AI · getbaton.ai
Context-extraction automation for SaaS onboarding — nearest hit
Baton · getbaton.dev
AI coding-agent orchestration
BatonAI · trybaton.ai
Natural-language software agents
Baton Systems
Post-trade fintech, funded since 2016

"Built for B2B SaaS companies looking to scale pre-sales efficiency… eliminate tedious manual data entry during customer handoffs."

— Baton AI's own positioning. Not a product competitor to Relay — but that's Relay's vocabulary, not just its name.
Position 05

What's left standing.

First-pass web checks only — no formal trademark or domain search yet. Displayed the way a real Code would be, because that's the honest status: nothing here is claimed.

Priority 01
Changeover
Needs clearance

The literal track & field term for the baton exchange. Verbs cleanly, no category collision found.

Priority 02
Ferry
Needs clearance

Strong verb ("ferry your context over"), no AI-tooling collision found — domain is the likely hard part.

Priority 03
Relais
Needs clearance

French for relay — cheapest emotional migration. Soft trademark neighbors to check (hospitality, healthcare).

×
Position 06

The trust field — scouted, and closed.

Continuity and trust are the two load-bearing brand ideas — so the trust wordfield was scouted as its own cluster. It's the most colonized space checked so far: "trust" is what every identity, custody, and governance company claims.

8 candidates checked — all closed
STEWARD
4+ live AI products, one doing agent memory across sessions
CUSTODIAN
An entire fintech/crypto-custody category
PROVENANCE
Taken twice — and already Relay's own feature term
VOUCH
Twice: agent identity verification + startup insurance
LINEAGE
An entire data-lineage tooling category
KEEPSAKE
Three products incl. Replicate's ML versioning library
TRUST
OneTrust/TrustArc/Trustwave already own it; Cyera ($12B) now brands itself literally "the trust layer"
TRANSPARENCY
Transparency International's global brand equity makes it a dilution risk on sight

Trust is the kind of claim that has to be demonstrated, not asserted. A company named "Trust-something" asserts it. A company whose name says continuity and whose product proves custody — encryption, residency, audit, receipts — demonstrates it.

— The synthesis: name from the continuity field, position on trust. It's why the shortlist held: Changeover, Ferry, Relais are all continuity names — and why checking the bare words themselves (added 2026-07-30) only confirmed it harder.
Position 07

Continuity as promise, trust as proof.

Working positioning lines in the two-beat register the brand can own — short declarative promise, short declarative proof. Name-independent: they work under RelayCTX today or any shortlist name later.

P

The promise — continuity

Context that survives the handoff.
Nothing gets dropped between sessions.

T

The proof — trust

Continuity you can prove.
Every hop on the record.

"Context moves. Custody holds."

— Strongest of the pass: four words, both pillars, verbs both times, no adjectives.
Position 08

The riff field — seeded for a creative director.

Divergence on purpose: raw metaphor material so the eventual CD engagement starts from a stocked field, not a blank page. Every entry passes one test — does it say continuity that can be trusted? Spot-checked where marked; the CD pass re-verifies anything it loves.

The split token

The pre-modern answer to Relay's exact problem: objects broken in two, rejoined to verify. Symbolon is the root of the word "symbol" — a Code, 2,500 years early.

SYMBOLON ○TESSERA ◐COUNTERSIGN ?

The rope & the trail

Climbing's spoken trust ritual — "On belay?" "Belay on." — and the stones stacked so the next traveler finds the route.

BELAY ◐CAIRN ◐

The score & the stage

Attacca: the composer's "proceed without pause" — a session handoff in one word, and the strongest open name found. The understudy steps in mid-run; the audience never feels the seam.

ATTACCA ○UNDERSTUDY ○MATCHCUT ◐ADJOURN ○?

The route & the loom

Relay history beyond the racetrack — dispatch riders, fresh horses at the post, the portage between waters — and the thread the shuttle carries across the warp.

ESTAFETTE ◐REMOUNT ○?PORTAGE ◐WEFT ◐SELVEDGE ○

The drawn line — dots & weave

The only field that isn't imported: Relay's graph literally connects dots — first contact creates the edge, and Codes are the numbers on them. The big names are closed (Weave is W&B's agent-observability tool; Constellation is a Canadian giant) — so this field pays off as visual system and language, not a name. The dots exist. Relay draws the lines.

STRAND ○?BRAID ◐INTERLACE ◐SEURAT ◐WEAVE ✕CONSTELLATION ✕

Coined names and compounds are deliberately left unexplored — that's the naming specialist's craft, and the field is stocked for them.

— ○ open · ◐ neighbors · ? unchecked — full annotated field in BRIEF.name-alternatives.md v0.3
Position 09

What actually depends on the name.

The applied brand-identity audit's answer: the visual system is well-insulated already — the real cost of any rename lives in the verbal layer.

✓ Name-independent

  • Open Signal mark — abstract radial burst, doesn't depict "relay"
  • Token system — dual-value teal, type scale, shape
  • Vocabulary structure — Code / receive / Stream as concepts

✕ Name-coupled

  • The wordmark — every lockup file
  • The verb "relay" — load-bearing across UI, MCP, marketing
  • "Code" as a term — orphaned if its verb pairing changes
  • --rly-* / relay_* — cheap but real find-and-replace