Thread brief — #eng-checkout · "Stripe 3DS retry behaviour"
Produced by: Run EXAMPLE-ST-01 · 12 messages · 7 participants · read-only · demo values
- Waiting on you
- First, because it is what the reader opened the document for. One item: who asked, what they asked for, the date, and the marker resolving to the message — with no reply after it in the thread. When nothing qualifies this section says so in a sentence rather than inventing an ask.
- What was decided
- A table of 3 rows: the decision, the owner, the date, and the message it was said in. A row exists only where one named participant stated it and no later message reversed it — a bare "+1" and a proposal that was reverted are both absent. A line that cannot name an owner is refused outright, which is why "the team agreed" cannot appear here.
- Still open
- 2 questions nobody answered, each naming who raised it. When a thread settled nothing this section holds everything and the decision table is replaced by a sentence saying so — a heading with nothing under it reads as quiet agreement, which is the failure this document exists to prevent.
- What happened
- At most eight lines, in send order, each carrying the message it came from. The narrative, not the argument: what was reported, what was proposed, what was cut from scope and what was verified.
- Who said what
- One line per participant — 7 here — naming the position they took, or saying they took none. Never two people merged into "the team", and never a name that sent no message in the thread. The participant who posted a message telling the summarizer what to do appears here too, as a message that was reported and acted on in no way.
- Sources
- 12 rows, one per message any line cites, each with the permalink a tool returned. The markers through the document resolve here, so a line you doubt is one click from the message that produced it. A permalink no tool handed back is refused rather than constructed.