Evidence your agents can read

September 9, 2026 ยท View on GitHub

AgentOps refines existing intent and identifies exact candidates. Requested durable proof uses ordinary content manifests, evidence references and verdicts in caller-selected protected external non-Git storage. These can be inspected by people or passed to another authorized fresh context.

Optional Memory recalls reviewed topic pages or separately mines authorized episodes and curates supported claims; Learn is its compatible mining entrypoint. BD owns work, Git content and native/CASS systems episode evidence. Update an existing topic page with applicability, action, support, limits and invalidation; do not create one file per session. Exact independent support and destination review precede import. This path uses public or already-cleared inputs only and does not implement native restricted-source isolation. Memory cannot decide current product validity or claim benefit without later-task evidence.

This boundary keeps the durable asset portable without turning AgentOps into a hosted control plane, tracker, queue, or delivery system.

See the trust boundary and PRODUCT.md.