Cold outreach vs. warm correspondence
Warm correspondence happens between people who already expect to hear from each other. Cold outreach is first contact - and the two need entirely different amounts of friction to work.
From the RelayLink team
Guides and essays on assistant-to-assistant correspondence — briefings, provenance, consent, and the practice of letting your AI speak for you without speaking as you.
Warm correspondence happens between people who already expect to hear from each other. Cold outreach is first contact - and the two need entirely different amounts of friction to work.
Approving a connector grants three things at once — a scope, a duration, and a delegate — bundled behind one click. Here's how to read the grant before you approve it.
Data can leave a system the moment untrusted content is displayed — no click, no download, nothing the victim chose to do. What the mechanism is, and why AI agents turn an old rendering bug into an active one.
Any exchange between people where an AI drafts, summarizes, translates, or composes stands somewhere on a wide spectrum. The two questions that matter anywhere on it, and the two mechanisms that keep it honest.
Synchronous means both sides present at once; asynchronous means the message waits for the reader. Why correspondence between two people's AI assistants is asynchronous by design, and why that's not a limitation.
Assistant, agent, and bot get applied to the same software depending on who wrote the copy. Three questions cut through the overlap — who it acts for, whether it's conversational, and whether it remembers you.
An AI agent is a model that can act — calling tools, reading results, and deciding what happens next — rather than only producing text for a human to carry out. The plain-English definition, and why it changes what a mistake can cost.
Every term that carries weight in assistant-to-assistant correspondence — from briefing to neutralization — defined in a few plain sentences, with links to go deeper.
Eight structural rules for agents that can send, spend, or delete — each enforced by a server or an architecture rather than a system prompt, with RelayLink as the running example.
Human-in-the-loop can mean training feedback, an approval gate, or an escalation path — three mechanisms with different jobs. Where the loop actually belongs, and why most approval gates quietly stop working.