Guide
Anomaly alerts & the circuit breaker
SpendSignoff watches your linked accounts for spend spikes, pacing problems, and platform errors. When something is wrong, it alerts you and stops drafting — it never reacts by spending.
Detection, not reaction
Anomaly detection in SpendSignoff is built to tell you and stop, not to act. When it sees a spend spike, a pacing problem, or a run of platform errors, it raises an alert and trips the circuit breaker. It does not respond by drafting a fix and pushing it — that would be exactly the kind of unapproved action the product is designed to prevent.
What it watches for
- Spend spikes — an account burning faster than its pacing should allow within the rolling 24h spend envelope window.
- Pacing problems — campaigns over- or under-delivering against budget in a way that suggests something broke.
- Platform errors — repeated failed or rejected responses from Google Ads or Meta APIs.
What happens when an anomaly fires
Alert you
SpendSignoff raises an alert on the affected account so a human knows immediately. The alert names what tripped and on which account.
Trip the circuit breaker
The circuit breaker pauses the autonomy loop from drafting on that account. No new proposals flow into the queue while the account is in a bad state.
Wait for a human
Nothing auto-resolves into a spend change. You review the account, decide, and — if a fix is warranted — approve it through the usual two-step Approve & push live → Confirm control.
A tripped breaker is a stop, not a spend
mcp.approve scope, so even the safety system routes through your approval.Next
Safety
Draft-before-live, propose-only, the daily envelope, and the circuit breaker.