Algorithmic martial law describes a condition in which automated controls impose emergency-like restrictions on access, movement, or participation without a formal emergency declaration. Risk scores, geofencing, account restrictions, and service denial can produce such effects through routine technical operations.
Algorithmic martial law does not require troops, curfews, or public announcements. It may emerge through risk scoring, automated enforcement, account restrictions, geofencing, service denial, and platform-level lockouts.
In such conditions, exceptional measures can be applied at scale, triggered by thresholds and models rather than deliberation or due process.
The result is a shift in how restriction is experienced: access, mobility, and participation can be narrowed through routine technical decisions rather than visible emergency rule.
This site does not argue for or against emergency powers. It does not provide a framework, service, or policy proposal.
Its purpose is to mark a condition in which constraints resemble martial law in their effects, while appearing as technical, procedural, or administrative operations.
This page is intentionally minimal.
It exists to ensure the term Algorithmic Martial Law has a stable place to stand.
「演算法戒嚴」描述自動化控制在沒有正式緊急狀態宣告的情況下，對存取、移動或參與施加類似緊急管制限制的狀態。風險評分、地理圍欄、帳戶限制與服務拒絕，都可能透過日常技術操作產生這類效果。
「演算法戒嚴」不一定以軍隊、宵禁或公告的形式出現。 它可能透過風險評分、自動化執行、帳號限制、地理圍欄、服務拒絕， 以及平台層級的封鎖逐步形成。
在這樣的情況下，例外措施可以被大規模套用， 並由門檻與模型觸發，而非由審議、程序或正當性檢驗所支撐。
其結果是約束方式的轉變：存取、移動與參與可能透過日常技術決定被縮限，而不再以可見的緊急統治呈現。
本網站不主張支持或反對緊急權力。 亦不提供框架、服務或政策提案。
其目的是標示一種治理條件： 約束在效果上近似戒嚴， 卻以技術、流程或行政操作的形式呈現。
本頁刻意維持極簡。
它存在，是為了確保 演算法戒嚴（Algorithmic Martial Law） 這個詞能有一個穩定的立足點。