Notifications
Clear all
Topic starter
18/08/2026 2:17 pm
TL;DR: Generic LLM judges and static rubrics often miss the behaviors that matter in production, so AI teams can end up optimising the wrong metrics, according to Judgment Labs. The post argues that production trajectories, user corrections, and preference signals should be converted into custom evals and reward loops, because post-deployment monitoring is now part of system quality, not an afterthought.
NHIMG editorial — based on content published by Judgment Labs: Climbing the Hills That Matter
By the numbers:
- Only 5.7% of organisations have full visibility into their service accounts.
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface.
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security.
Questions worth separating out
Q: What breaks when AI evals are not grounded in production behaviour?
A: Teams end up optimising for the wrong hill.
Q: Why do agentic AI systems need behaviour-based monitoring?
A: Because agent quality is not stable across tasks, users, or tool chains.
Q: How can organisations tell whether an AI agent is operating outside its intended boundary?
A: Look for inconsistent classifications, premature tool calls, fabricated inputs, and responses that ignore structured guardrails.
Practitioner guidance
- Map production telemetry to control objectives Define which agent behaviours matter for each workflow, then tie those behaviours to explicit control objectives such as allowed tools, approved data classes, and escalation thresholds.
- Build task-specific eval rubrics from live usage Sample user corrections, retries, approvals, and failures from production, then convert the repeated patterns into small rubrics that match the actual task.
- Separate model quality from runtime privilege risk Assess whether an agent is accurate and whether it is operating safely under the access it has been given.
What's in the full article
Judgment Labs' full blog covers the operational detail this post intentionally leaves for the source:
- How the ABM layer structures trajectory capture, bucketing, rubric mining, and reward conversion in practice
- Examples of how production user preferences are turned into stable scoring dimensions for specific workflows
- The kind of behavioural metadata teams can use to distinguish model quality problems from workflow design problems
- Implementation detail on how judge outputs can feed post-training optimisation workflows
👉 Read Judgment Labs' analysis of production-based evaluation for AI agents →
Agent behavior monitoring: why production data should steer evals?
Explore further
18/08/2026 3:10 pm
Generic evals create governance debt: When teams rely on one-size-fits-all judges, they are not just mismeasuring quality, they are building a blind spot into the control plane. The article is right that the same label can mean different things in different domains, and that reality matters even more when agent decisions map to privileges, data access, or tool execution. In agentic AI, measurement is governance, so a weak rubric becomes a weak control.
A question worth separating out:
Q: Who is accountable when production data changes an AI control model?
A: The organisation that deploys the agent remains accountable for keeping evaluation, access, and monitoring aligned with current behaviour. In practice that means product, security, and risk owners need a shared review loop so changes in usage patterns trigger control updates rather than being left to model teams alone.
👉 Read our full editorial: Production data is exposing why generic AI evals miss the mark
