GOVERNANCE

CIO.com on September 3, 2026: the real risk isn't a missing human in the loop, it's one that wears out — the 3-question test, and where AppH stands

On September 3, 2026, CIO.com published "When AI's human in the loop really isn't" by Grant Gross: beyond the already-known problem of the cosmetic approval button, the piece points at a second, more insidious risk — decision fatigue. When an agent is right 95% of the time, human vigilance erodes and validation becomes a formality. The article proposes a concrete three-question test to tell a real human check apart from a rubber stamp; here's how AppManager's approval gate answers it, without hiding behind adjectives.

According to Grant Gross (CIO.com, September 3, 2026), the critique of surface-level "human-in-the-loop" doesn't stop at the absence of real control — Doug Shepherd (Cloudflare) describes the most common case as a human "adjacent to the loop": able to see and flag, but not actually stop the action. The piece goes further with a second, distinct and equally real problem: decision fatigue. Eric Billingsley (TrustScale) puts it plainly: "If the system is right 95% of the time, the person's job becomes waiting for the rare case when it is wrong. Humans are not particularly good at sustained vigilance... Eventually, review becomes confirmation." Robert Blumofe (Akamai CTO) confirms it: diligence wanes, and human-in-the-loop turns into rote approval — his recommendation is to add, alongside the human, non-AI guardrails able to pause the agent's work automatically, without waiting for a click. Darren Kimura (AISquared) sums up the test that separates real control from mere monitoring in three questions: can reviewers halt the action before it takes effect? Can they change the output? Are their overrides recorded and enforced downstream? If the answer to any of those is no, Kimura warns, the human is just monitoring AI — not controlling it.

On Kimura's three questions, AppManager's approval gate clearly answers yes to all three. Can the action be halted before it takes effect? Yes — no agent action with real consequences executes without explicit approval from the owner or an admin in the Automations module, it's not an informational alert that can be ignored. Can it be modified or rejected? Yes, in the same interface. Is the override recorded and enforced downstream? Yes — every decision (approved, modified, rejected) leaves an entry in the per-actor, per-module audit log, reviewable afterward. On decision fatigue, though, AppH doesn't claim to be magically immune — it's a real risk, for us too. Our answer isn't to rely on the owner's eternal vigilance, it's to bound by design how many decisions reach them: only genuinely consequential actions (approving an expense, sending a customer reminder, confirming a refund) trigger the gate — not every micro-step the agent takes. Volume stays low by construction, not by human discipline. What AppH honestly doesn't have yet: the additional non-AI guardrail Blumofe recommends, able to pause an agent independently of the human click itself — today, the approval gate IS the only guardrail.

What struck us about this piece is that it refuses the easy answer. Plenty of human-in-the-loop articles stop at the first problem — the button that blocks nothing — and stay there, satisfied to have a technical safeguard. CIO.com points at a second problem that survives even once the first is solved: a control that genuinely blocks can still wear out over time if the person exercising it ends up approving without looking. We're not going to claim AppH is immune to that — that would be exactly the kind of unproven adjective this piece criticizes. What we can honestly say is that our answer isn't asking the owner to stay vigilant forever, it's bounding by design what they actually have to look at to what genuinely matters. And on the non-AI guardrail Blumofe recommends, we don't have it yet — noted, not hidden.

Verified by a human at AppH