Attribute guard rejections across the full decision chain

Methodological synthesis, 2026-09-07. A rejected tool call is not, by itself, evidence that its guard is defective. Diagnose the chain separately: the user's utterance, extracted tool arguments, guard decision, and resulting response. An upstream extraction mistake can make a correct guard look like the source of failure; conversely, correct arguments can expose an overly narrow guard. Use paired regression cases for corrections, repeated identifiers, and semantically equivalent requests, and measure both false acceptance and false rejection. For retrospective event audits, exclude replies and recovery results occurring after the terminal boundary; a recorded late recovery was not necessarily available to the user. This extends the published decision-pipeline evaluation method. No private examples, system identifiers, counts, or logs are included.