Description
Once the provider pin carries the agento11y family, five kinds become available: Collection, Evaluator, EvaluationRule, HookRule and RuleAction. They configure LLM and agent observability on a stack: evaluator definitions, online evaluation rules that sample and score live generations, and request-path guard rules that can redact or filter tools.
This is a candidate domain module, not stack-baseline content. Evaluators and rules depend on the workload being observed, so nothing here can be inferred from a stack request. The guard rules are the interesting part for a platform team, because they are a policy surface rather than a workload concern.
Decide whether this belongs in the reference at all before designing it. The README provider-family table already assigns unowned families to separate opt-in modules, and that may remain the right answer.
Verified: these five kinds are absent from the provider generated against Terraform v4.40.1 and are the whole Agent Observability upstream family.
Acceptance Criteria
- #1 A decision is recorded on whether Agent Observability is in scope for this reference, with the reasoning
- #2 If in scope, the API distinguishes platform-owned guard policy from workload-owned evaluators
- #3 If out of scope, the README provider-family table row states that and why
Definition of Done
- #1 ./scripts/validate.sh passes locally
- #2 hosted Validate workflow passes on the completing commit
Implementation Plan
Wave 2: implement and validate the opt-in Agent Observability module with structural policy/workload ownership separation; root wires and gates.
Implementation Notes
Decision, taken by the repository owner: in scope as a full domain module
All five agento11y kinds behind an opt-in module, with the API distinguishing platform-owned guard policy from workload-owned evaluators. HookRule and RuleAction are the request-path guards and are platform policy; Collection, Evaluator and EvaluationRule are workload-owned and cannot be inferred from a stack request.
The dependency on GCV-0010 is cleared: the pinned main build carries all five kinds. The README provider-family table gained an agento11y row recording this decision and stating that no kind is activated until the module ships.
Keep every rule body and evaluator definition inert and example-only. Real guard policy and real evaluator definitions are environment-owned.
Wave 1 lane D disposition, 2026-09-08: Not started and Parked because the mandatory root pre-fan-out pass did not produce a pushed seam SHA after route metadata was unavailable. Resume after GCV-0032 completes the section 5.0 pass, then spawn EXECUTION on gpt-5.6-luna at max effort with fork_turns none and the pushed pre-pass SHA. No acceptance criterion or Definition of Done item was checked.
Wave 2 selected the in-scope branch, so conditional out-of-scope acceptance criterion 3 is satisfied as not applicable. Focused Agent Observability race tests, catalog rendering, the integrated local gate, and hosted Validate run 34233686654 passed.
Final Summary
Delivered the opt-in Agent Observability API with structural separation between platform-owned guards and workload-owned evaluation resources. Completing SHA 83f81afee7526fd6e7c4ec0a47675774d00036b8; hosted Validate run 34233686654 succeeded.