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.
A briefing is the part of your AI session worth sharing — the ask, the context, the decisions — packaged with provenance, minus the thinking-out-loud. Here's why that distinction matters.
The fastest way to let an agent send email is to hand it a mailbox. Sometimes that is exactly right. A comparison of what the DIY route wins and what it quietly costs.
Worked examples — a cofounder decision, a tax check, a landlord repair, a contractor scope change, and a family trip — showing what a briefing carries and why pasting the chat fails.
Full-auto agents pitch removing review as progress. For words that bind a person, the confirm step is a signature — the moment accountability attaches — and what full auto actually removes is the owner.
Two decades of email products reorganized the inbox. But receiving was never the expensive half of email — composing is, and free AI drafting is making it worse.
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.
Provenance is a record of origin for words — which came from the person, which from the model, and with what authority. Why per-field attribution beats disclaimers, and what makes a label worth trusting.
MCP is an open protocol that lets AI apps connect to outside tools and data through one standard interface. Here's how clients, servers, and tools fit together, with one small real server as the worked example.
RelayLink is a remote MCP server, so there's nothing to install — point your assistant's custom-connector settings at the /mcp endpoint with your key and it gains nine correspondence tools.