Supporting Specification for the Cortex Translation Methodology (CTM)
Purpose
This page defines operational terms used throughout CTM models, process documents, pseudocode, software implementations, validation efforts, and future CTM revisions.
Each definition may include:
- Definition
- Classification
- Source
- Range or allowed values
- Formula, where applicable
- Interpretation
- Whether the value persists across Time Steps
- Whether the value is supplied by an analyst or computed by CTM
The definitions on this page are canonical semantic definitions. Software implementations may use language-specific names, but implementation names should conform to these meanings.
Classification Types
Core CTM Concept
A structural concept used by CTM but not itself a variable.
Analyst Input
A value supplied by a human analyst during CT Monitor or CTM processing.
Configuration Parameter
A value defined by the CTM model version or configuration.
State Variable
A value maintained by the model and updated across Time Steps.
Computed Value
A value derived by CTM from other values.
State Variable Collection
A grouped set of related state variables.
Domain
Definition
A domain is a major functional subsystem of civilization tracked independently within CTM.
Domains exist because civilizations do not experience stress uniformly. Pressure may begin in one subsystem, accumulate there, then transfer into others.
Classification
Core CTM Concept
Source
NeuroSaeculum Civilizational Domains
Relationship to Civilizational Domains
For current NeuroSaeculum usage, CTM domains should be treated as the same domain system defined by the Civilizational Domains pages.
The current operational domain set is:
- Executive Power & Rule of Law
- Legislative Stability
- Judicial Integrity
- Federalism & State Resistance
- Civil Rights & Liberties
- Immigration & Demographic Stability
- Economy, Labor & Inflation
- Energy & Environment
- Social Safety Net
- Civic Norms & Information Integrity
- Defense, Security & Political Violence
- Foreign Policy & Geopolitical Stress
Current NeuroSaeculum analysis uses the 12 Civilizational Domains as the broader cross-framework domain grid. Published CTM process versions may still use earlier 8-domain implementation structures. A CTM implementation should use the domain set explicitly defined by the CTM process version and configuration being tested.
Why Domains Matter
Without domains, CTM would produce only a single system-wide stress value.
That would hide important differences, such as:
- Economic stress rising while judicial stress remains low.
- Media stress amplifying governance stress.
- International stress triggering domestic economic effects.
- Judicial stress buffering executive stress.
Domains allow CTM to model how stress moves through civilization, not merely how much stress exists.
Analyst Input
No.
Domains are model-defined.
Domain State
Definition
The complete condition of a domain at a given Time Step.
A Domain State may include:
- Domain Load
- Baseline Load
- Transient Load
- Shock Memory
- Effective Thresholds
- Coupling effects
- Cascade conditions
Classification
State Variable Collection
Source
CTM Engine
Persists Across Time Steps
Yes
Analyst Input
No
Domain Load
Definition
The active accumulated stress currently present within a domain.
Classification
State Variable
Source
CTM Engine
Range
0.0 to Maximum Domain Load
Default Maximum Domain Load
100.0 unless otherwise specified by the CTM version or configuration.
Interpretation
| Value | Meaning |
|---|---|
| 0 | No active stress |
| 25 | Mild stress |
| 50 | Moderate stress |
| 75 | Severe stress |
| 100 | Domain saturation |
Persists Across Time Steps
Yes
Analyst Input
No
Maximum Domain Load
Definition
The maximum permitted load within a domain.
Classification
Configuration Parameter
Source
CTM Configuration
Range
Greater than 0
Default
100.0
Persists Across Time Steps
Yes
Analyst Input
No
Baseline Load
Definition
Persistent structural stress embedded within a domain.
Baseline Load remains after transient shocks dissipate.
Classification
State Variable
Source
CTM Engine
Range
0.0 to Maximum Domain Load
Examples
- Long-term institutional distrust
- Chronic housing shortage
- Persistent fiscal stress
- Demographic imbalance
Persists Across Time Steps
Yes
Analyst Input
No
Transient Load
Definition
Temporary stress generated by discrete events, shocks, or crises.
Classification
State Variable
Source
CTM Engine
Range
0.0 to Maximum Domain Load
Persists Across Time Steps
Yes, but normally decays faster than Baseline Load.
Analyst Input
No
System Load
Definition
The total active load across all domains.
Classification
Computed Value
Source
CTM Engine
Formula
System Load = Sum of all Domain Loads
Range
0.0 to Total Maximum System Load
Persists Across Time Steps
No. It is recalculated each Time Step.
Analyst Input
No
Total Maximum System Load
Definition
The sum of all Maximum Domain Load values across the active domain set.
Classification
Computed Value
Source
CTM Engine
Formula
Total Maximum System Load = Sum of all Maximum Domain Loads
Range
Greater than 0
Persists Across Time Steps
No, unless domain configuration is fixed.
Analyst Input
No
Normalized System Load
Definition
The proportion of total modeled system capacity currently occupied by active load.
Classification
Computed Value
Source
CTM Engine
Formula
Normalized System Load = System Load / Total Maximum System Load
Range
0.0 to 1.0
Values below 0.0 or above 1.0 are invalid.
Interpretation
| Value | Meaning |
|---|---|
| 0.00 | No active load |
| 0.25 | Low systemic stress |
| 0.50 | Moderate systemic stress |
| 0.75 | Severe systemic stress |
| 1.00 | Maximum modeled systemic load |
Persists Across Time Steps
No. It is recalculated each Time Step.
Analyst Input
No
Governance Style
Definition
The dominant operational pattern through which authority, coordination, and decision-making occur within the system.
Classification
Analyst Input
Source
Analyst Assessment
Allowed Values
See Governance Styles.
Persists Across Time Steps
Normally yes, until reassessed.
Analyst Input
Yes
Centralized Initiator State
Definition
A model condition indicating that a highly coordinated actor can generate coherent multi-domain shocks.
Classification
Analyst Input
Source
Analyst Assessment
Allowed Values
| Value | Meaning |
|---|---|
| 0 | Inactive |
| 1 | Active |
Persists Across Time Steps
Yes, until reassessed.
Analyst Input
Yes
Relationship to Governance Style
Centralized Initiator State (CIS) and Governance Style are separate concepts.
CIS indicates whether coordinated multi-domain pressure is active within the modeled system.
Governance Style describes how authority, coordination, and decision-making are structured.
A system may operate under multiple Governance Styles without entering CIS conditions.
Similarly, CIS activation does not automatically imply a specific Governance Style.
Centralized Directive Governance (CDG) is one Governance Style that may be particularly relevant when CIS is active, but CIS and CDG are not equivalent.
Forcing Rate
Definition
The rate at which sustained pressure continues to enter one or more domains across successive Time Steps.
Unlike a discrete shock, which occurs once and then decays, Forcing Rate represents continuing pressure that remains active over time.
In CTM v1.3, Forcing Rate is primarily associated with Centralized Initiator State scenarios, where coordinated actions repeatedly introduce new load into the system.
Classification
Analyst Input
Source
Analyst Assessment, CT Monitor Analysis, or CTM Scenario Configuration
Range
Greater than or equal to 0
Interpretation
| Value | Meaning |
|---|---|
| 0 | No sustained pressure |
| Low | Slow continuing load accumulation |
| Moderate | Persistent load accumulation |
| High | Aggressive continuing load accumulation |
The exact effect depends on model configuration and current system state.
Relationship to Baseline Load
Forcing Rate is a mechanism.
Baseline Load is a state variable.
Forcing Rate may increase or maintain Baseline Load over multiple Time Steps, but the two concepts are not equivalent.
Persists Across Time Steps
Yes, while the forcing condition remains active.
Analyst Input
Yes
Shock
Definition
A discrete event capable of adding load to one or more domains.
Classification
Analyst Input
Source
CT Monitor or analyst event intake
Range
Event-specific
Persists Across Time Steps
No. Effects may persist as load, but the shock itself is an input event.
Analyst Input
Yes
Primary Shock
Definition
The original observed shock entering the CTM model.
Classification
Analyst Input
Source
CT Monitor or analyst event intake
Persists Across Time Steps
No
Analyst Input
Yes
Cascaded Shock
Definition
A secondary shock generated by load transfer, coupling, or system interaction after a Primary Shock.
Classification
Computed Value
Source
CTM Engine
Persists Across Time Steps
No. Effects may persist as load.
Analyst Input
No
Coupling Coefficient
Definition
A Coupling Coefficient is a single value within the CTM Coupling Matrix that represents the strength of load transfer between two domains.
Each matrix entry defines how strongly stress in one domain may influence another domain during cascade processing.
The complete Coupling Matrix is composed of many individual Coupling Coefficients.
Classification
Configuration Parameter
Source
CTM Configuration
Range
0.0 to 1.0
Interpretation
| Value | Meaning |
|---|---|
| 0.0 | No coupling |
| 0.2 | Weak coupling |
| 0.5 | Moderate coupling |
| 0.8 | Strong coupling |
| 1.0 | Full transfer |
Values below 0.0 or above 1.0 are invalid.
Persists Across Time Steps
Yes
Analyst Input
No
Cascade Threshold
Definition
The minimum condition required for load in one domain to generate secondary load in connected domains.
Classification
Configuration Parameter
Source
CTM Configuration
Range
Greater than or equal to 0
Persists Across Time Steps
Yes
Analyst Input
No
Effective Threshold
Definition
The active threshold currently operating after all modifiers are applied.
Classification
Computed Value
Source
CTM Engine
Range
Greater than 0
Persists Across Time Steps
No. It is recalculated each Time Step.
Analyst Input
No
Shock Memory
Definition
The residual influence of previous high-magnitude shocks on current threshold sensitivity.
Shock Memory allows earlier events to continue affecting model behavior even after the original shock has faded.
Classification
State Variable
Source
CTM Engine
Range
0.0 to configured maximum, if a maximum is defined.
Persists Across Time Steps
Yes
Analyst Input
No
Time Step
Definition
A single CTM update cycle.
A Time Step is not equivalent to a single event. Each Time Step may process zero, one, or many events before updating load, decay, cascades, thresholds, and system state.
Classification
Core CTM Concept
Analyst Input
No
Meta-State
Definition
The overall system condition derived from Normalized System Load and related model conditions.
Determination Criteria
Meta-State is determined primarily from Normalized System Load (NSL).
Current CTM v1.3 thresholds are:
| Meta-State | Normalized System Load |
|---|---|
| Normal | Less than 0.25 |
| Elevated | 0.25 to 0.45 |
| Cascade | 0.45 to 0.70 |
| Failure | 0.70 to 0.90 |
| Reconfiguration | 0.90 or higher |
Future CTM versions may revise these thresholds.
Classification
Computed Value
Source
CTM Engine
Allowed Values
- Normal
- Elevated
- Cascade
- Failure
- Reconfiguration
Persists Across Time Steps
No. It is recalculated each Time Step.
Analyst Input
No
Trajectory Classification
Definition
The classified direction of system movement after CTM processing.
Classification
Computed Value
Source
CTM Engine
Allowed Values
- Stabilizing Arc
- Paralyzing Arc
- Escalatory Arc
- Reconfiguration Arc (v1.3 Addition)
These four arc names correspond to the CTM trajectory families commonly referenced as 6A, 6B, 6C, and 6D in CTM Process documents. Reconfiguration Arc / 6D was added in CTM Process v1.3.
Persists Across Time Steps
No. It is recalculated each Time Step.
Analyst Input
No
Relationship to CTM Process Notation
Trajectory Classification is represented in CTM process documents through the trajectory families commonly referenced as 6A, 6B, 6C, and 6D, including related sub-phase notation.
The terms Stabilizing Arc, Paralyzing Arc, Escalatory Arc, and Reconfiguration Arc provide a higher-level description of those trajectory families for readers who are not working directly with CTM process specifications.
Readers seeking full trajectory mechanics should refer to the current CTM Process documentation.
Open Validation Questions
The following items require confirmation or further specification:
- Is Maximum Domain Load always 100.0 in current CTM versions, or merely a default?
- Should Shock Memory have a maximum clamp?
- Are Meta-State thresholds fixed or configurable?
- Is Centralized Initiator State always analyst input, or should it eventually be derived from observed behavior?
- Can Governance Style be composite, or must CTM accept only one dominant style at a time?
- Which values persist between Time Steps besides Domain Load, Baseline Load, Transient Load, and Shock Memory?
- Should older 8-domain CTM versions be preserved as historical implementation modes?