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.
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.
A vague expression of interest asks the recipient to invent the project. Propose the object and the division of labour, name what you bring, and raise credit while it is still cheap.
An update is a broadcast and an ask is directed at a person. Put the second inside the first and it gets filed with the news. How to separate them, and make the ask grantable.
Outreach worth sending doesn't scale, and that is the mechanism rather than the flaw. Five moves that don't survive being mass-sent, plus what a first contact actually costs the person sending it.
The load-bearing premise in most messages is a subordinate clause nobody notices. How to surface it, attribute it, and make it cheap to correct.
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 decision record is a short durable document capturing one decision — the context that forced it, the options rejected, and the consequences accepted. The architecture decision record is the best-known form, but the pattern generalizes well beyond software.
Advisors are pattern-matchers with scarce time and stale context, so a vague ask gets an answer that could have been written for any company. Four moves that force a specific reply.
A context brief is a short passage — roughly 150 to 400 words — that gives a reader with none of your history enough background to answer one specific question, and nothing beyond it. How it differs from a summary, an executive summary, and documentation.
Issue threads are where maintainer decisions go to die — buried framing, self-selected participants, and an exhausted merge at the end. Four moves that fix it, plus the one case where a direct ask beats a thread.