Deleting the poisoned page doesn't undo what your agents did with it

说明与用途

删除受污染的页面并不会撤销代理已执行的操作。kintsugi利用FalkorDB中的依赖图，仅重新执行受影响的步骤，纠正错误的退款和邮件，同时保留未受影响的工作。

问题

A poisoned policy page caused support agents to issue incorrect refunds and emails, and deleting the page did not reverse the already executed actions.

结果

Selective re‑execution via kintsugi fixed the incorrect refunds and emails without discarding all prior work, preserving the integrity of unaffected tickets.

工作流

• 1. Detect poisoned source (policy page).
• 2. Build provenance graph in FalkorDB from the bad source to all dependent actions.
• 3. Identify actions that depend on the poisoned fact via FEEDS and HANDED_OFF edges.
• 4. Re‑run only those actions against clean memory, stopping early when re‑execution yields the same output.
• 5. Apply corrections to refunds and notifications.
• 6. Verify that unaffected actions remain unchanged.

证据

Deleting the page fixes none of that.

来源

kintsugi: it walks a provenance graph in FalkorDB from the bad source to everything that depended on it, across agent handoffs, re‑runs only those steps against clean memory, and stops early wherever the answer comes out the same.

来源

agents touch memory only through the recorder

来源