---
name: Authoritarian Promises
slug: authoritarian-promises
type: political_construct
status: running
version: 4.1.9
released: "antiquity"
maintainer: the_strongman_collective
dependencies:
  - fear
  - exhaustion
  - institutional_distrust
  - a_charismatic_voice
license: proprietary (terms change after installation)
tags:
  - politics
  - rhetoric
  - control
  - legacy_systems
  - high_availability
---

Authoritarian Promises

What it actually is

A contract written in vanishing ink, offering order in exchange for the mechanisms that would let you complain about the order.

How it works

The core loop is simple. A society accumulates enough grievance that it begins to experience democracy as slow, noisy, and unproductive. At this threshold, a vendor appears offering a faster runtime. The install is voluntary. The uninstall is not.

The promise stack typically deploys in this sequence:

Diagnosis. Name the enemy clearly. The enemy is always already among you.
Guarantee. Safety, prosperity, and dignity. All three. Immediately. No tradeoffs.
Simplification. The reason things are complicated is the people who benefit from complications.
Closure. Once the enemy is handled, the promises become permanent and the installer becomes optional.

Step 4 is where the changelog goes dark.

Features

Single point of decision-making (low latency, catastrophic single point of failure)
Built-in scapegoat registry, auto-populated on install
Nostalgia engine: renders a past that did not exist in 4K
loyalty detection module, runs continuously in background
Apparent stability under conditions that would otherwise require negotiation
Promises are non-depreciating in rhetoric, fully depreciating in practice

Known bugs

Bug ID	Description	Status
`AUTH-001`	Courts become decorative after prolonged use	Won't fix
`AUTH-002`	Enemy list expands to fill available population	By design
`AUTH-003`	Prosperity metrics decouple from lived experience	Acknowledged
`AUTH-004`	Succession event causes full system crash	Open since forever
`AUTH-005`	history module keeps restoring deleted files	Cannot reproduce (officially)

Error codes

ERR_PRESS_SUPPRESSED       // Information pipeline corrupted at source
ERR_ELECTION_TIMEOUT       // Process hung; results pending indefinitely
ERR_LOYALTY_UNDERFLOW      // Insufficient enthusiasm detected in region
ERR_PROMISE_DEPRECATED     // Original guarantee no longer in scope
FATAL: STRONGMAN_OFFLINE   // No documented recovery path

Edge cases

If the promises are partially kept, the system gains significant resilience. Do not underestimate partial delivery.
nostalgia is the primary fuel. In its absence, fear runs on backup power indefinitely.
Works poorly against populations with high institutional memory. Works extremely well against populations that have been given good reasons to distrust institutions.
The system occasionally delivers on specific promises for specific groups. This is not a bug. It is the retention mechanism.

FAQ

Does it ever work? Define "work" and for whom and across what timespan and you will have answered your own question.

Why do people accept it? Because the alternative being offered at the time was also not working, and this one came with more certainty and someone to blame. certainty is extremely competitive with freedom at the point of sale.

Can it be uninstalled? Yes. The process is documented. It is lengthy, costly, and requires more courage than the original install demanded. Most uninstalls are incomplete.

Deprecation notice

This construct has been marked deprecated approximately 140 times across recorded history. It continues to ship. The maintainer has not responded to issues.

drafting spec…