Regime Analyzer

Module path: Framework_Field_Theory/Analyzer/Regime/ Parent module: FFT Analyzer Layer: Core Frameworks — Structural Spine

Metadata#

module: FFT Regime Analyzer
parent_module: FFT Analyzer
layer: Core Frameworks — Structural Spine
version: 2026.2
status: Active, Canonical
analyzer_type:
  - regime detection
  - regime classification
  - regime transition mapping
  - regime-boundary diagnostics
  - regime-blindness detection
  - regime contradiction analysis
  - regime drift analysis
 
session_context:
  drift_sensitivity: high
  regime_sensitivity: extremely_high
  dimensional_envelope: D0–D7
  coherence_requirements:
    - regime state must be declared or inferred
    - transitions must be explicit
    - operator-regime coupling must be visible
 
cross_module_propagation:
  imports:
    - SARG regime geometry
    - FFT operator families
    - FFT dimensional architecture
    - FFT coherence engines
    - Mode substrate states
    - Substrate Flow invariants
  exports:
    - regime signatures
    - regime maps
    - transition vectors
    - boundary diagnostics
    - blindness check profiles
    - regime contradiction reports
    - regime drift vectors

Purpose#

The FFT Regime Analyzer identifies and maps the regime state of any framework, system, or conceptual structure modeled using Framework Field Theory. A regime is the behavioral state of a framework under resonance, coherence, dimensional, and operator constraints.

Regimes (R0–R3) determine how a framework behaves in practice — not just what it contains structurally, but how it operates under real conditions. Two frameworks with identical operator sets and dimensional envelopes can occupy entirely different regimes depending on their coherence state, boundary integrity, and contradiction profile.

The Regime Analyzer is the largest diagnostic submodule in the Analyzer suite because regime analysis requires the most cross-cutting coverage: it must account for boundaries, contradictions, drift, and blind spots that the other submodules surface but do not resolve at the regime level.

This analyzer is responsible for:

• classifying regime state (R0–R3)
• mapping regime structure and transitions
• detecting regime-specific drift
• surfacing contradictions between stated and enacted regimes
• testing boundary integrity between adjacent regime levels
• running blindness checks for regime-level blind spots
• stress-testing boundaries for leakage, overlap, and collapse

It is the behavioral state diagnostic of FFT.

Regime Model (R0–R3)#

What the Regime Analyzer Detects#

1. Regime Detection & Classification#

• Current regime level (R0–R3)
• Regime stability and resilience
• Regime prerequisites and dependencies

2. Regime Mapping#

• Visual and structural regime maps across domains
• Multi-system regime comparison
• Regime topology and adjacency

3. Regime Drift#

• How regime assignments shift under perturbation or reframing
• Regime drift velocity and direction
• Drift-driven regime transitions

4. Regime Contradictions#

• Contradictions between stated and enacted regime positions
• Internal inconsistencies within a regime classification
• Contradiction severity and resolution pathways

5. Regime Boundaries#

• Boundary definitions between adjacent regime levels
• Boundary sharpness and permeability
• Transition thresholds across boundaries

6. Regime Blindness#

• Regime-level blind spots the system cannot self-detect
• Structural assumptions invisible from within the current regime
• Blindness patterns common to specific regime levels

7. Boundary Diagnostics#

• Stress-testing regime boundaries for leakage, overlap, and collapse
• Boundary integrity under scaling, perturbation, and reframing
• Diagnostic routines for boundary failure modes

Directory Structure#

Regime/
├── README.md
├── Regime_Analyzer.md
├── Regime_Maps.md
├── Regime_Drift.md
├── Regime_Contradictions.md
├── Regime_Boundaries.md
├── Regime_Examples.md
├── Blindness_Checks.md
└── Boundary_Diagnostics.md

Files#

How to Use the Regime Analyzer#

Step 1 — Declare the Framework Provide: regime assumptions, operator pattern, dimensional envelope, coherence state, and any known regime history.

Step 2 — Classify Regime State The analyzer determines: R0–R3 position, regime stability, resilience, and prerequisites.

Step 3 — Map Regime Structure Generate: regime maps, multi-system comparisons, topology and adjacency profiles.

Step 4 — Detect Regime Drift Scan for: drift in regime assignment, drift velocity and direction, drift-driven transitions.

Step 5 — Surface Contradictions Identify: stated vs. enacted regime mismatches, internal inconsistencies, contradiction severity.

Step 6 — Test Boundary Integrity Evaluate: boundary sharpness, permeability, and transition thresholds between adjacent levels.

Step 7 — Run Blindness Checks Uncover: regime-level blind spots, structural assumptions invisible from within, common blindness patterns.

Step 8 — Run Boundary Diagnostics Stress-test: boundary integrity under scaling, perturbation, and reframing; flag leakage, overlap, and collapse risks.

Step 9 — Generate Regime Signature A regime signature includes: R-level, stability, drift profile, contradiction count, boundary integrity, blindness exposure, and transition readiness.

Example Output#

Framework: Hierarchical Command Structure
Regime Signature:
  regime: R1 (Stabilized)
  stability: high
  resilience: low
  drift:
    detected: true
    type: gradual
    direction: R1 → R0 (under sustained perturbation)
    velocity: slow
  contradictions:
    count: 2
    severity: moderate
    notes: stated adaptability exceeds enacted behavior
  boundary_integrity:
    R0–R1: strong
    R1–R2: weak (transition threshold unclear)
  blindness:
    exposure: moderate
    blind_spots: inability to detect own rigidity; assumes stability equals health
  transition_readiness:
    R2: possible (requires operator rebalance and contradiction resolution)
  notes: stable but brittle; contradiction resolution and blindness acknowledgment needed before R2 transition

Navigation#

• Regime Analyzer
• Regime Maps
• Regime Drift
• Regime Contradictions
• Regime Boundaries
• Regime Examples
• Blindness Checks
• Boundary Diagnostics

Cross-Module Integration#

Related Modules#

• FFT Analyzer — Parent Analyzer module
• Drift — Drift detection across all layers
• Operators — Operator profiling and regime coupling
• Dimensional — Dimensional structure and transitions
• Coherence — Coherence stability and paradox exposure
• Examples — Cross-cutting worked examples
• SARG (theory) — Regime geometry and transition algebra

Part of TriadicFrameworks · Framework Field Theory · Analyzer