Three Dead Ends in an AI Pairing Session, and the Replayable Claim Ledger That Ended It

说明与用途

在一次 AI 配对会议中，工程师修复了双重扣费错误，但助手的解释性声明缺乏证据。他们引入了声明账本，每条声明都附带可验证的命令，最终让高级工程师接受了补丁。

问题

A webhook handler double‑charged customers due to a retry bug, and a coding assistant’s patch was rejected because its explanatory claims were not verifiable.

结果

The claim ledger turned prose assertions into executable tests, enabling the senior engineer to verify all claims and accept the patch.

工作流

• 1. Reproduce the double‑charge bug by sending a signed webhook twice.
• 2. Use the AI assistant to propose a patch and an explanation with four claims.
• 3. Attempt to review the explanation by reading the transcript, re‑rolling the prompt, and relying on a passing test suite—each approach fails to provide evidence for all claims.
• 4. Create a JSONL claim ledger, recording each claim with a command that will fail if the claim is false.
• 5. Run the ledger runner against a pinned revision to replay each claim and record verdicts.

证据

The bug was small: a webhook handler that double‑charged on retried deliveries.

来源

The assistant proposed an idempotency key, a lookup before insert, and a small migration. Its explanation contained four assertions:…

来源

The decision that survived: a claim ledger… Before the next patch, the pair wrote every assertion the assistant made into a JSONL file…

来源