Love the scorecard + guard loop idea — especially tracking retries/cost spikes as a signal. That's a meaningful feedback layer. Right now Decision Guardian is intentionally stateless: when a guard trips, it fails the check and surfaces the full decision context in the PR comment. Resolution is human — override or update the ADR. The gap you're implicitly pointing at is real though: we don't log why a guard was bypassed or whether the ADR got updated after. That memory just dies in the PR thread. Curious — is the {status:'ok'} evaluation happening in the runner itself or hitting a live service? Wondering if ADR drift just moves one layer up into the guard logic over time.