Pull the Slack thread, the ticket, the design doc and the PR into one project. Ask questions. Every claim comes back cited to the exact item it came from — and nothing else.
Free for one project. No card. Connect a tool in under a minute.
Payments — idempotency incidentanswers use only the 14 items in this project
Why did the retry double-charge?
The client regenerates the idempotency key whenever the socket resets1, and the gateway only dedupes inside a 60-second window2. A retry after a slow timeout arrives as a genuinely new charge.
Answered from 2 of 14 items
PAY-1421Retry design notes stale
Reads fromSlackLinearGoogle DocsNotionGitHub…or paste any text.
How it works
A project is a boundary, not a folder.
01Create a projectOne incident, one migration, one launch. Scope is the point — it's what makes an answer trustworthy.
02Paste the context inDrop a link and Triaj recognises the source, snapshots it, and shows you how fresh that snapshot is.
03Ask, and follow the citationEvery claim carries a marker. Click it to see the snippet, the author, the snapshot age — then open the original.
Provenance
It tells you when it doesn’t know.
A model that answers everything is a model you have to double-check. Triaj answers from the project or says so plainly — and marks a snapshot stale the moment the source moves on.
Answers cite the exact item, not the toolStale snapshots are flagged, never silently usedEach member authorises their own accounts
Nothing in this project answers that
The 14 items here cover the retry path and the incident review, but none mention the refund SLA. I’d rather say so than guess.
The honest miss — a first-class state, not an error.
Stop re-reading the thread.
One project, five minutes, and the context stops being scattered.