Theoretical framework models behavioral dynamics of dominance-first actors across political networks, highlighting the systematic failure of rational-actor negotiations.
The Dominance Operating System (DOS) specifies the behavioral architecture of operators whose primary optimization target is dominance rather than outcome. Outcome-based frameworks (interest-based negotiation, evidence-based confrontation, shame deployment, graduated escalation) fail against this operator class systematically (rather than occasionally), because each encodes a counterpart model that does not match the target. The latter are also called rational-actor frameworks. DOS replaces that presupposition with a specification of an unstable self whose functional coherence depends on continuously manifesting dominance through interaction with audiences, opponents, and institutions. Installation is specified as the joint output of three active systems (operator, elite coalition, mass base) with counter-strategy directed at whichever system is most vulnerable rather than at the operator alone. Follower loyalty divides into two modes requiring different counter-strategies: impaired rationality, disruptable through mechanism naming and outside relationships; and trans-rational loyalty, grounded in communitas and sacred participation, which requires competing ritual rather than better evidence. Structural contents. Fifteen Laws, twenty-one Mechanisms, four Consequences, seven query modules, and an Installation Spectrum anchored by substrate irreversibility, which specifies pre-installation phases, transition events, post-installation states, and the Culminating Point of Installation past which over-installation produces coalition fragility. The operator typology distinguishes Extraction-Primary, Dominance-Primary, and Convergent types with distinct counter-strategy priorities, modified along two orthogonal axes: virtù as capability variance, and mode as operational intensity. The counter-strategy apparatus comprises a five-step Counter-Strategy Sequence, a Contraindicated Techniques list, and Counter-Ritual Design prescriptions for communitas-formed loyalty. How to use it. State which of the seven modules you are running and supply its inputs: score a move, score a response, predict the next move, diagnose the installation stage, run a vulnerability scan, assess mass-base heat, or assess elite coalition fracture. Module outputs are diagnostic hypotheses, not determinations. Accuracy is model-conditional, and the framework's known failure modes (precise transition timing, multi-mechanism simultaneity, typology-ambiguous cases, and the outstanding base-rate problem) are documented in the text rather than left implicit. The framework is downloadable as a PDF (optimized for readers) and a Markdown version (optimized for AI use). Easiest to download, read, and use the PDF version. Quick start: drag the downloaded DOS framework file (either PDF or md) into any chatbot (and note any topic or news to analyze), then ask, "How do I use this?" The framework is written to load directly into a large language model context (no plugins, no configuration, and no background in political science required). Version note. v2.1.1 is a release-form revision of v2.1 (2026-04-22). Analytical content is unchanged; revisions are confined to front matter, deposit metadata, a Quick Start section, and an AI disclosure statement. Citations to v2.1 remain valid. A companion volume, the Extended Reference (full source apparatus, case studies, cross-case stress-testing, four-layer Patronage-Capital topology, fascism-specific mechanisms, and per-claim confidence tiering) is forthcoming. Method disclosure. Developed using the Iterative AI Production (IAP) protocol, a structured human-in-the-loop research method in which large language models are used for source retrieval, cross-case stress-testing, adversarial critique, and drafting under continuous author direction. All structural claims, case classifications, and citations were reviewed and accepted, revised, or rejected by the author, who is solely responsible for the content. Comments, counter-cases, and falsification attempts are welcome.
No takes yet. Share an insight, caveat, or question.
Loren Curtis Rauch (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: