agent-evals-and-observability

name	agent-evals-and-observability
description	Design, run, review, or release framework- and vendor-neutral evaluations and observability for AI agents. Use when defining agent evals, datasets, graders, trajectory review, regression analysis, release gates, production traces, or privacy-aware telemetry. Covers task and trajectory contracts, statistical comparisons, and incident-to-case learning; route framework implementation to pydanticai or langgraph when needed.
license	MIT
compatibility	No runtime dependency. Host-, framework-, model-, and telemetry-backend-neutral methodology.
metadata	{"source":"Curated from primary and official sources listed in references/source-index.md; checked 2026-07-13"}

Agent Evals and Observability

Evaluation asks whether behavior meets a defined criterion on a declared dataset or production sample. Observability supplies traces, logs, metrics, correlations, and diagnostic context. Use both; neither proves what the other does.

Workflow

1. Define the decision, risk, task contract, trajectory contract, and unacceptable outcomes. Select evidence by harm, reversibility, and deployment stage, not a staged completeness scale.
2. Create an immutable dataset version and manifest before comparing versions. Declare provenance, rights/consent, slices, fixtures, expected side effects, contamination risk, limitations, retention, and changelog.
3. Select complementary graders that observe the claimed property. Use deterministic checks for observable mechanics; use execution/environment checks for state and side effects; use human, model-judge, pairwise/ranking, domain, and safety review where appropriate.
4. Run the candidate and baseline under comparable conditions. Preserve run configuration, stochastic repeats where variability affects the decision, failures/timeouts, and trajectory evidence.
5. Report a multidimensional profile and uncertainty. Use paired comparisons where possible; inspect slices, missingness, base rates, confounders, effect sizes, and multiple comparisons. Non-significance is not equivalence.
6. Apply a risk-tiered release gate: hard safety, privacy, authorization, and side-effect invariants cannot be averaged away. Record authority, insufficient-evidence outcomes, rollback, and follow-up.
7. Instrument production with minimized, redacted telemetry. Feed verified incidents and near misses into cases after consent, transformation, and contamination review.

Stop when the supported decision, evidence gaps, residual risks, and responsible owner are recorded. Escalate rather than infer a pass when required evidence is unavailable or conflicts.

Load By Need

Need	Load
Choose evaluation evidence and contracts	references/evaluation-design.md
Build immutable cases, fixtures, and provenance	references/datasets.md
Select or calibrate graders	references/graders.md
Define measures or compare runs	references/metrics-and-statistics.md
Review tools, state, recovery, or side effects	references/trajectory-review.md
Triage a regression or decide release readiness	references/regression-and-release.md
Design traces, logs, metrics, or privacy controls	references/production-observability.md
Interoperate with OpenTelemetry	references/opentelemetry-genai.md
Need framework-specific implementation	references/framework-routing.md
Exercise the methodology with safe probes	references/synthetic-scenarios.md
Verify a source claim or status	references/source-index.md

Templates

Use templates/eval-plan.md, templates/dataset-manifest.md, templates/grader-specification.md, templates/trace-review.md, templates/run-report.md, and templates/release-gate.md. They are decision records, not checklists that manufacture evidence.

Guardrails

• Do not use a scalar score, keyword hit, schema validation, or repeated output as proof beyond the property it directly observes.
• Do not capture prompts, outputs, tool arguments, intermediate reasoning, credentials, or personal data by default. Minimize before export, redact early, restrict access, set retention/deletion paths, and prepare incident response.
• Do not treat human judgment as definitive truth. Human and model graders require explicit rubrics, calibration, disagreement analysis, and revalidation when conditions change.
• Keep prevalence-oriented production samples separate from risk-enriched challenge cases. Do not silently reweight either into the other.

When Not To Use

Use systematic-debugging to investigate one active defect before proposing fixes. Use verification-methodology for general evidence-backed completion claims, secure-software-engineering to design preventive controls, and framework skills for SDK-specific code.