Provisional Order on AI Competence Anxiety

Suppose someone finishes a task in forty minutes that used to take two hours. The tools changed. The output is the same quality, possibly better, and the time investment is a fraction of what it was. These are the facts of the situation. They are not enough to resolve it.

AI competence anxiety adds one private manual check. This check is not in the workflow. It appears afterward, when the task is done and the question of what proportion of it was actually done by the person doing it becomes available for review. The check does not resolve that question. It produces a rough estimate and a mild unease that the estimate is optimistic.

That check becomes part of the normal workflow.

Under the governing rule, ai competence anxiety becomes procedure once repetition feels safer than reconsidering it. By year-end, someone has accumulated enough AI-assisted work to look back at a full calendar of tasks and find that the boundary between their output and the tool's output is not as clear as it appeared at the time. This is not a crisis. It is an administrative problem for which no standard form exists.

The help is useful enough to use and awkward enough to disguise.

Assisted work becomes routine while disclosure stays exceptional. This is the organizational state of 2023. Most workplaces that adopted AI tools did not simultaneously adopt disclosure norms for AI-assisted output. What filled the gap was a private protocol: check the output manually, keep the method quiet, proceed. AI competence anxiety is what that protocol feels like from the inside.

Consider the counterfactual: suppose no private check had been added. The work would have been submitted as produced, the method would have remained unexamined, and the unease would have accumulated without a release. The manual check is, in that sense, the more honest arrangement. It acknowledges what the workflow does not say aloud.

The acknowledgment is also private.