Offline capability audit: disconnect, test each critical tool for 10 minutes, grade fully/partially/dependent — find local-first alternatives for dependent critical tools

Why This Is a Rule

Internet connectivity is a single point of failure for cloud-dependent tools. When the WiFi goes down on a flight, at a coffee shop, or during an outage, every cloud-dependent tool in your stack becomes simultaneously unusable. If your note-taking app, task manager, and document editor all require internet, a connectivity loss blocks your entire workflow — not because the work requires internet, but because the tools do.

The offline capability audit reveals your actual internet dependency by empirically testing it. You disconnect and discover which tools work fine (local-first), which work partially (cached data readable but not editable), and which fail completely (blank screen or error message). The audit converts vague assumptions ("I think my tools work offline") into verified grades, revealing the real vulnerability surface.

For any critical tool graded "fully dependent," you need either a local-first alternative or an explicit contingency plan. The goal isn't to eliminate all internet dependency — that's impractical — but to ensure your critical path (the tools needed for your most important work) can function during connectivity loss. Non-critical tools can remain cloud-dependent without risk.

When This Fires

• Annually, or when adding a new critical tool to your stack
• Before any extended travel or location change where connectivity may be unreliable
• When a connectivity outage has revealed unexpected tool dependencies
• Complements Choose open portable formats (Markdown, CSV, JSON) over proprietary — migration cost compounds daily with every new piece of locked-in data (open formats) and 3-2-1 backup rule: 3 copies of critical data, on 2 different media types, with 1 stored offsite — redundancy protects against correlated failures (backup rule) with the connectivity-resilience dimension

Common Failure Mode

Assumed offline capability: "Google Docs works offline!" — but only if you enabled offline mode in advance, only for recently opened documents, and only in Chrome. The actual offline experience may be far more limited than the marketing claims suggest.

The Protocol

(1) List your critical tools: the tools needed for your most important daily work (note-taking, writing, task management, communication). (2) Disconnect from the internet (airplane mode or WiFi off). (3) Test each critical tool for 10 minutes of actual use: can you create new content? Edit existing content? Access your data? Search? (4) Grade each tool: Fully offline (all critical functions work without internet), Partially offline (some functions work; others don't — document what's limited), Fully dependent (the tool is unusable without internet). (5) For any critical tool graded "fully dependent": identify a local-first alternative that can serve as a fallback during connectivity loss. For "partially offline" tools: document the limitations so you know what to expect.