Oversight Erosion · Primary
The review process still runs. It stopped meaning anything.
How this principle feeds it
review keeps running but stops catching failures, which is the condition's defining state.
Principles Library / Earned Agent Trust
Agent Trust Must Be Continuously Earned, Not Historically Assumed
AI signs are on by default. Use the AI switch to exclude them. This principle applies once agents produce or act on work in your delivery.
For each consequence: Not seen / Sometimes / Persistently / Not sure.
Based on your answers, recognize at most two conditions: No / Partly / Yes, that is us.
Oversight Erosion: The review process still runs. It stopped meaning anything.
Governance Drag: Work is done. Approvals are not.
Intent Drift: The team built exactly what was asked. It is no longer what is needed.
What else have you observed? Optional. Shared only if you choose to start coaching.
Start a Diagnosis session: review and edit a draft containing your note, conditions you recognized in Step 3 (including whether they match partly), warning signs and consequence ratings before sending it. No scores or principle files are sent.
Trust in an agent system must be grounded in current, observed behavior, not in historical performance.
An agent that performed reliably in the past provides no guarantee of reliable performance today. As context shifts, configurations age, and novel situations arise, trust based on history becomes a governance liability.
A drop in output quality starts a review before users find the problem.
The team can say what current evidence backs its trust in the agent.
One bad failure doesn't send everyone scrambling back to manual work.
The review process still runs. It stopped meaning anything.
review keeps running but stops catching failures, which is the condition's defining state.
Work is done. Approvals are not.
manual checks on every agent output add delay well beyond the risk they remove.
The team built exactly what was asked. It is no longer what is needed.
the agent keeps executing against policies that no longer reflect the organization, and outputs stay consistent while drifting from need.
Showing all 5 practices. Answer the Diagnose questions and the most relevant come first.
Before deployment, agree what observable evidence, reviewed on what cadence, keeps confidence in the agent, and what you scale back first when it falls short.
Start by asking your team: What would have to be true for you to reduce trust in this agent?
The team can name the evidence that would make it look harder at the agent, and what it would scale back first.
Run automated, continuous monitoring and human, periodic, outcome-focused evaluation side by side. You need both. Neither one stands in for the other.
Start by asking your team: When did you last check agent outputs against today's organizational needs rather than past outputs?
Sign-off means someone actually weighed the outputs, and review time only shrinks with a written reason.
Start a structured review whenever there's a significant organizational change, a context shift or a drop in output quality.
Start by asking your team: Has anything changed in the organization since deployment that might affect whether outputs are still fit for purpose?
Each organizational change or vendor model update starts a review of the agent's outputs and policies.
Make sure the team can say, at any time, what current evidence supports its confidence in the agent.
Start by asking your team: What evidence from the last two weeks tells you this agent is still performing correctly?
Asked about reliability, the team points to outputs it checked recently.
When the agent has run a long time without incidents, take that as a cue to check whether monitoring is sufficient.
Start by asking your team: Which monitoring metrics would catch gradual degradation versus sudden failure?
Internal review catches agent failures before users or downstream systems do.