Sludge audit frameworks and their inversion
An audit tool that maps a service's behavioral journey, scores each friction point, and tags it as exclusionary (remove), rationing (replace with a purpose-built mechanism), or reflective (preserve but redesign for agents).
AI agents can now strip administrative friction out of a service unilaterally, faster than anyone decides whether that friction was doing a job. Some of it only excluded people and should go; some of it was quietly rationing scarce capacity or verifying eligibility, and removing it without a replacement breaks something.
The challenge is to tell those apart before the friction is gone: to audit each point of friction not just for what it costs, but for what it was holding in place.
Government needs to know, for each point of administrative friction, whether it was excluding people or quietly rationing scarce capacity before an agent strips it out, so that removing friction clears a barrier rather than breaking a function nothing replaces.
The people who lose if this goes wrong are those a removed verification was meant to protect, and those a blunt overcorrection then shuts out when an overwhelmed system reaches for blanket caps or new barriers. Keep the path open by replacing a rationing friction with a fairer mechanism rather than nothing, and never with a cap on appeals or complaints, so clearing exclusionary friction does not just relocate the exclusion.
An audit that classifies each cataloged friction point as remove, replace, or preserve, so a friction performing a rationing or reflective function is given a purpose-built substitute rather than just flagged for removal.
No surface has been built yet; the approach above is the brief for one.
- Established Headline
For auditing administrative friction.
- Frontier
For the inversion — deciding, before friction is removed, whether it rations or merely excludes, in a context where AI removes friction unilaterally.
The sludge audit framework is highly transferable and already being adopted internationally. The critical adaptation for AI-agent contexts requires a new analytical step, the sludge inversion question. For each friction point identified in an audit, ask:
- Is this friction purely exclusionary (sludge)? If so, remove it, and note that AI agents will remove it regardless.
- Does this friction perform a legitimate rationing or verification function? If so, replace it with a purpose-built mechanism (rate limit, structured intake, identity verification) before AI agents render it moot.
- Does this friction create a beneficial "pause for reflection" (cooling-off periods, mandatory consideration periods)? If so, preserve the pause but redesign it for an agent-mediated context.
The failure mode is friction imposed without anyone asking whether it performs a legitimate function before being automated. The sludge-audit inversion forces that burden analysis, whose absence lets a system impose an unexplained, unaccountable compliance burden on claimants.