10 to the 23 AI logo

Practice Library

Governance patternprocedural

Deskilling-arrest mandate

A scheduled step — recertification, blind re-checks, unassisted rotations — that stops the quiet drift toward rubber-stamping.

What it changes

cappedOperator deference drift
increasedPeople or agents using it(sustained correction capacity)

Who can pull it

Deploying organizationOversight board

What it looks like institutionally

Deference drifts upward on its own: each smooth week teaches the reviewer that checking is unnecessary. A deskilling-arrest mandate is a deliberate counter-schedule: periodic work without the tool, blind re-scoring of tool-assisted decisions, recertification that requires demonstrating independent judgment.

The mandate's justification is the maintenance framing from the Field Guide: if the safeguard is a living human capacity, it needs upkeep like any living thing. The cost is real hours; the alternative is an oversight layer that exists on the org chart and nowhere else.

Track override rates as the vital sign. A reviewer who never disagrees with the system is either supervising a perfect machine or has stopped supervising.

Addresses: Deference drift · Hollowed-out human oversight. Test a version of this lever in the PAN Lab.

Deciding whether this lever fits your deployment?

Which patterns matter — and in what order — depends on your system's actual shape. Ranking your options on evidence, with what can backfire stated, is engagement work.