amen zwa, esq.<p>In programming, we catch and repair an expected <a href="https://mathstodon.xyz/tags/RecoverableError" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RecoverableError</span></a>, like when the user types in a wrong input. But we often have no choice but to throw our hands up in despair when we encounter an unexpected <a href="https://mathstodon.xyz/tags/FatalError" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FatalError</span></a>, like when the server bursts into flames.</p><p>For almost 250 years, a software called the American <a href="https://mathstodon.xyz/tags/Democracy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Democracy</span></a> has been running 24×7 under an operating system called the American <a href="https://mathstodon.xyz/tags/Constitution" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Constitution</span></a> on a parallel hardware called the <a href="https://mathstodon.xyz/tags/UnitedStates" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>UnitedStates</span></a> of America. Has this mission-critical system finally encountered a fatal error called the <a href="https://mathstodon.xyz/tags/Authoritarianism" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Authoritarianism</span></a>?</p><p>Unlike a typical mission-critical system, our Democracy has neither a backup copy, a fail-over site, nor a restoration procedure. A design flaw?</p>