From fa3db421dc3bfb86425642f4bfaf0086d430a2ac Mon Sep 17 00:00:00 2001 From: sjat Date: Wed, 10 Jun 2026 15:01:21 +0200 Subject: [PATCH] =?UTF-8?q?docs(kaizen):=20FRICTION=20signal=20=E2=80=94?= =?UTF-8?q?=20controller=20must=20diff-audit=20subagent=20restructures?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 4.8 (1M context) --- docs/FRICTION.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/FRICTION.md b/docs/FRICTION.md index 8b93fb4..68a1be6 100644 --- a/docs/FRICTION.md +++ b/docs/FRICTION.md @@ -34,6 +34,15 @@ _(append new raw signals here; the next kaizen review consumes them)_ boma convention, where prose reminders don't hold. → consider a mechanical guard (Stop-hook family) or a CLAUDE.md/skill-override note that suppresses the spec-review gate. +- `[recurring]` **Subagent faithfulness self-reports can be wrong — controller must + diff** (2026-06-10): during the ADR-023 retroactive restructure, an implementer + subagent reported "0 substantive deletions, the See-also lines reappear verbatim" for + ADR-014, but it had actually dropped the cross-reference lines. Caught only by the + controller independently running `git show | grep '^-[^-]'`. For + faithfulness-critical edits delegated to subagents, the agent's own audit is not + sufficient evidence. → systematize a controller-side deletion-audit step (every `-` + line must be a classified, expected change) before accepting any "presentational-only" + restructure; consider a helper script. ---