Schema drift
Schema drift under Monitor → Schema drift (Growth+) compares the last 7 days with the 7 days before that. It surfaces agents where validation failures climb after a prompt or model change, and flags orchestration runs whose step order does not match the published playbook. Fingerprints are shape hashes — not stored payloads.
Failure-rate alerts
- Recent window needs at least
20requests before an alert can fire. - Validation-failure rate must rise by at least
10percentage points versus the prior window. - Fingerprint shift — the dominant output shape hash changed while the fail rate jumped.
- Fail-rate jump — the hash stayed the same but the failure rate still rose by the threshold.
- Each alert links to the agent's validators editor to Simulate a fix before you save.
Sequence anomalies
On published playbooks only, ValGuard compares observed orchestration step order against the template. A run is flagged when a step is unexpected, two steps share the same sequence number, or a step runs before an earlier template step.
Operator surface
Open Schema drift in the dashboard (Growth+). Pair with observability for health scores and validation coverage. Shipped notes: What's new.