Guides and explainers
How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.
A decision transfers ownership of an outcome. An opinion transfers judgment and leaves you holding it. A review hunts defects in something already built. Picking the wrong one is why careful messages get answers that miss.
Four days of silence and the instinct is to write the nudge. Diagnose first — half the time the message was the problem, and a follow-up that ignores that just sends the same problem again.
A no that comes back for a second round was usually a maybe when it left. Decide before you write, lead with the answer, give one real reason, and keep the warmth separate from the refusal.
Subject lines drifted into advertising, so readers learned to discount them. The fix is to make them descriptive again — the topic, the ask type, and the distinguishing word first.
You cannot un-know your own background, so you cannot feel what is missing from your draft. Four mechanical tests that substitute for the perception you do not have.
A TL;DR is a verdict, not a topic label, and some readers will act on it without opening anything else. The rules that make it safe for them to do that.
A call, an email, and a briefing each win in a different situation. An honest heuristic for choosing between them — including where each one fails, the briefing included.
Sending cost and reading cost are paid by different people, and every drop in the price of composing widens the gap. What that does to a channel, and the only two structural responses to it.
The understanding you built across a long AI session is not a document you can hand over. It is accumulated state — corrections, abandoned directions, and inferences nobody typed — indexed to you.
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.