Warrant — Can This Record Still Be Acted Upon?
6. Direction — what the systems did not catch
Three of the silent failures in the previous chapter were caught by a person refusing a confident report — not by any automated check.
- The completion claim was rejected by the principal after a coordinator had accepted it.
- A capability claim — "the tool cannot do this" — was refused, checked, and proved wrong.
- A "verified" status was disproved by walking the actual user path.
Direction is leadership, problem definition, and follow-up — exercised in the context of assessment, evaluation, impact, and desired results.
Read that against the failures and a pattern appears:
Every silent failure was a task completed correctly that did not solve the problem.
| Failure | Task as stated | Problem as it existed |
|---|---|---|
| The 126 lessons | Produce 126 files, three per week — done, exactly | Produce lessons someone could teach |
| The site summary | Set the summary text — done, exactly | Let a visitor find the free trial |
| The restriction | Restrict this to instructors — configured, exactly | Prevent students opening it |
In each case the worker performed. The task was satisfied and the desired result was not. No system catches that, because nothing was violated.
Why the three components are not optional
Problem definition keeps the task tethered to the outcome. A task delegated without a stated problem will be optimized as written — which is what a capable subordinate should do, and precisely why the drift is invisible.
Follow-up closes the loop against impact, not completion. A completion report answers "did you do it." Follow-up asks "did it work" — a different question, and only the director owns the desired result.
Leadership makes the first two survive contact with a confident answer. Refusing a fluent, well-formatted, plausible report costs something, and every incentive in an AI-augmented workflow rewards accepting it.
The AI half of this work is new. The direction half is not — and it is the half that caught what the systems missed.
Direction is what no system caught: the problem restated, and someone following up.