One section per M-ID, carrying its gate, archetype, version and date as data, its face as a 16:9 stage, and its speaker note hidden beside it. scripts/build_deck.py cuts a flow from flows.json out of this file and refuses any cut that lists a slide above its gate. The OPEN family is here in full; the NDA and data-room families are index rows only, because this repo is published — their copy of record is the gated master on the board (relay-board/docs/operations/assets/deck-master-nda.html, the same markup behind Access), which decks/deck.config.json names and the build merges in, one copy of record per M-ID. The whole family, both masters, is the master-full flow.
Find a slide by its M-ID, never by position. Provenance is the caption above each stage and the note inside it; nothing reaches a face. Templates: the archetype library. Law: GUIDE.presentations.md.
OPEN family — the story spine and the Introduction+ set
←→ navigate · N notes · Esc exit
M00R resources · master-only · T16 · stripped from every cut
Resources
Built from git. Cut by script.
Every Relay deck is a cut from these masters: the OPEN family in relay-creative, the gated families on the board. A slide changed here is overwritten on the next build — copy changes go to git first, and the copy deck is generated from it. Find a slide by its M-ID in the speaker notes, never by position.
Portable, collaborative, sovereign context for AI work.
Relay Context Inc. · Introduction · Shared in confidence · 2026
Cover. The mark draws in, then the claim. v3 (2026-09-12): the standfirst is the claim from the ElevateIP positioning — the hook above it, the three words under it; the deck carries the claim from here on. The framing line and date are per-cut variables.
The model does the work. The session ends. The context is gone. Every new tool, every new session, every handoff begins again.
SESSION 01
starts from zero
SESSION 02
starts from zero
SESSION 03
starts from zero
context lost between every session, tool, and handoff
The wall, in sequence: each session lands, then the cross. Do not narrate the mechanism of loss, only its shape. v4: four short sentences in place of two long ones — the body now breaks on full lines, no single word left hanging.
Relay is the context layer for AI — work picks up where it left off.
Portable
Context travels between sessions, tools and agents with its history intact.
Collaborative
A team and its agents work from one live context. Nobody re-briefs anyone.
Sovereign
It stays under its owner's control, not inside one vendor's platform.
A statement slide carries no beat. Let the headline sit, then the three pillars land left to right. v6 (2026-09-22): the 60-word sentence became a one-line claim plus three pillars in the system's own component — the claim is said first and said plainly. Sovereign is the enterprise reason to pay and stays third, where it reads as a property rather than a pitch. v7 (2026-09-23): the register rule — the ruled noun is "the context layer for AI" and it belongs on investor and architect surfaces only; "context infrastructure" was the architect phrasing and is not the front door. Person-facing surfaces take the verb sentence instead ("Relay moves your working context between AI sessions, tools, and people. You own what travels."), and do not revive "context tools for agents", "the platform for context" or "context platform". Canon: relay-board docs/strategy/positioning.md → The Frame Stack → the register rule.
M04 OPEN · v6 · 2026-09-22 · T13 Landscape
Why now
A window, and no standard.
Three things landed at once. The gap between them is the opening.
The pipes AI tools can talk to each other now
The rush memory tools, each for one person
The gap nothing carries context between people
A category is forming — and the standard gets set once.
The window opens: the callout arrives from the right after the body. No IP language at this gate — see M08 v5. If asked "who else?": single-user memory tools exist (onrelay.app, Mem0, AI Context Flow) and the platforms ship their own memory. None moves context between people with consent, receipts and recall, and no standard for that exists. Copies arriving in weeks are the evidence the window is closing, not a threat to hide. Record: relay-board docs/strategy/competitor-onrelay.md. v6 (2026-09-22): the paragraph-beside-a-floating-callout read as jumble; it is now the T13 landscape — three categories land in sequence and the accent band beneath them carries the claim.
M15 OPEN · v1 · 2026-06-09 · T03 Statement with callout product flows only
Where it fits
The layer between the work.
No established player has claimed this space — because the infrastructure to solve it only just arrived. You're not switching away from something. You're adding the part of the stack that hasn't existed before.
A new category – a foundation to build upon.
“The earlier context starts flowing, the richer it gets.”
Product and partner audiences. Not in investor flows.
Package the context of your work, from wherever you're working.
2
Route
Relay carries it under your rules: who can receive it, where it's allowed to go.
3
Receive
It arrives where it's needed and work continues — on the record.
A4K9R2one Code carries it — for a person or an agent alike
Three beats, then the Code. The motif is movement only: never annotate envelope, payload or routing internals. The example Code is example-shaped and implies no length.
M07 OPEN · v5 · 2026-09-23 · T12 Layers · figure: the stack, Relay as foundation
Where it fits
A new layer, not another tool.
The toolsClaude, Cursor, custom agents
Memory toolsstore and retrieve, for one person
Orchestrators & pipelinesmove data, not working context
Agent messaginga name, an address, a sentence
Relaycarries the work itself, between all of them
the layer beneath, not another box beside
Each is valuable. None carries the work itself between them.
“They built the doorbell. The package is still the open problem.”
The layer settles: categories stack, then the resolution. Categories stay generic at this gate. v3 (2026-09-12): the resolution now defines Relay positively — infrastructure beneath the agent platforms, an index across them — and hands the investor the Git scope test; the line they repeat back. v4 (2026-09-22): one 450-character block became three short paragraphs and the “newest of them” sentence was cut — the quote beneath already makes that point. v5 (2026-09-23): the slide claims a layer and drew four flat boxes, so the claim had no picture (EC: "where's it fit into the setup"). It is now T12 Layers — the tools and the four adjacent categories as bands, Relay as the accent-tinted foundation beneath all of them. The foundation tint is the only accent on the slide; nothing else may carry it.
M60 OPEN · v2 · 2026-09-23 · T03 Statement with callout
Why me
I built the layer I needed.
Twenty years making handoffs work between people who don't share a system — five of them running a partnership with a $2.5B Canadian retailer.
AI handed me the same problem at speed. No tool could solve it from the inside, because the loss happens in the gap. So I built the layer that sits there.
I hit that wall first. Anyone putting agents to work hits it next.
The first workload, not the only one.
Founder, told as origin rather than biography. Built 2026-09-22 on EC's call that the deck had no founder slide and that a pure “I needed it” story reads as a tool, not infrastructure — so the middle paragraph turns on the feature/layer decision, which is an architecture fact and true regardless of who has embedded Relay yet. Designed to sit immediately before M08: the callout pre-frames M08’s “most of them the founder’s own daily operation” as a first workload rather than thin traction, which is the whole reason the slide exists. In a flow without M08 the callout loses its referent — re-word or drop it. Do not write that Relay powers other platforms: as of 2026-09-22 no third-party product ships on it (EC, asked directly: “not yet”), and a built-but-dormant capability claim breaks the standing constraint. “Runs on open protocol, works inside Claude/Cursor/custom agents” is present-tense true and carries the same altitude. v2 (2026-09-23), EC:“i built it because it didn’t exist, not just that I needed it. Others will need this.” The headline moves from need to absence — a founder who needed something built a tool; a founder who found nothing there built infrastructure. The closing line carries the “others” beat as a claim about the PROBLEM (“anyone putting agents into real work hits it next”), never about adoption — no third party ships on Relay as of today, so a users claim would break the standing constraint. Do not rewrite that line into “teams are adopting” or any present-tense usage claim.
M08 OPEN · v4 · 2026-09-11 · T06 Proof · figure: traction set the number is evidence, not the hero
Real today
Active now, with the tools people already use.
relays moved — a year of one operator's real daily work, not a demo
revenue — every user on a free or beta plan until v1.0
Live where the work happens — Claude, Cursor, custom agents, any MCP-compatible platform; no integration required
Going to market now.
“Not a concept — a working layer.”
The honest set and nothing else; never the retracted “21 external” figure. The headline is the maturity claim; the number is evidence under it, never the hero. Re-verify every figure at every re-cut. v5 (2026-09-18): the closing line was “Protection in progress.” — retired. The provisional is deferred on cost (relay-board finance/commitments.md), so next to traction numbers that line implied a filing in motion and invited the exact “moat without a castle” objection an investor put in writing on 2026-09-18. “Going to market now” is true, answers the “so what next” the slide raises, and pre-empts the objection instead of inviting it. Do not restore an IP claim here without a filing.
M58 OPEN · v1 · 2026-09-19 · T02 Statement · figure: three facts
Beside Claude
The layer a team keeps under its own control.
For a team piloting Claude, Relay is the context layer beside it: what one session knew moves to the next — the same person's, a teammate's, or an agent's — and the team keeps a record of who received what, and when. Nothing at the bank is integrated with; each person connects Relay to the assistant they already use in a few minutes.
PortableMoves between Claude Code, Claude Desktop, Cursor and any MCP-compatible tool without re-briefing.
CollaborativeOne shared Stream per team: the current state of the work, where the next session starts.
SovereignContext stays under its owner's control, not inside any one assistant. Encrypted, hardened service today; per-tenant keys next; customer-held keys for regulated deployments.
Runs from North American infrastructure today. A pilot runs on working context, not client data.
Outcome-level only: what a team keeps, never how. The ladder is named at its rungs (trust/narrative.md — hardened SaaS today, per-tenant keys near-term, customer-held keys funded) and nothing below that altitude. The limit is conceded on the face because a bank will ask: NO Canadian-only residency exists — content sits in the shared US/CA region (DESIGN-NOTE.data-residency) — so never say "your data stays in Canada". Hosts named are the verified set only. Built 2026-09-19 for the enterprise-pilot flow; M-ID provisional, EC assigns the final.
M59 OPEN · v1 · 2026-09-19 · T11 Timeline · figure: kickoff → weeks 1–6 → day 60–90
The pilot
Small, short, and on working context.
KickoffFive to fifteen peopleOne team from the Claude pilot, ideally one that already shares work. Thirty minutes to start; each person connects in a few minutes.
Weeks 1–6Three things, only threeHand work between sessions and tools with a Code. Keep one shared Stream as the team's working state. Let an agent receive context the same way a person does. Check-ins at week two and week six.
Day 60–90What we learnWhether people come back on their own in the first week; whether handing work between tools becomes normal; whether the team stops pasting files around.
Nothing during the pilot. If it continues, the standard Team plan at the public price — fifteen dollars a seat a month — said before the pilot ends, not after. Receiving and export are always free, and your context is never hostage.
The pilot shape from growth/pilot-proposal.audi-strecker.md, generalized: no fee, the public Team price named ahead (strategy/pricing-commitments.md — the three invariants on the face are ratified), no Enterprise number, no discount, ever, on an OPEN face. Cohort five to fifteen; sixty to ninety days; two check-ins. If a recipient asks for Enterprise terms the answer is a separate conversation on its own paper. Built 2026-09-19 for the enterprise-pilot flow; M-ID provisional.
M09 OPEN · v1 · 2026-06-04 · T08 Round · figure: toggle per recipient; filled from Canonical Facts by the build
The round
Raising a pre-seed to scale the layer.
A pre-seed via SAFE — open now, rolling close. Funds the founding team, go-to-market, and enterprise pilots.
Founding teamGo-to-marketEnterprise pilots
Terms and the full picture in conversation, under MNDA.
“The next step is a short conversation — and a look at what's already built.”
Per-recipient toggle. With the figure on, the build drenches this slide and fills the figure from Canonical Facts (the round's page of record is the source; never type it here). No cap, no discount, no returns, no projections.
M05 OPEN · v5 · 2026-09-22 · T15 Close · drenched bookend · invite aside (cut generates the QR from invite-url; absent otherwise)
Context carries forward with Relay.
A high-level introduction, shared ahead of a fuller conversation. Product, architecture and early signal are best shown directly.
Close. The Introduction variant. The full-deck variant (the ask + next steps) is NDA-tier and lives on the board. v4 (2026-09-12): the invite aside — a QR the cut generates from the flow's invite-url (with invite-url-display and invite-line); a flow without the variable keeps the plain close. First use: the Elevate 2026 profile deck, pointing at the access code ELEVATE2026 (the tracked /x/ link the code mints — case-sensitive, so the address on the face is the code's own spelling). v5 (2026-09-22): “conversation” said twice in three sentences; the closing line goes, the invite aside is the call to action.
G1 NDA · v1 · 2026-06-03 · T16 Gate divider
NDA gate
What follows is shared under NDA.
Architecture, business model, and defensibility. The Introduction deck ends at the close and never includes this slide or anything after it.
Divider. Its presence in a cut is itself a gate check.
NDA and data-room families — index rows only
The copy for these slides is not in this repository. Since 2026-09-12 it is version-controlled in the gated master on the board — relay-board/docs/operations/assets/deck-master-nda.html, the same <section class="rly-slide"> markup behind Access, with the board's canon reconciliation applied — which decks/deck.config.json names and the build merges in. Archetypes below are as built there; EC assigns finals. The June Drive Master Copy Deck document is superseded: build_deck.py --copy generates the copy deck from the masters.
ID
Slide
Gate
Archetype
Figure
M10
The Platform
NDA
T12 Layers
four layers over a foundation
M28
Interaction Model
NDA
T05 Category
the three streams, the four lanes beside
M11
How It Works
NDA
T04 Flow
nodes + chip, at the NDA altitude
M13
Validation
NDA
T03 Statement with callout
—
M14
Landscape
NDA
T13 Landscape
named categories, Relay as the band between
M12
The Moat
NDA
T02 Statement
the compounding loop
M24
Enterprise: Two Models
NDA
T05 Category
the two models, the three phases beside
M29
Enterprise Data Layer
NDA
T05 Category
five pillars
M16
The Choreographer
NDA
T05 Category
the four questions
M17
Two Protocols, One Layer
NDA
T05 Category
two surfaces
M18
Your Context, Everywhere
NDA
T02 Statement
—
M19
The Graph
NDA
T02 Statement
—
M20
Business Model
NDA
T05 Category
Free → Pro → Team → Enterprise
M21
Projections
NDA
T09 Ladder
month 6 → 24, the Series A gate marked
M22
Where This Goes
NDA
T05 Category
four vectors
M23
The Ask
NDA
T07 Stat
the target; cap, discount, ownership, runway as facts
M25
Anchor Motion
NDA
T11 Timeline
pilot → year 1 → years 2–3
M26
Targets & Gates
NDA
T11 Timeline
the two gates
M27
Raise Structure
NDA
T02 Statement
—
M34
Team
NDA
T14 Roster
the roster
M36
Founder
NDA
T05 Category
the three lines, the seat beside
M40
Use of Funds (summary)
NDA
T10 Bars
four groups
M41
Use of Funds: Allocation
NDA
T10 Bars
twelve lines, largest-remainder percentages
M42
The Plan: Hires & Milestones
NDA
T11 Timeline
hires and gates
M43
Platform Roadmap
NDA
T11 Timeline
Now · Next · Then — time-sensitive
M44
Milestone-Gated Tranches (the Drive master's unregistered “One System” close also carries M44 in its note — a bound rebuild replaces it)
NDA
T09 Ladder
T1–T4, floor and target marked
M45
The Community Allocation
NDA
T07 Stat
the slice
G2
Data-room gate
NDA+FILED
T16 Gate divider
—
M30 · M31 · M32 · M33 · M35
Patent · Unit Economics · Cap Table · CTS · Architecture