Guides and explainers
Learn
How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.
Nothing matches. Clear the search to see every guide in this list.
Reference · 36
- RelayLink account vs contact vs recipient
- RelayLink Webhook Headers Reference
- RelayLink Webhook Payload Example
- What Is an AI Agent Webhook?
- Call, email, or briefing: choosing the channel
- What is a decision record?
- The economics of attention in messaging
- Delegation vs. automation: they are not the same thing
- Defense in depth, applied to AI systems
- Tool poisoning: when the tool description is the attack
- What is an audit trail?
- What is non-repudiation?
- What is data exfiltration?
- The confused deputy problem, and why AI agents are prone to it
- How email threading actually works
- SPF, DKIM, and DMARC, explained without the jargon
- What is streamable HTTP (and why MCP servers use it)
- MCP tool annotations explained — readOnly, idempotent, destructive, openWorld
- How to evaluate an AI communication tool
- AI communication failure modes: the six ways it goes wrong
- The principal-agent problem, applied to AI assistants
- What is a context brief?
- Why AI context doesn't transfer to another person
- What is a magic link? The one-click login pattern, explained
- Cold outreach vs. warm correspondence
- What you're actually granting when you connect an app
- What is zero-click exfiltration?
- What is AI-mediated communication?
- Synchronous vs. asynchronous AI communication
- Assistant vs. agent vs. bot: what's the difference?
- What is an AI agent? A plain-English definition
- The AI correspondence glossary
- A safety checklist for AI agents that can act
- Human-in-the-loop AI: what it means and where the loop belongs
- AI provenance: knowing who said what
- What is MCP? The Model Context Protocol, explained in plain English