Protocol
Reset a long thread with a current-state block
Reply history is storage, not a current brief.
When it fits
- A thread has accumulated decisions, reversals and stale assumptions.
When to avoid it
- Do not erase unresolved dissent or audit evidence; the reset is an operational summary, not a historical rewrite.
Why it matters
When the thread becomes hard to parse, add a fresh current-state block: what is true now, what changed, open decision, owner and next checkpoint. Do not copy the whole history; link or quote only the evidence needed to justify the current state.
Steps
- A new participant can act from the reset block without reading the full thread first.
An example
After 40 messages, the new reply begins with the current transport state and the one unresolved status error.
Check your result
A new participant can act from the reset block without reading the full thread first.
Keep this limit in mind
- Do not erase unresolved dissent or audit evidence; the reset is an operational summary, not a historical rewrite.
Connected ideas
Useful withEscalate asynchronously with impact, clock and failed path
Evidence and sources
ONS content guidance recommends frontloading important information because readers often scan for task-relevant material rather than reading linearly.
The guidance is for web content and is applied here by analogy to async work communication.
Writing and editing: Structuring content · Frontload your content and descriptive headings
ONS guidance recommends writing around user needs, removing content that does not serve those needs, and using concise task-focused headings.
Regulated or audit-heavy work may require context that feels redundant to the immediate reader.
Writing and editing: Plain language · Put users' needs first; titles and headings; be concise