What is network dependency single point of failure?

Network dependency single point of failure is a concept in personal epistemology: Tools that work without internet are more reliable for critical work.

Example: You are drafting the most consequential strategy document of the quarter. You are ninety minutes in, deep in flow, the argument crystallizing. Your cloud-based editor freezes. A spinning icon replaces your cursor. The Wi-Fi indicator on your laptop shows nothing. You refresh — the page will not load. You open a new tab — no connection. The hotel Wi-Fi has collapsed, and your document is trapped on a server three thousand miles away. You cannot see your notes, you cannot continue writing, and you cannot even verify whether your last paragraph was saved. Three miles away, your colleague is working on the same deadline using a local Markdown editor backed by files on her own machine. She does not notice the outage for forty minutes, because nothing about her workflow required the internet. She finishes the draft, syncs it when the connection returns, and never lost a sentence. The difference is not talent or discipline. It is architecture. Her tools worked without the network. Yours did not.

This concept is part of Phase 46 (Tool Mastery) in the How to Think curriculum, which builds the epistemic infrastructure for tool mastery.