AgentOps as a Trust Boundary

Generation is stochastic. AgentOps adds a small, inspectable boundary between an agent's claim and a caller's decision to rely on it.

The boundary has four facts:

• the requested behavior and acceptance are explicit;
• the exact subject is identified by content, not by a mutable branch name;
• a distinct fresh context judges that subject against the acceptance;
• the result identifies checked and unchecked scope and can be persisted as a standalone content-addressed verdict.v2 when a consumer requires it.

This is evidence, not permission to ship. AgentOps does not own Git, CI, tracking, retries, queues, release, or recovery. The consumer system decides what to do after PASS, FAIL, or NOT_PROVEN.

Optional Premortem, Council, and multi-model strategies can strengthen the judgment selected by the caller. Optional Learn analysis can study collections of past verdicts later. Neither changes the core lifecycle.

See PRODUCT.md and the RPI traversal.