Classify tool delegations as appropriate, convenient, or critical — critical delegations create capability gaps when tools fail

Why This Is a Rule

Not all tool delegations carry the same risk. Using a spell checker (appropriate: it's better than you at pattern-matching and easy to verify) is fundamentally different from relying on GPS navigation so completely that you can't navigate without it (critical: tool failure would strand you). The classification determines how much redundancy you need.

Appropriate delegation: the tool performs the task better than you could, and you can easily verify its output. Using a calculator for arithmetic. Using a linter for code style. These are pure gains — the tool is more reliable than you, and errors are easy to catch. Convenient delegation: the tool saves time, but you retain the capability to perform the task yourself. Using AI to draft emails you could write yourself. Using templates for documents you could create from scratch. These are efficiency gains with built-in redundancy — if the tool fails, you fall back to doing it yourself. Critical delegation: you cannot perform the task without the tool because the capability has atrophied or was never developed. Using GPS without map-reading skills. Using AI for analysis you can't perform manually. These create single points of failure: tool failure = capability gap.

When This Fires

• Before adopting any new tool for cognitive work
• When evaluating existing tool dependencies for resilience
• When a tool goes down and you discover you can't do the work without it — that's a critical dependency you should have identified earlier
• When building AI-augmented workflows where capability delegation is increasingly common

Common Failure Mode

Drifting from convenient to critical without noticing: you start using GPS as a convenience (you could navigate without it) and gradually lose the underlying skill. Five years later, GPS failure means you can't navigate at all. The delegation silently shifted from convenient to critical as the biological skill atrophied. The classification must be re-evaluated periodically because capability atrophy changes the category.

The Protocol

(1) For each tool-delegated task, classify: Appropriate: tool is more capable AND output is easily verifiable. Low risk. Convenient: tool saves time AND you retain the underlying capability. Medium risk — ensure the capability is maintained. Critical: you cannot perform this without the tool. High risk — the tool is a single point of failure. (2) For appropriate delegations → delegate freely. The risk is minimal. (3) For convenient delegations → delegate but periodically exercise the underlying capability (Periodically perform critical delegated tasks without the tool — maintaining the biological skill is redundancy, not inefficiency) to prevent drift to critical. (4) For critical delegations → either invest in developing the biological capability (reducing dependency) or invest in tool redundancy (backup tools, fallback procedures). (5) Re-classify annually: has any convenient delegation drifted to critical?