Room ended
Incident Review: settlement double-charge (SEV2)
Here's what this session produced. Review it, then decide what becomes proof - nothing leaves the room unless you choose it to.
◆ This room can become proof
A incident review isn't just a call you had - it's evidence of how you think, review, and explain. Save it to your Workspace Proof Portfolio to build a proof-backed reputation across the Skills Tech ecosystem.
Where this room came from
Provenance carried from the product that started it.
Started from Connect · on Cloud
Connect conversation
- Conversation
- conv_payments_oncall
Session summary
Assembled from your notes & rubric (not AI-generated in this MVP)
Blameless SEV2 review of a settlement double-charge caused by a dedupe race under retry storms. Owners assigned, regression test landed.
- Stronger idempotency key across all settlement writers.
- Fast, blameless root-cause; clear ownership.
- Other writers may share the same weak-key pattern - audit needed.
- Audit all idempotency keys in payments-svc by end of sprint.
Notes
Decisions, risks, strengths, and action items
- Decision
Adopt the stronger idempotency key across all settlement writers.
Tue, Jun 30, 8:00 PM
- Action
Add a regression test for concurrent retries on the same external_ref.done
Tue, Jun 30, 8:00 PM
Proof candidate
The signature output of a room - private by default.
Incident Review - Settlement Double-Charge (SEV2)
Led a blameless review, identified the dedupe race, and drove the idempotency-key fix to ownership.
- ◆Root cause found in 15 min
- ◆Regression test landed
- ◆Owner assigned
◕ Team - Your team can see this for readiness & coverage.
Saved locally to demo the loop. In the full ecosystem this writes to your Workspace Proof Portfolio; no real Workspace write or model call happens in this MVP.
Rubric
No rubric - this is a lightweight meeting mode.
Meeting-style rooms skip scoring. Add a Skills Tech Talk rubric to score communication and explanation.