TriadicFrameworks
Overview

Regime Modes Index

A directory of regime‑mode artifacts within the Governance Substrate Model (GSM)

Regime modes describe the operational patterns a governance system can occupy within the structural manifold. They are not basins, not ideologies, and not normative categories—they are dynamic modes of operation that systems move through as drift, tension, and awareness conditions change.

This index catalogs all regime‑mode artifacts in the Analyzer layer.

Purpose of Regime Modes#

Regime modes help the Analyzer:

  • interpret structural vectors in context
  • detect when a system shifts operational patterns
  • distinguish stable operation from transitional or stressed modes
  • support the Observer’s history/now/future lenses
  • provide interpretable categories for dashboards and teaching tools

They act as the “behavioral states” of a system within the manifold.

Core Regime Modes#

These modes appear across GSM analysis:

  • Stable Mode — system is aligned with its basin and invariants
  • Tension Mode — invariant strain or physics imbalance is rising
  • Drift Mode — structural movement is active and measurable
  • Compensatory Mode — cross‑axis physics is correcting imbalance
  • Transition Mode — system is crossing basin boundaries
  • Absorptive Mode — buffers are engaged to stabilize structure
  • Fragmentation Mode — oversight, timing, or access coherence is breaking down
  • Reconstruction Mode — system is re‑establishing structural identity after transition

Each mode is defined in its own artifact file (if present) or within the transition engine.

  • governance_manifold.yaml
    Defines the structural space where regime modes operate.

  • behavioral_invariants.yaml
    Determines when a system enters tension or compensatory modes.

  • governance_physics.yaml
    Governs compensatory and drift‑amplifying modes.

  • equilibrium_basins.yaml
    Defines stable modes and transition boundaries.

  • drift_detection.yaml
    Detects drift, compensatory movement, and regime‑shift drift.

  • coherence_event_schema.yaml
    Emits events that correspond to regime‑mode transitions.

  • coherence_scoring.yaml
    Quantifies stability vs. tension vs. transition likelihood.

  • observer_lens (if present)
    Uses regime modes to narrate history/now/future.

How Regime Modes Are Used#

Regime modes appear in:

  • Analyzer narratives
    (“System is in a compensatory mode due to C↔O imbalance.”)

  • Observer timelines
    (“Entered tension mode in 1993; drift mode in 1995.”)

  • Transition Simulator
    (“System is in transition mode; next step is reconstruction mode.”)

  • Dashboards
    (“Current regime mode: Stable / Drift / Tension / Transition.”)

  • Educational modules
    (“Compare France’s 2000–2010 regime‑mode sequence.”)

Extending Regime Modes#

Contributors may add:

  • new mode definitions
  • mode‑specific invariants
  • mode‑specific physics adjustments
  • mode‑specific drift thresholds
  • mode‑specific narrative templates

Extensions must remain substrate‑aligned and non‑ideological.

Purpose of This Index#

This index provides:

  • a clear map of regime‑mode artifacts
  • a reference for contributors
  • a stable anchor for future regime‑mode extensions
  • a teaching‑friendly overview of operational patterns in governance systems

It ensures regime‑mode analysis remains coherent and discoverable across the GSM.

Powered by Docsbook