(A1) One-Panel Engine

CivOS Phase-Shift Engine: Detect Regime Change Before Headlines (v1.0)

Start Here for Shadow Sensor Pack https://edukatesg.com/shadow-sensor-ecu-ssecu/

Summary (5 lines)

Civilisation-scale events (war, crashes, tech jumps) follow one structure: noise → posture → readiness → intent → actuation → irreversibility → new phase.
Most people misread rhetoric as actuation.
CivOS fixes this by classifying signals, gating reliability, and requiring convergence across lanes.
We run two scores: PS_fast (early warning) and PS_confirmed (actuation-gated).
This is a phase detector, not a prophecy machine.

The One-Panel Model

The 6 signal classes (VocabularyOS)

RHETORIC: statements, threats, promises
POSTURE: assets positioned, resources allocated, “presence”
READINESS: alert state raised, staffing surge, C2 tempo
ORDER: directives, deadlines, authorizations, plans locked
ACTUATION: real-world lever pull (closures, mobilisations, restrictions)
KINETIC: irreversible contact (strike, halt, seizure, failure)

Two scores (always)

PS_fast: reacts early (includes weak/far signals with caps)
PS_confirmed: only moves hard on ORDER/ACTUATION/KINETIC with T1/T2 evidence

TTC compression (time-to-crossing)

Phase shifts are not just “how tense.” They are “how soon the next irreversible window opens.”

TTC_event: time to next plausible action window
TTC_policy: time to next decision / vote / directive
TTC_market: time to forced unwind / margin / funding roll

Hidden Fragility: what fools people

Rhetoric inflation: strong words with zero actuation
Posture mirage: presence without readiness or intent
Single-sensor delusion: one proxy (e.g., pizza) “proves” escalation
No convergence: signals don’t align across independent lanes
No backtest: weights drift until the model becomes astrology

Sensors & Thresholds

Near-node sensors (high value)

Official actions, deployments, closures, orders, rules, directives
Verified restrictions and enforceable commitments
Kinetic confirmations

Far-node sensors (low value unless convergent)

Traffic/food delivery proxies, social chatter, anecdotal anomalies
Tracker anomalies without baseline (AIS/flight)
“People saying” signals

The convergence rule (core safety)

Far-node signals cannot move PS_confirmed alone.
They only matter if they converge with near-node actuation/order tokens inside a TTC window.

Almost-Code (copy block)

			
PS Engine v1.0 :=
  classify signals into {RHET, POST, READY, ORDER, ACT, KIN}
  compute PS_fast (sensitive, capped far-node)
  compute PS_confirmed (actuation-gated)
  compute Confidence, Volatility, ConvergenceGap
  enforce: far-node never escalates confirmed alone
  enforce: irreversibility tokens dominate the scale

		

Failure Mode Trace (required)

			
No gating → rhetoric spikes score → false alarm → trust decay → model ignored → real actuation missed → late reaction → phase crossing.

How to run this with any LLM

Ask it to output:

tokens (id/class/tier)
which lane each token belongs to
PS_fast vs PS_confirmed
top drivers/brakes + TTC windows
trigger watchlist (what would push +10 / +25)

FAQ

Is this prediction? No. It’s phase detection (early warning + confirmation).
Why two scores? To separate “heat” from “actuation.”
Why convergence? To reduce false positives from single weak sensors.

Phase Monitor Universal Token Grammar (Master Glossary) (v1.0)

Summary (5 lines)

This page is the single master glossary that makes every Phase Monitor domain machine-readable.
All domains share the same Token schema, tiers, classes, dedup, and gating.
Domain packs only differ in token dictionaries (war/finance/tech/social/supply).
This prevents drift: same grammar → comparable outputs.
If a term is not defined here, it should not be used in snapshots.

1) Token Schema (canonical, universal)

			
Token := {
  id: STRING,                         # stable token name (dictionary-defined)
  actor: STRING,                      # optional: institution / state / market node
  domain: {WAR, FINANCE, TECH, SOCIAL, SUPPLY},
  lane: STRING,                       # domain-specific lane label
  class: {RHET, POST, READY, ORDER, ACT, KIN},
  polarity: {ESCALATE, DEESCALATE},
  base_weight: FLOAT,                 # dictionary-defined
  reliability_tier: {T1, T2, T3, T4},
  actuation_level: FLOAT,             # derived from class
  timestamp: ISO8601,
  evidence_ref: STRING,               # citation / link / document ref
  notes: STRING                       # optional explanation
}

		

2) The 6 Classes (VocabularyOS classification)

RHET — Rhetoric

Statements, threats, promises, commentary.

POST — Posture

Positioning assets/capacity without action: deployments, allocations, readiness hints.

READY — Readiness

Alert state changes, staffing surges, operational tempo, “prepared to act.”

ORDER — Orders & deadlines

Directives, authorizations, deadlines, “by X date,” explicit operational plans.

ACT — Actuation (lever pull)

Rules enforced, closures, controls, mobilisations, policy steps with immediate effect.

KIN — Kinetic / Irreversible contact

Direct engagement, failure, seizure, breach, default, coup—events that change the state space.

3) Reliability Tiers (hard)

			
T1 = primary wire / official docs / direct releases
T2 = reputable major outlets / method-backed OSINT orgs
T3 = credible individuals with baselines + reproducible data
T4 = rumours, screenshots, “people saying”, unverified dashboards

Reliability factors

			
Rel(T1)=1.00
Rel(T2)=0.80
Rel(T3)=0.55
Rel(T4)=0.30

4) Actuation Levels (derived from class)

			
Act(RHET)=0.20
Act(POST)=0.50
Act(READY)=0.70
Act(ORDER)=0.80
Act(ACT)=0.90
Act(KIN)=1.00

		

5) Impact Function (universal)

			
Sign(ESCALATE)=+1
Sign(DEESCALATE)=-1
Impact(token) =
  base_weight
  * Rel(reliability_tier)
  * Act(class)
  * Sign(polarity)

		

6) Dedup Rules (semantic duplicate suppression)

Why

Ten headlines about one event must not create ten points of score.

Rule

			
Dedup :=
  for tokens with same id + same actor + same theatre within 24h:
    keep the highest reliability instance
    drop the rest

Exception (allowed to add new token)

A new report can create a second token only if it changes:

duration (hours → days)
scope (local → corridor-wide)
class upgrade (POST→ORDER→ACT→KIN)
constraint set (new restrictions / enforceable rules)

7) Gating Rules (the core accuracy lock)

7.1 Far-node cap rule

Any token tagged as proxy in a dictionary:

can move PS_fast (capped)
cannot move PS_confirmed alone

7.2 Confirmed gate

			
Gate :=
  if exists token.class in {ORDER, ACT, KIN}
  and token.reliability_tier in {T1, T2}
  within last 72h:
    confirmed moves normally
  else:
    confirmed is damped (0.50x)

		

7.3 Convergence promotion

			
Promotion :=
  if (≥1 baseline-verified proxy signal)
  AND (≥2 near-node ORDER/ACT/KIN tokens, tier T1/T2)
  AND (inside TTC window)
  then:
    PS_confirmed += small_step (≤ +3)
    Confidence += +0.05

		

8) Confidence (how to compute it)

Confidence is not “how much we believe” — it’s evidence quality.

			
Confidence :=
  clamp(0,1,
    0.20
    + 0.15*(count(T1 tokens last 7d))
    + 0.10*(count(T2 tokens last 7d))
    - 0.10*(count(T4 tokens last 72h))
    - 0.05*(DedupDrops last 72h)
  )

		

Interpretation:

0.80–1.00: evidence-rich, actuation-confirmed regime
0.50–0.79: mixed, watch convergence
<0.50: noisy / proxy-heavy, do not overreact

9) Volatility (acceleration sensor)

			
Volatility :=
  HIGH if |ΔPS_fast_72h|≥10 or |ΔPS_confirmed_72h|≥8
  MED  if moderate
  LOW  otherwise

10) Failure Mode Trace (required)

			
No universal grammar → each domain invents terms → outputs incomparable → weights drift → false positives rise → model loses credibility.

LLM Run Prompt Pack (Copy/Paste) (v1.0)

Use these prompts with any LLM to produce consistent outputs.

Prompt 1 — Token Extraction (strict)

			
You are running Phase Monitor v1.0.
Task:
1) Extract tokens from the sources below.
2) Output ONLY valid JSON array of Token objects using the schema:
{ id, actor, domain, lane, class, polarity, base_weight, reliability_tier, actuation_level, timestamp, evidence_ref, notes }
Rules:
- Classify each token into RHET/POST/READY/ORDER/ACT/KIN.
- reliability_tier: T1/T2/T3/T4 based on source quality.
- actuation_level derived from class using:
RHET 0.20, POST 0.50, READY 0.70, ORDER 0.80, ACT 0.90, KIN 1.00
- If multiple sources report the same token within 24h, keep only the highest tier.
- Do NOT invent facts. If unclear, omit the token.
Sources:
[PASTE LINKS OR TEXT]

		

Prompt 2 — Dedup + Channel Mapping

			
Given the token JSON list, apply Dedup rules.
Then map tokens into channels:
STRUCTURAL_POSTURE, LEVER_ACTUATION, IRREVERSIBLE_EVENTS, STABILIZERS_BRAKES, TTC_COMPRESSION
Output:
1) Deduped token list
2) Channel buckets (token ids grouped)
3) Notes on any class upgrades (POST→ORDER etc.)

		

Prompt 3 — Score Computation (RUN output)

			
Compute RUN using Phase Monitor Engine v1.0.
Output:
PS_fast, PS_confirmed, Confidence, Volatility, ConvergenceGap,
ActiveWindows {TTC_event, TTC_policy, TTC_market, ReactionWindow},
TopDrivers (max 5), TopBrakes (max 5),
TriggerWatchlist {+10, +25, 80-100 entry}
Rules:
- PS_confirmed is actuation-gated (ORDER/ACT/KIN + T1/T2 within 72h).
- Far-node proxy tokens cannot move PS_confirmed alone.
- Apply Promotion only if convergence conditions are met.
- Keep output unemotive, structural.

		

Prompt 4 — Snapshot Post Generator (paste-ready)

			
Using the RUN output, generate a Phase Snapshot post using this fixed structure:
Header
Scores
TTC Windows
Channel Readout
Top Drivers
Top Brakes
Far-node Vector (optional)
Trigger Watchlist
Failure Mode Trace
Notes
How to run with any LLM
Do not add extra sections.

		

Phase Monitor is a Regeneration Sensor

Why tracking regime shifts is civilisation-critical (CivOS × VocabularyOS) (Z0–Z6 × P0–P3) (v1.0)

Summary (one screen)

Civilisation survives only if regeneration rate exceeds decay rate.
But regeneration fails first when coordination fails under load—because people misread the world and pull the wrong levers too late.

Phase Monitor is a CivOS control surface: it detects when a domain has shifted regimes (war/finance/tech/social/supply) before irreversible crossings, using VocabularyOS tokenization + gating + convergence so narratives don’t hijack decisions.

This is not “prediction.” It is early detection + actuation discipline.

1) CivOS coupling: why this is civilisation-critical

Core CivOS law (applied)

Let:

Ġ(t) = regeneration rate (capability repair + coordination repair + pipeline recovery)
Ḋ(t) = decay rate (role extinction + institutional drift + overload losses)
C(t) = civilisation capability stock (human pipeline mass, not money/infra)

Collapse happens when Ğ(t) < Ḋ(t) long enough to cross thresholds.

Phase Monitor’s job is to protect Ğ(t) by preventing:

late detection (TTC missed)
false alarms (trust collapse → real alarms ignored)
wrong actuation (pulling the wrong lever at the wrong time)

It is a regeneration sensor because it preserves the time advantage required for truncation + stitching (APRC).

2) VocabularyOS upgrade: why tokens matter (and what changed)

The newest VocabularyOS upgrades are exactly what Phase Monitor needs:

Upgrade A — Vocabulary is not a word list

VocabularyOS is Node × Bind × Weight × Z × P (language as a lattice).
Phase Monitor uses that to convert messy narratives into stable tokens with:

class (RHET/POST/READY/ORDER/ACT/KIN)
tier (T1–T4)
base_weight + actuation_level
dedup rules

Upgrade B — Anti-hallucination via gating

Two scores prevent narrative takeover:

PS_fast = early heat (can include proxies)
PS_confirmed = actuation-gated (ORDER/ACT/KIN + T1/T2)

This is the accuracy upgrade. It stops “pizza signals” from becoming truth, while still allowing far-node proxies to contribute through convergence.

3) The Phase Model: P0–P3 (how regimes move)

P3 — Stable band

Signals exist, but actuation is bounded and brakes hold.
PS_fast low, PS_confirmed low, convergence gap small.

P2 — Loaded but controlled

Posture shifts, rhetoric increases, but confirmed actuation is limited.
PS_fast rises; PS_confirmed rises only if order/actuation appears.

P1 — Drift & brittleness regime

The dangerous zone: coordination noise rises, proxies spike, narratives polarize.
Convergence gap often widens. False alarms become likely.

P0 — Fracture / irreversibility

KIN tokens: conflict, defaults, closures, coups, halts.
PS_confirmed jumps, TTC collapses.

Phase Monitor exists to keep systems from drifting P2→P1→P0 unnoticed, and to trigger truncation/stitching when possible.

4) Z0–Z6 mapping: why a “war/finance/tech” monitor is also EducationOS

Phase Monitor is a Z-ladder instrument:

Z0 (individual)

A parent, student, operator: “What is happening?”
Wrong lens → panic or complacency → poor decisions.

Z1 (family / micro-team)

Resource routing: time, attention, money, safety actions.
False alarms destroy trust; late alarms destroy safety.

Z2 (school / SME / local institution)

Operational continuity: closures, liquidity, staffing, compliance.
Phase Monitor protects planning under load.

Z3 (city)

City OS stability depends on:

supply corridors
financial plumbing
governance coherence
civil protection

Phase Monitor is a city-level early warning and actuation discipline tool.

Z4 (nation)

National levers: policy actuation, diplomacy, capital controls, mobilisation.
Phase Monitor provides structured decision inputs with TTC windows.

Z5 (world corridors)

Cross-border coupling: shipping, energy, finance, tech, conflict.
Phase Monitor prevents “single-lane blindness.”

Z6 (civilisation)

Civilisation stability depends on preventing irreversible threshold crossings across coupled lanes.
Phase Monitor is a CivilisationOS sensor primitive: it tracks the arrows (shocks) so the lattice can re-route and regenerate.

5) V/O/O role integration

Operator

Runs snapshots weekly, enforces dedup, refuses hype.
Outputs: PS_fast/PS_confirmed + trigger watchlist.

Oracle

Improves measurement:

calibrates weights via backtests
designs new sensors (baseline verified)
reduces convergence gap errors

Visionary

Expands the system:

new domains
new token dictionaries (versioned)
new corridor comparisons (Singapore ↔ NY ↔ Tokyo etc.)
…but only when Operators and Oracles keep it stable.

6) Failure mode trace (civilisation-critical)

			
Weak vocabulary lens → noisy tokenization → PS_confirmed becomes hype-driven
→ false alarms → trust collapse → true actuation ignored
→ TTC missed → irreversible crossing → regeneration too late.

7) What this enables (the “why now”)

With War/Finance/Tech/Social/Supply packs, you can:

track Iran–US escalation without being hijacked by rumor proxies
detect financial regime shifts by liquidity/policy actuation (not price noise)
detect tech inflections by deployment/adoption/capex/regulation (not benchmarks)
detect social stability shifts by comms shutdown / emergency law / institutional fracture
detect supply chain fractures by export bans / port closures / prolonged chokepoint disruption

This is a universal lattice monitor for shocks—so CivOS can do truncation + stitching instead of post-mortems.

8) Publish pack (where this page links)

Place this page at:
/phase-monitor/why-phase-monitor-is-civilisation-critical/

And link it from:

/phase-monitor/ (Master Hub)
CivOS core law page (Rate Dominance)
VocabularyOS “Genesis Selfie” and “Vocabulary is civilisation-critical”
EducationOS “Education is the regeneration organ” pillar

9) Minimal “Run With Any LLM” block (paste)

Prompt:

Tokenize sources using the Master Token Registry.
Tier (T1–T4) + class (RHET..KIN).
Dedup.
Compute PS_fast / PS_confirmed + TTC windows.
Output TriggerWatchlist.

(A2) VocabularyOS Signal Grammar

Tokenization, Reliability Gating, Noise Suppression (v1.0)

Summary (5 lines)

VocabularyOS converts messy narratives into computable tokens.
Tokens carry: actor, lane, class, reliability tier, actuation level, weight.
Reliability gating prevents low-quality sources from moving confirmed scores.
Noise suppression deduplicates repeated reporting of the same event.
This is how language becomes a stable sensor layer.

The Token (canonical)

Token schema

			
Token := {
  id: STRING,
  actor: {US, IRAN, PROXY, MULTI, OTHER},
  lane:  {MIL, DIP, ECON, INFO, TECH, SOC, LOG},
  class: {RHET, POST, READY, ORDER, ACT, KIN},
  polarity: {ESCALATE, DEESCALATE},
  base_weight: FLOAT,
  reliability_tier: {T1,T2,T3,T4},
  actuation_level: FLOAT,
  timestamp: ISO8601,
  evidence_ref: STRING
}

		

Reliability tiers (hard)

T1: primary wire / official docs / direct releases
T2: reputable major outlets / method-backed OSINT orgs
T3: credible individuals with baselines + reproducible data
T4: screenshots, rumours, tabloids, “people saying”

Reliability factor

			
Rel(T1)=1.00
Rel(T2)=0.80
Rel(T3)=0.55
Rel(T4)=0.30

Actuation levels (hard)

			
Act(RHET)=0.20
Act(POST)=0.50
Act(READY)=0.70
Act(ORDER)=0.80
Act(ACT)=0.90
Act(KIN)=1.00

		

Effective impact (the core math)

			
Impact(token) =
  base_weight
  * Rel(reliability_tier)
  * Act(class)
  * Sign(polarity)
Sign(ESCALATE)=+1
Sign(DEESCALATE)=-1

		

Noise suppression (semantic dedup)

Rule

If 20 articles describe the same actuation, count it once.

			
Dedup :=
  keep highest reliability instance within 24h
  only add new token if it changes:
    - duration
    - geography/theatre
    - class (POST→ORDER→ACT)
    - constraints (new rules / closures / directives)

		

Failure Mode Trace

			
No tokenization → narrative soup → double-counting → score spikes → false positives → model loses credibility → real actuation ignored.

How to run with any LLM

Prompt it:

“Extract tokens in the schema above from these sources.”
“Assign tier T1–T4; explain why.”
“Dedup same-event tokens; keep only escalations in class or duration.”

(A3) Universal Sensor Pack Directory

Near-Node vs Far-Node Signals Across Domains (v1.0)

Summary (5 lines)

Sensors are not equal.
Near-node sensors touch the real lever; far-node sensors are proxies.
Far-node signals are allowed to be noisy — but only useful under convergence.
This directory is a reusable lattice: war/finance/tech/social/supply chains.
Copy this pack and swap token dictionaries per domain.

Sensor families (universal)

1) Near-node actuation sensors (highest value)

Orders, directives, deadlines
Closures, restrictions, controls
Deployments, mobilisations
Enforceable agreements or withdrawals
Confirmed kinetic events

Moves: PS_fast ✅ PS_confirmed ✅

2) Operational readiness sensors

Alert levels, staffing surges, C2 tempo
War rooms, emergency committees
Exercises that alter real access/control

Moves: PS_fast ✅ PS_confirmed (only if T1/T2) ✅

3) Civil protection posture sensors

Embassy drawdowns / travel advisories
Airline route changes, evacuation planning
Insurance war-risk changes (if documented)

Moves: PS_fast ✅ PS_confirmed (via convergence) ⚠️

4) Airspace / maritime actuation proxies

NOTAM / NAVTEX / exclusion zones (documented)
AIS reroutes / convoy patterns (baseline required)
Tanker/airlift surges (baseline required)

Moves: PS_fast ✅ PS_confirmed (via convergence) ⚠️

5) Market microstructure sensors (confirmation, not cause)

Volatility spikes, credit spreads, funding stress
Options skew shifts (baseline required)
Risk premia jumps

Moves: PS_fast ✅ PS_confirmed (small, via convergence) ⚠️

6) Tempo proxies (weak)

Food delivery/traffic anomalies near decision hubs
Social chatter about “late nights”

Moves: PS_fast (tiny, capped) ✅ PS_confirmed ❌

Promotion rule (far-node → useful)

			
FarNodePromotion :=
  if (≥1 far-node in AIR/MAR/CIV/LOG)
  AND (≥2 T1/T2 near-node ORDER/ACT/KIN within 72h)
  then:
    PS_confirmed += small_step
    Confidence += bump
else:
    far-node affects PS_fast only

		

Failure Mode Trace

			
Treat proxies as proof → single-sensor hallucination → wrong regime call → credibility collapse → future warnings ignored.

(A4) Scoring Kernel v1.0

Phase-Shift Score Engine — Almost-Code Spec (v1.0)

Summary (5 lines)

This is the executable kernel: PS_fast, PS_confirmed, Confidence, Volatility.
Scores are built from channels with caps, fed by token impacts.
Confirmed score is actuation-gated.
Irreversibility events dominate the top of the scale.
TTC windows prevent premature decay after major actuation.

Channels (universal)

			
Channels :=
  STRUCTURAL_POSTURE   cap=25
  LEVER_ACTUATION      cap=20
  IRREVERSIBLE_EVENTS  cap=20
  STABILIZERS_BRAKES   cap=20  (subtractive)
  TTC_COMPRESSION      cap=15

		

Token → channel mapping (generic)

			
POST/READY/ORDER tokens -> STRUCTURAL_POSTURE
ACT tokens              -> LEVER_ACTUATION
KIN + irreversibles     -> IRREVERSIBLE_EVENTS
DIP/controls/brakes     -> STABILIZERS_BRAKES
deadlines/rollovers     -> TTC_COMPRESSION

		

Score computation

			
ChannelScore[c] = clamp(0, cap[c], Σ Impact(tokens mapped to c))
PS_fast =
  clamp(0,100,
    S_posture + S_actuation + S_irrev
    - S_brakes + S_ttc )
PS_confirmed =
  clamp(0,100,
    Gate(S_posture) + Gate(S_actuation) + Gate(S_irrev)
    - Gate(S_brakes) + Gate(S_ttc) )

		

Gate rule (confirmed)

			
Gate(x):
  if exists token.class in {ORDER, ACT, KIN} with tier in {T1,T2} in last 72h:
     return x
  else:
     return 0.50*x

		

Irreversibility multiplier

			
IRREVERSIBLE := {KINETIC_CONFIRM, PROLONGED_CLOSURE, EMBASSY_BREACH, DEFAULT/FAILURE, CAPITAL_CONTROLS}
Mult =
  1.00 + 0.25 * count(IRREVERSIBLE tokens, last 7d, tier in {T1,T2})
PS_confirmed := clamp(0,100, PS_confirmed * Mult)

TTC window clamp (anti “decay too early”)

			
If MajorActuation (ORDER/ACT/KIN, tier T1/T2) at t0:
  Window := [t0, t0 + 7d]  # configurable
During Window:
  PS_confirmed(t) >= PS_confirmed(t-24h) - 10
unless StrongBrake exists (enforceable deal/monitoring/withdrawal):
  clamp relaxes to -20

		

Diagnostics

			
ConvergenceGap := |PS_fast - PS_confirmed|
Volatility := HIGH if |ΔPS_fast_72h|>=10 or |ΔPS_confirmed_72h|>=8
           := MED  if moderate
           := LOW  otherwise

Failure Mode Trace

			
No actuation gate → confirmed behaves like fast → narrative heat becomes “truth” → repeated false alarms → future true alarms ignored.

(A5) Backtesting Doctrine

Calibrating Weights Without Fooling Ourselves (v1.0)

Summary (5 lines)

Weights are not opinions; they are fitted against truth spines.
Backtests prevent narrative drift and confirmation bias.
We calibrate to catch phase shifts early while limiting false spikes.
We never “explain after the fact” without logging missed signals.
A model without backtests is just storytelling.

The truth spine method (canonical)

Choose an event (war escalation, crash, tech adoption jump).
Write the ground-truth timeline (dates + irreversible actions).
Collect signals as they existed then (avoid hindsight leakage).
Tokenize + tier them.
Run the engine day-by-day.
Compare: did PS_confirmed spike on irreversibility? did PS_fast rise early?

What “good” looks like

PS_fast rises 1–7 days before the crossing window
PS_confirmed stays disciplined (no big moves on rhetoric)
Irreversibility events dominate the 80–100 band
Convergence gap shrinks near true crossings (fast and confirmed agree)

Avoiding overfit (hard rules)

Don’t tune weights to one case only. Use 3+ cases per domain.
Keep caps stable; only adjust token base weights and promotion thresholds.
Log false positives and false negatives explicitly.

Calibration levers (allowed)

Base weights (per token)
Reliability tier mapping
Promotion rule threshold (how many convergent signals required)
TTC clamp window length (theatre dependent)

Calibration levers (not allowed)

“Explaining away” misses by inventing new tokens after the fact
Moving goalposts (changing classes or tiers retroactively)
Raising far-node weights until they act like near-nodes

Failure Mode Trace

			
No truth spine → hindsight leakage → weights tuned to yesterday → false confidence → next regime shift surprises the system.

Minimal backtest output format

			
BacktestRun := {
  event_name,
  truth_spine_dates,
  PS_fast_series,
  PS_confirmed_series,
  first_warning_date,
  crossing_date,
  false_spike_count,
  missed_signal_notes,
  calibrated_weight_changes
}

		

(B1) Weekly Snapshot Template

The CivOS Weekly Phase Snapshot Format (Copy/Paste Template) (v1.0)

Summary (what this page is)

This page is a standard output format for any situation you are tracking (war, finance, tech, social stability).
It forces discipline: two scores, convergence gap, TTC windows, and a trigger watchlist.
It prevents narrative drift by making every update comparable week-to-week.

Snapshot Header (fixed)

Window: YYYY-MM-DD → YYYY-MM-DD (Timezone)
Theatre / Domain: (e.g., Iran–US / War) or (Global Credit / Finance)
Engine Version: v1.0
Sources Policy: T1/T2 primary; T3/T4 capped fast-only

1) Scores (always 2)

PS_fast: _ / 100 PS_confirmed: _ / 100

Confidence: _ (0.00–1.00) Volatility: LOW / MED / HIGH Convergence Gap: |PS_fast − PS_confirmed| = _

Interpretation (fixed rules)

Gap > 15: narrative heat / weak confirmation regime
Gap < 8: confirmed regime (either escalation or stabilisation)

2) Active TTC Windows

TTC_event: (time to next plausible action window)
TTC_policy: (time to next decision / vote / directive)
TTC_market: (time to next forced roll / margin / funding stress)

Retaliation / reaction window active? YES / NO
(if YES: score decay is clamped unless StrongBrake exists)

3) Top Drivers (max 5)

List token ids only, then one-line evidence each.

TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref

4) Top Brakes / Stabilizers (max 5)

TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref

5) Channel Readout (capped)

STRUCTURAL_POSTURE: _ / 25 LEVER_ACTUATION: _ / 20
IRREVERSIBLE_EVENTS: _ / 20 STABILIZERS_BRAKES: _ / 20 (subtractive)
TTC_COMPRESSION: __ / 15

6) Far-Node Sensor Vector (fast-only, capped)

(Only include if you have baseline + reproducible data.)

AIRSPACE_ACTUATION_PROXY: _ / 10 MARITIME_ACTUATION_PROXY: _ / 10
CIVIL_PROTECTION_POSTURE: _ / 10 LOGISTICS_RAMP: _ / 10
OSINT_TEMPO_PROXY: _ / 5 MARKET_RISK_SENSOR: _ / 5

Convergence Hit? YES / NO
If YES: state the convergent set (max 1 line)

7) Trigger Watchlist (the most important section)

7.1 +10 triggers (moderate jump)

Any one of:

ORDER class token (T1/T2) that tightens TTC materially
ACTUATION token that increases duration/scope of a lever pull
confirmed civil protection shift (embassy drawdown / evacuation advisory)

7.2 +25 triggers (strong jump)

Any one of:

ATTRIBUTED_KINETIC_ACTION (confirmed)
PROLONGED_CHOKEPOINT_CLOSURE (hours → day(s) with verification)
EMBASSY_BREACH_SIEGE or equivalent institutional breach
CAPITAL_CONTROLS / market halt (domain dependent)

7.3 80–100 band entry (irreversibility regime)

Requires:

≥1 irreversibility token (T1/T2)
AND
convergence gap < 8
AND
TTC_event ≤ 72h (or already crossed)

8) Failure Mode Trace (required)

			
If we remove actuation gating → PS_confirmed becomes hype-driven → false alarms → trust collapse → true phase shift missed.

9) How to run this snapshot with any LLM

Prompt:

“Extract tokens in schema; assign tier and class.”
“Compute PS_fast and PS_confirmed using v1.0 rules.”
“Dedup same-event reports; keep only class upgrades/duration changes.”
“Output TopDrivers/Brakes + TTC windows + Trigger Watchlist.”

(B2) Snapshots Index

Phase Snapshots Index (War / Finance / Tech / Social / Supply Chain) (v1.0)

Purpose

This index is the navigation hub that makes your system legible to humans and LLMs.
Every domain uses the same snapshot template, so comparisons are clean.

1) War / Geopolitics

War Sensor Pack (v1.0) — (link)
War Token Dictionary (v1.0) — (link)
War Backtests Index — (link)
Weekly War Snapshots — (link)

Active theatres (examples)

Iran–US (weekly) — (link)
Red Sea / shipping lane (weekly) — (link)
East Asia tension corridor (weekly) — (link)

2) Finance / Markets

Finance Sensor Pack (v1.0) — (link)
Finance Token Dictionary (v1.0) — (link)
Finance Backtests Index — (link)
Weekly Finance Snapshots — (link)

Lanes (examples)

Global Liquidity (weekly) — (link)
Credit Stress (weekly) — (link)
FX / Capital Flow (weekly) — (link)

3) Technology / AI / Energy

Tech Sensor Pack (v1.0) — (link)
Tech Token Dictionary (v1.0) — (link)
Tech Backtests Index — (link)
Monthly Tech Snapshots — (link)

Lanes (examples)

AI capability acceleration (monthly) — (link)
Semiconductor chokepoints (monthly) — (link)
Energy storage / batteries (monthly) — (link)

4) Social Stability / Governance

Social Sensor Pack (v1.0) — (link)
Social Token Dictionary (v1.0) — (link)
Social Backtests Index — (link)
Weekly Social Snapshots — (link)

5) Supply Chains / Critical Infrastructure

Supply Chain Sensor Pack (v1.0) — (link)
Supply Chain Token Dictionary (v1.0) — (link)
Supply Chain Backtests Index — (link)
Weekly Supply Chain Snapshots — (link)

Index Governance (so it stays clean)

One snapshot per domain per cadence (weekly/monthly).
Every snapshot must include: PS_fast, PS_confirmed, Confidence, Volatility, ConvergenceGap, TTC windows, Trigger Watchlist.
No emotional language. No sensational titles.
Backtests are the only place you discuss calibration changes.

(B3) Trigger Watchlist Design

The “What Would Move the Score” Block (Reusable) (v1.0)

Purpose

This block tells readers exactly what tokens would shift the system.
It prevents hindsight rationalization and forces forward discipline.

Universal Trigger Ladder

Level 1 — Soft escalation (+5 fast)

increased rhetoric frequency (still RHET class)
unverified proxy anomalies (T3/T4)

Moves: PS_fast only

Level 2 — Posture shift (+10 fast, +5 confirmed if gated)

visible redeployments
readiness alerts
staffing surge indicators (T1/T2)

Moves: both, but confirmed is gated

Level 3 — Orders & deadlines (+10 confirmed)

explicit “by X date” directives
formal authorization statements
written proposals / formal rejection notices (domain dependent)

Moves: PS_confirmed strongly

Level 4 — Actuation (+25 confirmed)

chokepoint closure / capital controls / export bans
verified restrictions that alter real flows

Moves: PS_confirmed strongly (often triggers TTC clamp)

Level 5 — Irreversibility (80–100 band)

attributed kinetic exchange
prolonged closure (duration regime change)
system failure / default / coup / halt (domain dependent)

Moves: both converge; gap shrinks

Failure Mode Trace

			
No trigger ladder → readers can’t tell what matters → everything feels important → nothing is important → real actuation surprises the system.

War Pack v1.0 (CivOS × VocabularyOS)

(C1-1) War Sensor Pack v1.0

War / Geopolitics Sensor Pack (Near-Node + Far-Node) (v1.0)

Summary (5 lines)

This pack lists all sensors used to detect war-phase transitions.
Sensors are split into Near-Node (high value) and Far-Node (proxy).
Far-nodes are capped and only matter through convergence.
This pack supports the PS Engine v1.0 outputs: PS_fast / PS_confirmed / TTC windows.
Clone this pack for any theatre (Iran–US, Red Sea, East Asia).

0) Hard rules (non-negotiable)

Far-node signals never move PS_confirmed alone.
Confirmed score only moves hard on ORDER / ACTUATION / KINETIC (T1/T2).
Convergence > single-sensor.
Dedup same event (do not double count repeated headlines).
Keep outputs unemotive: structure only.

1) Near-Node Sensors (highest value)

1.1 Orders & directives (ORDER class)

What it looks like

explicit deployment deadlines (“fully deployed by X date”)
authorization language (expanded ROE, operational plan confirmed)
formal contingency planning statements

Why it matters
Orders compress TTC and often precede actuation.

Moves

PS_fast ✅
PS_confirmed ✅ (strong)

1.2 Force posture changes (POSTURE/READINESS class)

Examples

carrier strike group repositioning
bomber/fighter redeployment
air defense repositioning
troop reinforcement to region
war-room / Situation Room tempo (C2)

Why it matters
Posture is necessary but not sufficient; readiness determines if posture is “real.”

Moves

PS_fast ✅
PS_confirmed ✅ (only if T1/T2 and class is READINESS/ORDER)

1.3 Lever actuation (ACTUATION class)

Examples

chokepoint closures / exclusion zones
sanctions enforcement steps with immediate effect
shipping restrictions / interdictions
new restrictions on movement/airspace/sea lanes

Why it matters
This is the system pulling a real lever.

Moves

PS_fast ✅
PS_confirmed ✅ (+25 ladder candidate)

1.4 Civil protection posture (POSTURE/ORDER class)

Examples

embassy drawdowns / dependents authorized departure
urgent travel advisories (“leave immediately”)
evacuation staging / airlift for civilians

Why it matters
States protect their people when risk becomes real.

Moves

PS_fast ✅
PS_confirmed ⚠️ (via convergence; can be strong if T1/T2)

1.5 Kinetic confirmations (KINETIC class)

Examples

attributed strikes
missile launches/impacts confirmed
seizures / direct engagements
casualties acknowledged (even if numbers revised later)

Why it matters
This is irreversibility.

Moves

PS_fast ✅
PS_confirmed ✅ (80–100 band entry candidate)

2) Far-Node Sensors (proxy layer; capped; convergence only)

2.1 Airspace & flight signals (AIRSPACE_ACTUATION_PROXY)

Examples

documented NOTAMs / restricted areas
tanker surges (refueling patterns)
strategic airlift clusters
unusual medevac aircraft positioning

Use rule

must have baseline (compare to same weekday/time over 4–8 weeks)
must be reproducible (multiple trackers / independent confirmations)

Moves

PS_fast ✅
PS_confirmed ⚠️ only via convergence

2.2 Maritime signals (MARITIME_ACTUATION_PROXY)

Examples

NAVTEX warnings / drill zones
AIS reroutes / convoy patterns
shipping insurance war-risk signals (if documented)
escort announcements / interdiction posture

Use rule

baseline required; distinguish drills vs prolonged restrictions

Moves

PS_fast ✅
PS_confirmed ⚠️ only via convergence

2.3 Logistics ramp proxies (LOGISTICS_RAMP)

Examples

sudden munition resupply indicators (if verifiable)
expedited contracting language (method-backed)
surge in fuel/parts movement (rarely visible publicly)

Moves

PS_fast ✅
PS_confirmed ⚠️ only via convergence

2.4 Tempo proxies (OSINT_TEMPO_PROXY) — weakest

Examples

food delivery spikes near hubs
anecdotal “late night” chatter
single-point traffic anomalies

Use rule

never raise PS_confirmed
PS_fast impact capped (max +1/day from T4)

Moves

PS_fast ✅ (tiny)
PS_confirmed ❌

2.5 Market risk sensor (MARKET_RISK_SENSOR)

Examples

oil risk premium spike
shipping rates / war-risk insurance
FX stress in regional currencies

Use rule
Market confirms perceived risk; it does not prove actuation.

Moves

PS_fast ✅
PS_confirmed ⚠️ (small, via convergence)

3) Convergence rule (War Pack)

			
WarConvergence :=
  if (≥1 FarNode in {AIRSPACE, MARITIME, CIVIL, LOGISTICS})
  AND (≥2 NearNode tokens in class {ORDER, ACTUATION, KINETIC} with tier {T1,T2})
  AND (within TTC ≤ 72h)
  then:
    PS_confirmed += small_step (≤ +3)
    Confidence += +0.05
    Volatility := HIGH
else:
    far-nodes affect PS_fast only

		

4) Failure Mode Trace (required)

			
Proxy treated as proof → false alarm → trust decay → real actuation ignored → late response → irreversible phase crossing.

5) How to run this pack with any LLM

Prompt:

“Extract war tokens using War Token Dictionary v1.0; assign tier/class.”
“Compute PS_fast / PS_confirmed using Engine v1.0.”
“Output TTC_event, TTC_policy, RetaliationWindow, TriggerWatchlist.”

(C1-2) War Token Dictionary v1.0

War / Geopolitics Token Dictionary (Copy/Paste) (v1.0)

Summary (5 lines)

This dictionary is the canonical token set for war-phase detection.
Every token has a class (RHET/POST/READY/ORDER/ACT/KIN) and a lane (MIL/DIP/ECON/CIV/LOG/INFO).
Weights are base weights (before reliability × actuation).
This list is deliberately finite and stable. Extend by versioning forward only.

0) Token format (canonical)

TokenDef := { id, lane, class, polarity, base_weight, notes }

1) Highest-impact irreversibility tokens (80–100 band drivers)

ATTRIBUTED_KINETIC_ACTION

lane: MIL | class: KIN | polarity: ESCALATE | base_weight: 20
notes: confirmed strike with attribution (state/proxy)

MISSILE_ATTACK_CONFIRMED

lane: MIL | class: KIN | polarity: ESCALATE | base_weight: 20
notes: ballistic/cruise/drone strike confirmed as attack (not test)

NAVAL_ENGAGEMENT_CONFIRMED

lane: MIL | class: KIN | polarity: ESCALATE | base_weight: 18
notes: shots fired, vessel hit, boarding in combat conditions

EMBASSY_BREACH_SIEGE

lane: CIV | class: KIN | polarity: ESCALATE | base_weight: 18
notes: compound breached/sieged; a strong precursor + irreversibility marker

PROLONGED_CHOKEPOINT_CLOSURE

lane: ECON | class: ACT | polarity: ESCALATE | base_weight: 18
notes: chokepoint disruption shifts from hours → day(s)+

2) Actuation tokens (lever pulls; +25 ladder candidates)

CHOKEPOINT_ACTUATION

lane: ECON/MIL | class: ACT | polarity: ESCALATE | base_weight: 18
notes: temporary closure/restriction/exclusion zone at chokepoint

INTERDICTION_SEIZURE

lane: MIL/ECON | class: ACT | polarity: ESCALATE | base_weight: 16
notes: seizure/boarding/interdiction with enforcement

AIRSPACE_RESTRICTION_ACTUATION

lane: MIL | class: ACT | polarity: ESCALATE | base_weight: 14
notes: enforceable no-fly / restricted corridors with real constraints

SANCTIONS_ENFORCEMENT_STEP

lane: ECON | class: ACT | polarity: ESCALATE | base_weight: 12
notes: sanctions move from rhetoric → enforceable operational step

MASS_MOBILIZATION

lane: MIL | class: ACT | polarity: ESCALATE | base_weight: 16
notes: call-up / mobilization beyond routine readiness

3) Orders & TTC compression tokens (confirmed movers)

FULL_DEPLOYMENT_DIRECTIVE

lane: MIL | class: ORDER | polarity: ESCALATE | base_weight: 15
notes: “by X date” deployment / readiness directive (TTC compression)

STRIKE_AUTHORIZATION_SIGNAL

lane: MIL | class: ORDER | polarity: ESCALATE | base_weight: 16
notes: formal authorization language, expanded ROE, strike window set

OPERATION_WEEKS_LONG_PLANNING

lane: MIL | class: ORDER | polarity: ESCALATE | base_weight: 12
notes: planning for sustained operations (not a one-off)

RETALIATION_EXPECTED_OFFICIAL

lane: MIL | class: READY | polarity: ESCALATE | base_weight: 10
notes: official expectation of retaliation changes readiness posture

4) Force posture & readiness tokens (fast movers; confirmed gated)

CARRIER_STRIKE_GROUP_POSITIONING

lane: MIL | class: POST | polarity: ESCALATE | base_weight: 10

BOMBER_OR_FIGHTER_REDEPLOYMENT

lane: MIL | class: POST | polarity: ESCALATE | base_weight: 9

AIR_DEFENSE_REPOSITIONING

lane: MIL | class: POST | polarity: ESCALATE | base_weight: 8

C2_WAR_ROOM_TEMPO

lane: MIL | class: READY | polarity: ESCALATE | base_weight: 8
notes: situation room / emergency council tempo (T1/T2 only)

LIVE_FIRE_DRILL_NEAR_CHOKEPOINT

lane: MIL | class: ACT | polarity: ESCALATE | base_weight: 6
notes: drills matter more when paired with restrictions

5) Civil protection tokens (stabilizer or escalation markers)

EMBASSY_DRAWDOWN

lane: CIV | class: ORDER | polarity: ESCALATE | base_weight: 10

TRAVEL_ADVISORY_LEAVE_IMMEDIATELY

lane: CIV | class: ORDER | polarity: ESCALATE | base_weight: 10

EVACUATION_STAGING

lane: CIV/LOG | class: READY | polarity: ESCALATE | base_weight: 9

6) Diplomatic brake tokens (subtractive; confirmed if enforceable)

TALKS_CONFIRMED

lane: DIP | class: POST | polarity: DEESCALATE | base_weight: 8

PROPOSAL_SUBMITTED_WRITTEN

lane: DIP | class: ORDER | polarity: DEESCALATE | base_weight: 9

ENFORCEABLE_MONITORING_MECHANISM

lane: DIP | class: ACT | polarity: DEESCALATE | base_weight: 14
notes: verification regime + compliance mechanism

DECONFLICTION_HOTLINE_ACTIVE

lane: DIP/MIL | class: ACT | polarity: DEESCALATE | base_weight: 10

DRAW_DOWN_CONFIRMED

lane: MIL | class: ACT | polarity: DEESCALATE | base_weight: 12
notes: verifiable reduction in posture/readiness

7) Far-node proxy tokens (fast-only, capped)

NOTAM_EXCLUSION_ZONE_PROXY

lane: MIL | class: ACT | polarity: ESCALATE | base_weight: 6
notes: only if NOTAM text is sourced (baseline helps)

TANKER_SURGE_PROXY

lane: MIL/LOG | class: READY | polarity: ESCALATE | base_weight: 5
notes: baseline required

AIS_REROUTE_PROXY

lane: ECON | class: POST | polarity: ESCALATE | base_weight: 5
notes: baseline required; confounded by weather/drills

OSINT_TEMPO_PROXY_PIZZA_TRAFFIC

lane: INFO | class: POST | polarity: ESCALATE | base_weight: 2
notes: T3/T4 only; never moves confirmed

MARKET_RISK_SENSOR_OIL_SPIKE

lane: ECON | class: POST | polarity: ESCALATE | base_weight: 4
notes: confirmation only; never decisive alone

8) Failure Mode Trace (required)

			
Unbounded token list → weight drift → everything becomes “signal” → false positives dominate → model becomes unusable.

9) “Run” instructions (for your weekly war snapshot)

Extract tokens from the week.
Tier them (T1–T4).
Dedup same-event repeats.
Compute PS_fast + PS_confirmed.
Output TopDrivers/Brakes, TTC windows, TriggerWatchlist.

If you reply Next, I’ll generate the Finance Pack v1.0 (Sensor Pack + Token Dictionary) in the same format, so you can immediately track sudden changes to markets with the same lattice engine.

Finance Pack v1.0 (CivOS × VocabularyOS)

(C2-1) Finance Sensor Pack v1.0

Financial Regime Shift Sensor Pack (Near-Node + Far-Node) (v1.0)

Summary (5 lines)

Financial “shocks” follow the same phase structure: noise → positioning → liquidity stress → forced action → irreversibility → new regime.
This pack detects regime shift, not day-to-day price moves.
Near-node sensors focus on liquidity, credit, funding, policy actuation.
Far-nodes are proxies and only matter through convergence.
Outputs feed PS Engine v1.0: PS_fast / PS_confirmed / Confidence / Volatility / TTC windows.

0) Hard rules

Markets are not a single lane: separate Liquidity / Credit / Volatility / Policy / Plumbing.
Price move ≠ regime shift unless it couples to funding/liquidity actuation.
Far-node proxies never move PS_confirmed alone.
Irreversibility tokens (halts, defaults, capital controls, emergency facilities) dominate 80–100.
Always track ΔPS (72h/7d) — acceleration is often more informative than level.

1) Near-Node Sensors (highest value)

1.1 Liquidity & funding stress (core)

Examples

repo stress / funding rates spike
widening bid-ask spreads in key instruments
money market dislocation (when documented)
margin requirement increases (verified)

Why it matters
Liquidity withdrawal is the main mechanism behind cascades.

Moves

PS_fast ✅
PS_confirmed ✅ (strong when T1/T2 or primary data)

1.2 Credit fracture

Examples

credit spreads widen sharply across grades
CDS blowouts in systemically important names
bank funding stress signals (documented)

Moves

PS_fast ✅
PS_confirmed ✅ (via convergence with liquidity/policy)

1.3 Volatility regime change

Examples

implied vol spike + persistent term-structure inversion
correlation spikes (everything moves together)
repeated limit down / circuit breakers

Moves

PS_fast ✅
PS_confirmed ⚠️ (needs actuation / liquidity coupling)

1.4 Policy actuation (central banks / regulators)

Examples

emergency rate decision / surprise meeting
liquidity facility activation / expansion
regulatory short-selling bans / capital controls
deposit guarantees / bank resolution steps

Why it matters
This is direct actuation; it often marks regime boundaries.

Moves

PS_fast ✅
PS_confirmed ✅ (+25 ladder candidate)

1.5 Institutional failure / halt (irreversibility)

Examples

bank failure, forced merger, resolution
exchange trading halt / market closure
default events, payment failure
capital controls

Moves

PS_fast ✅
PS_confirmed ✅ (80–100 band candidate)

2) Far-Node Sensors (proxy layer; capped)

2.1 Options positioning proxies

Examples

sudden put skew shifts, gamma exposure flips
large block hedging behavior (if method-backed)

Use rule
Baseline required; don’t treat one-day flow as regime shift.

Moves

PS_fast ✅
PS_confirmed ⚠️ only via convergence

2.2 Bank chatter / insider signals

Examples

anecdotal “risk committees active”
rumor of margin calls without confirmation

Moves

PS_fast (tiny) ✅
PS_confirmed ❌ unless verified by T1/T2

2.3 Real-economy stress proxies

Examples

shipping rates spikes, commodity dislocations
sudden FX shortages in key corridors

Moves

PS_fast ✅
PS_confirmed ⚠️ only via convergence

3) Convergence rule (Finance Pack)

			
FinanceConvergence :=
  if (≥1 FarNode in {OPTIONS_PROXY, REAL_ECON_PROXY})
  AND (≥2 NearNode tokens among {LIQUIDITY_WITHDRAWAL, FUNDING_STRESS, POLICY_ACTUATION, CREDIT_FRACTURE} with tier {T1,T2})
  AND (within TTC ≤ 72h)
  then:
    PS_confirmed += small_step (≤ +3)
    Confidence += +0.05
    Volatility := HIGH
else:
    far-nodes affect PS_fast only

		

4) Failure Mode Trace

			
Price-only model → headline-chasing → misses liquidity withdrawal → cascade begins → “surprise crash” narrative → late intervention.

5) How to run this pack with any LLM

Prompt:

“Extract finance tokens using Finance Token Dictionary v1.0; assign tier/class.”
“Compute PS_fast / PS_confirmed.”
“Output TTC_market (funding rollovers / margin windows) + TriggerWatchlist.”

(C2-2) Finance Token Dictionary v1.0

Financial Regime Shift Token Dictionary (Copy/Paste) (v1.0)

Summary (5 lines)

This dictionary defines stable tokens for detecting financial regime shifts.
Tokens are grouped by Liquidity, Credit, Volatility, Policy, Irreversibility.
Weights are base weights before reliability × actuation.
Keep the list finite; version forward only.

0) Token format

TokenDef := { id, lane, class, polarity, base_weight, notes }

1) Irreversibility tokens (80–100 band drivers)

BANK_FAILURE_OR_RESOLUTION

lane: FIN | class: KIN | polarity: ESCALATE | base_weight: 20
notes: bank failure, resolution, forced merger, bail-in

EXCHANGE_TRADING_HALT_OR_CLOSURE

lane: FIN | class: KIN | polarity: ESCALATE | base_weight: 18

SOVEREIGN_DEFAULT_OR_PAYMENT_FAILURE

lane: FIN | class: KIN | polarity: ESCALATE | base_weight: 20

CAPITAL_CONTROLS_ACTUATED

lane: POLICY/FIN | class: ACT | polarity: ESCALATE | base_weight: 18

DEPOSIT_GUARANTEE_EMERGENCY

lane: POLICY | class: ACT | polarity: DEESCALATE | base_weight: 14
notes: stabilizer but marks regime boundary; treat as brake + “phase marker”

2) Policy actuation tokens (+25 ladder candidates)

EMERGENCY_LIQUIDITY_FACILITY_ACTIVATED

lane: POLICY | class: ACT | polarity: DEESCALATE | base_weight: 16
notes: stabilizer, but indicates severe stress

SURPRISE_RATE_DECISION

lane: POLICY | class: ACT | polarity: DEESCALATE | base_weight: 12

REGULATORY_SHORT_SELLING_BAN

lane: POLICY | class: ACT | polarity: DEESCALATE | base_weight: 10
notes: stabilizer; often appears in crisis windows

FORWARD_GUIDANCE_SHIFTS_HARD

lane: POLICY | class: ORDER | polarity: ESCALATE/DEESCALATE | base_weight: 10
notes: use polarity based on tightening vs easing

3) Liquidity & funding stress tokens (core)

LIQUIDITY_WITHDRAWAL

lane: FIN | class: ACT | polarity: ESCALATE | base_weight: 16
notes: measurable liquidity drain / market-making retreat

REPO_STRESS_SPIKE

lane: FIN | class: ACT | polarity: ESCALATE | base_weight: 14

BID_ASK_WIDENS_SYSTEMIC

lane: FIN | class: ACT | polarity: ESCALATE | base_weight: 12

MARGIN_REQUIREMENTS_RAISED

lane: FIN | class: ORDER | polarity: ESCALATE | base_weight: 12

FORCED_DELEVERAGING_SIGNAL

lane: FIN | class: READY | polarity: ESCALATE | base_weight: 10
notes: forced unwind signs (T1/T2 preferred)

4) Credit fracture tokens

CREDIT_SPREADS_WIDEN_SHARP

lane: FIN | class: ACT | polarity: ESCALATE | base_weight: 12

CDS_BLOWOUT_SYSTEMIC_NAME

lane: FIN | class: ACT | polarity: ESCALATE | base_weight: 12

BANK_FUNDING_STRESS

lane: FIN | class: ACT | polarity: ESCALATE | base_weight: 14

5) Volatility regime tokens

IMPLIED_VOL_SPIKE_PERSISTENT

lane: FIN | class: ACT | polarity: ESCALATE | base_weight: 10

CORRELATION_SPIKE_ONE_FACTOR

lane: FIN | class: READY | polarity: ESCALATE | base_weight: 8

CIRCUIT_BREAKERS_TRIGGERED

lane: FIN | class: KIN | polarity: ESCALATE | base_weight: 14

6) Currency / flow fracture tokens

FX_SWAP_BASIS_WIDENS

lane: FIN | class: ACT | polarity: ESCALATE | base_weight: 10

RESERVE_DRAIN_ACCELERATES

lane: FIN/POLICY | class: ACT | polarity: ESCALATE | base_weight: 12

FX_CONTROLS_TIGHTENED

lane: POLICY | class: ACT | polarity: ESCALATE | base_weight: 14

7) Stabilizers / brake tokens (subtractive)

COORDINATED_CENTRAL_BANK_ACTION

lane: POLICY | class: ACT | polarity: DEESCALATE | base_weight: 14

SWAP_LINES_EXPANDED

lane: POLICY | class: ACT | polarity: DEESCALATE | base_weight: 14

BACKSTOP_PROGRAM_EXPANDED

lane: POLICY | class: ACT | polarity: DEESCALATE | base_weight: 12

8) Far-node proxy tokens (fast-only, capped)

OPTIONS_SKEW_SHIFT_PROXY

lane: FIN | class: READY | polarity: ESCALATE | base_weight: 5
notes: baseline required

RUMORED_MARGIN_CALLS_PROXY

lane: INFO | class: RHET | polarity: ESCALATE | base_weight: 3
notes: T3/T4; never moves confirmed

INSIDER_SELLING_CLUSTER_PROXY

lane: INFO | class: POST | polarity: ESCALATE | base_weight: 4
notes: confounded; baseline required

REAL_ECON_FREIGHT_DISLOCATION_PROXY

lane: ECON | class: POST | polarity: ESCALATE | base_weight: 5

9) Failure Mode Trace

			
Volatility-only lens → misses funding stress → forced deleveraging begins → liquidity vanishes → crash appears “sudden.”

Technology Pack v1.0 (CivOS × VocabularyOS)

(C3-1) Tech Sensor Pack v1.0

Technology Inflection Sensor Pack (Capability → Adoption → Actuation → Irreversibility) (v1.0)

Summary (5 lines)

World-changing technology transitions follow a repeatable chain: capability break → deployment → adoption threshold → capital/supply re-routing → regulation response → irreversible lock-in.
This pack detects inflection, not hype cycles.
Near-node sensors emphasize capability evidence, scale deployment, capex + supply constraints, and regulatory actuation.
Far-node sensors (buzz, social chatter) are capped and only matter through convergence.
Outputs feed PS Engine v1.0: PS_fast / PS_confirmed / Confidence / Volatility / TTC windows.

0) Hard rules

Benchmarks alone don’t prove world change unless they translate to deployment/adoption.
Adoption is an actuation event (enterprise migration waves, mandates, standardization).
Capex + supply-chain rerouting is a high-value confirmation lane.
Regulation is a phase marker (ban/mandate/export control) and must be tracked as actuation.
Far-nodes (buzz) never move PS_confirmed alone.

1) Near-Node Sensors (highest value)

1.1 Capability evidence (CAPABILITY lane)

Examples

reproducible benchmark breakthroughs (method + baseline + peer replication)
capability crosses a known threshold (e.g., cost/performance parity, latency barrier)
stable performance under stress (robustness, safety, generalization)

Moves

PS_fast ✅
PS_confirmed ⚠️ (only if reproducible + T1/T2 technical sources)

1.2 Deployment at scale (DEPLOY lane)

Examples

enterprise rollout (large orgs migrate workflows)
platform-level integration (OS/hardware stack adoption)
sustained user growth or throughput (measured, not claimed)

Moves

PS_fast ✅
PS_confirmed ✅ (ORDER/ACT class signals often exist here)

1.3 Adoption threshold & standards lock-in (ADOPT lane)

Examples

industry standards adopted
mandated interfaces / compliance requirements
education curriculum integration (for truly civilisational tech)

Moves

PS_fast ✅
PS_confirmed ✅ (often +25 ladder candidate when mandates appear)

1.4 Capex re-routing & supply constraint (CAPEX/SUPPLY lane)

Examples

massive capex shifts into one stack (fabs, GPU clusters, energy infrastructure)
sustained shortages / allocation regimes (not one-off)
export controls / strategic stockpiling

Why it matters
Civilisation-scale tech forces the lattice to reroute energy and capital.

Moves

PS_fast ✅
PS_confirmed ✅ (ACTUATION when allocation regimes appear)

1.5 Regulation response (REG lane) — phase marker

Examples

bans, mandates, licensing regimes
export controls / restrictions on tooling
safety compliance frameworks with enforcement

Moves

PS_fast ✅
PS_confirmed ✅ (+25 ladder candidate)

1.6 Irreversibility (KINETIC equivalent in tech)

Examples

mass adoption lock-in (network effects make reversal costly)
standard becomes default across industry
major platform commits long-term (multi-year contracts + ecosystem shift)

Moves

PS_fast ✅
PS_confirmed ✅ (80–100 band candidate when lock-in is real)

2) Far-Node Sensors (proxy layer; capped)

2.1 Hiring & skills demand proxy

job postings spike in specific skills (baseline required)
wage premia emerge for niche expertise

Moves: PS_fast ✅ | PS_confirmed ⚠️ via convergence

2.2 Patent clustering / research chatter proxy

patent clusters, arXiv surges (baseline required)
but beware: publications ≠ adoption

Moves: PS_fast ✅ | PS_confirmed ⚠️ via convergence

2.3 Social/media buzz proxy (weakest)

“everyone talking about it”
viral demos without reproducibility

Moves: PS_fast (tiny) ✅ | PS_confirmed ❌

3) Convergence rule (Tech Pack)

			
TechConvergence :=
  if (≥1 FarNode in {HIRING_PROXY, PATENT_PROXY})
  AND (≥2 NearNode tokens among {DEPLOYMENT_AT_SCALE, CAPEX_REROUTE, REGULATION_ACTUATION, ADOPTION_STANDARD_LOCK} with tier {T1,T2})
  AND (within TTC ≤ 30d)    # tech moves slower than war/markets
  then:
    PS_confirmed += small_step (≤ +3)
    Confidence += +0.05
    Volatility := HIGH
else:
    far-nodes affect PS_fast only

		

4) Failure Mode Trace

			
Buzz-driven tracking → overestimates capability → misses adoption/capex lock-in → late recognition of true inflection → wrong strategic allocation.

5) How to run this pack with any LLM

Prompt:

“Extract tech tokens using Tech Token Dictionary v1.0; assign tier/class.”
“Compute PS_fast / PS_confirmed.”
“Output TTC_adoption (months/quarters), TTC_regulation, TTC_supply.”

(C3-2) Tech Token Dictionary v1.0

Technology Inflection Token Dictionary (Copy/Paste) (v1.0)

Summary (5 lines)

This dictionary defines stable tokens for detecting technology inflection points.
Tokens cover: capability, deployment, adoption, capex/supply, regulation, irreversibility.
Weights are base weights before reliability × actuation.
Keep the list finite; version forward only.

0) Token format

TokenDef := { id, lane, class, polarity, base_weight, notes }

1) Irreversibility / lock-in tokens (80–100 band drivers)

STANDARD_LOCK_IN_CONFIRMED

lane: ADOPT | class: ACT | polarity: ESCALATE | base_weight: 18
notes: an industry standard becomes default and enforced

PLATFORM_DEFAULT_INTEGRATION

lane: DEPLOY | class: ACT | polarity: ESCALATE | base_weight: 18
notes: major platform makes tech the default path (reversal costly)

ENTERPRISE_MIGRATION_WAVE

lane: DEPLOY | class: ACT | polarity: ESCALATE | base_weight: 16
notes: multiple large orgs migrate workflows (documented)

MULTI_YEAR_ECOSYSTEM_COMMITMENTS

lane: CAPEX | class: ORDER | polarity: ESCALATE | base_weight: 16
notes: long-term contracts, procurement lock-in

2) Actuation tokens (+25 ladder candidates)

REGULATION_MANDATE_OR_BAN

lane: REG | class: ACT | polarity: ESCALATE | base_weight: 16
notes: licensing, ban, mandate with enforcement

EXPORT_CONTROLS_ESCALATE

lane: REG/SUPPLY | class: ACT | polarity: ESCALATE | base_weight: 14

ALLOCATION_REGIME_SUPPLY_CONSTRAINT

lane: SUPPLY | class: ACT | polarity: ESCALATE | base_weight: 14
notes: rationing/allocation becomes normal

CAPEX_REROUTE_SURGE

lane: CAPEX | class: ACT | polarity: ESCALATE | base_weight: 14
notes: sustained capex shift into stack

3) Deployment tokens (confirmed movers)

DEPLOYMENT_AT_SCALE_CONFIRMED

lane: DEPLOY | class: ACT | polarity: ESCALATE | base_weight: 14

INTEGRATION_IN_CRITICAL_WORKFLOWS

lane: DEPLOY | class: ORDER | polarity: ESCALATE | base_weight: 12
notes: embedded into mission-critical pipelines

THROUGHPUT_METRICS_SUSTAINED

lane: DEPLOY | class: READY | polarity: ESCALATE | base_weight: 10
notes: sustained usage metrics, not one-day spike

4) Capability evidence tokens (fast movers; confirmed gated)

BENCHMARK_BREAKTHROUGH_REPRODUCIBLE

lane: CAPABILITY | class: READY | polarity: ESCALATE | base_weight: 10
notes: must be reproducible; otherwise treat as RHET

COST_PERFORMANCE_PARITY_CROSSED

lane: CAPABILITY | class: ACT | polarity: ESCALATE | base_weight: 12
notes: parity triggers adoption cascades

ROBUSTNESS_UNDER_STRESS_CONFIRMED

lane: CAPABILITY | class: READY | polarity: ESCALATE | base_weight: 10
notes: stability under distribution shift

5) Adoption tokens

EDUCATION_CURRICULUM_ADOPTION

lane: ADOPT | class: ORDER | polarity: ESCALATE | base_weight: 10
notes: education system starts training pipeline for it

WORKFORCE_RETRAINING_WAVE

lane: ADOPT | class: ACT | polarity: ESCALATE | base_weight: 12
notes: broad retraining indicates structural adoption

COMPETITOR_CATCHUP_RACE

lane: ADOPT | class: READY | polarity: ESCALATE | base_weight: 8
notes: multiple rivals shift strategy to respond

6) Stabilizers / brakes (subtractive)

REGULATORY_SLOWDOWN_OR_MORATORIUM

lane: REG | class: ACT | polarity: DEESCALATE | base_weight: 10
notes: braking adoption / deployment

CAPEX_PULLBACK_CONFIRMED

lane: CAPEX | class: ACT | polarity: DEESCALATE | base_weight: 12

ADOPTION_BACKLASH_ENTERPRISE_PAUSE

lane: DEPLOY | class: ACT | polarity: DEESCALATE | base_weight: 10

7) Far-node proxy tokens (fast-only, capped)

HIRING_SPIKE_PROXY

lane: ADOPT | class: POST | polarity: ESCALATE | base_weight: 5
notes: baseline required; confounded by cycles

PATENT_CLUSTER_PROXY

lane: CAPABILITY | class: POST | polarity: ESCALATE | base_weight: 5
notes: baseline required; patents ≠ deployment

VIRAL_DEMO_BUZZ_PROXY

lane: INFO | class: RHET | polarity: ESCALATE | base_weight: 2
notes: never moves confirmed alone

8) Failure Mode Trace

			
Benchmark obsession → ignores deployment/capex/regulation → misses lock-in → late strategic response to a true inflection.

Universal Phase-Shift Template Pack v1.0 (CivOS × VocabularyOS)

(U1) Universal Phase-Shift Template

The Cloneable Directory + Spec Page for Any Domain (v1.0)

Summary (5 lines)

This page is the master template for tracking any regime shift: war, finance, tech, social stability, supply chains.
You plug in a domain token dictionary and sensor pack, then run the same PS Engine v1.0.
Outputs are standardized: PS_fast / PS_confirmed / Confidence / Volatility / TTC windows / TriggerWatchlist.
Far-node proxies are capped and only matter through convergence.
Backtests calibrate weights and protect the system from narrative drift.

0) Directory Layout (clone this)

/phase-monitor/{domain}/

00-start-here (this template)
01-sensor-pack-v1-0
02-token-dictionary-v1-0
03-backtests-index
04-weekly-snapshots-index (or monthly)
05-latest-snapshot (always points to newest)

1) Domain Definition Block (fill this)

			
Domain := {
  name: STRING,
  scope: STRING,                     # what it covers, what it excludes
  cadence: {weekly, monthly, ad-hoc},
  TTC_default: DURATION,             # typical time-scale of phase shifts
  primary_lanes: [LANE...],          # e.g., {MIL,DIP,ECON} or {LIQ,CREDIT,POLICY}
  irreversibility_tokens: [TOKEN_ID...],
  key_chokepoints_or_levers: [STRING...]
}

		

2) Required Inputs (must exist before snapshots)

Sensor Pack v1.0 (Near-node + Far-node, convergence rules)
Token Dictionary v1.0 (finite list, versioned)
Backtest Index (at least 1 backtest before public forecasting cadence starts)
Weekly Snapshot Template (the standardized output format)

3) The Universal PS Engine v1.0 (reference block)

			
PS Engine v1.0 :=
  tokenize narratives -> Token schema
  tier sources -> T1..T4
  classify -> RHET/POST/READY/ORDER/ACT/KIN
  dedup same-event repeats
  compute channel scores with caps
  compute PS_fast (sensitive, capped far-node)
  compute PS_confirmed (actuation-gated)
  apply irreversibility multiplier
  compute TTC windows + clamp during reaction windows
  output diagnostics: Confidence, Volatility, ConvergenceGap

		

4) Convergence Rule (universal)

			
Promotion :=
  if (≥1 FarNode sensor is strong AND baseline-verified)
  AND (≥2 NearNode tokens are ORDER/ACT/KIN with tier T1/T2)
  AND (within TTC window)
  then:
    PS_confirmed += small_step (≤ +3)
    Confidence += +0.05
else:
    FarNode affects PS_fast only

		

5) Snapshot Output Contract (must match exactly)

			
RUN := {
  PS_fast: 0..100,
  PS_confirmed: 0..100,
  Confidence: 0..1,
  Volatility: LOW|MED|HIGH,
  ConvergenceGap: INT,
  ActiveWindows: {TTC_event, TTC_policy, TTC_market, ReactionWindow},
  TopDrivers: [Token.id x5],
  TopBrakes: [Token.id x5],
  TriggerWatchlist: {+10, +25, 80-100 entry}
}

		

6) Failure Mode Trace (required)

			
No backtests → weight drift → false positives → trust loss → true phase shift ignored → late response.

7) “How to Use With Any LLM” (copy block)

Prompt sequence:

Extract tokens in schema from sources.
Tier + classify.
Dedup.
Compute RUN using PS Engine v1.0.
Output TriggerWatchlist.

(U2) Backtests Index Skeleton (Universal)

Backtests Index (Truth Spines + Calibration Logs) (v1.0)

Purpose

Backtests are where the model earns credibility.
They turn “a nice idea” into a calibrated system.

1) Backtest Index Table (copy/paste)

Backtest	Domain	Event Window	Crossing Date	First PS_fast Warning	First PS_confirmed Spike	False Spikes	Notes
Backtest-001	War	YYYY-MM-DD..	YYYY-MM-DD	YYYY-MM-DD	YYYY-MM-DD	N	link
Backtest-002	Finance	YYYY-MM-DD..	YYYY-MM-DD	YYYY-MM-DD	YYYY-MM-DD	N	link
Backtest-003	Tech	YYYY-MM-DD..	YYYY-MM-DD	YYYY-MM-DD	YYYY-MM-DD	N	link

2) Backtest Page Template (copy block)

			
BacktestRun := {
  event_name,
  domain,
  truth_spine_dates: [ {date, irreversible_action, evidence_ref} ... ],
  token_series: [ {date, tokens[]} ... ],
  PS_fast_series: [ {date, score} ... ],
  PS_confirmed_series: [ {date, score} ... ],
  first_warning_date,
  crossing_date,
  false_spike_log: [ ... ],
  missed_signal_log: [ ... ],
  calibrated_changes: [
    {token_id, old_weight, new_weight, reason, validated_on_cases}
  ]
}

		

3) Calibration Governance (hard)

Never tune to one case only.
Every weight change must be validated on ≥3 cases (within that domain) before promotion.
Keep token dictionary finite; extend by versioning forward only.

(U3) “Start Here” Page for Any Domain (ultra short)

Start Here: How to Read Phase Snapshots (v1.0)

Summary

PS_fast is early warning.
PS_confirmed is actuation-gated confirmation.
Confidence tells you evidence quality.
Volatility tells you the score is accelerating.
TriggerWatchlist tells you what would change the regime.

The only rule you need

Don’t react to words. React to actuation + convergence.

Below are three filled backtest skeletons (truth spine + token-series placeholders) you can publish immediately, then fill day-by-day tokens later. I’m using primary/authoritative sources for the load-bearing dates (Fed, NY Fed, Reuters).

Backtest-001 (War) — Soleimani 2020 (template filled)

I’m not re-webbing this one right now (you already used it as your calibration anchor), so here is the publishable skeleton in your engine format. Replace the evidence_refs with your already-used sources/logs from your prior Soleimani timeline.

			
BacktestRun := {
  event_name: "US–Iran escalation (Soleimani) 2020",
  domain: "War",
  truth_spine_dates: [
    {date: "2020-01-03", irreversible_action: "ATTRIBUTED_KINETIC_ACTION", evidence_ref: "your-T1-source"},
    {date: "2020-01-08", irreversible_action: "MISSILE_ATTACK_CONFIRMED", evidence_ref: "your-T1-source"}
  ],
  token_series: [
    {date: "2020-01-01", tokens: ["C2_WAR_ROOM_TEMPO", "CARRIER_STRIKE_GROUP_POSITIONING"]},
    {date: "2020-01-03", tokens: ["ATTRIBUTED_KINETIC_ACTION"]},
    {date: "2020-01-04..2020-01-10", tokens: ["RETALIATION_EXPECTED_OFFICIAL", "EMBASSY_DRAWDOWN", "TRAVEL_ADVISORY_LEAVE_IMMEDIATELY"]}
  ],
  PS_fast_series: "to-fill",
  PS_confirmed_series: "to-fill",
  first_warning_date: "to-fill",
  crossing_date: "2020-01-03",
  false_spike_log: "to-fill",
  missed_signal_log: "to-fill",
  calibrated_changes: "to-fill"
}

		

Backtest-002 (Finance) — March 2020 Crash & Policy Actuation (truth spine anchored)

Key truth-spine anchors:

Market-wide circuit breakers triggered on Mar 9, Mar 12, Mar 16, 2020 (S&P 500 level-1 halts). (Reuters)
Fed emergency cut to 0–0.25% announced Mar 15, 2020 (FOMC statement). (Federal Reserve)
PMCCF + SMCCF announced/established Mar 23, 2020 (corporate credit facilities). (Federal Reserve)

			
BacktestRun := {
  event_name: "COVID liquidity fracture & March 2020 crash",
  domain: "Finance",
  truth_spine_dates: [
    {date: "2020-03-09", irreversible_action: "CIRCUIT_BREAKERS_TRIGGERED", evidence_ref: "Reuters circuit breaker explainer"},
    {date: "2020-03-12", irreversible_action: "CIRCUIT_BREAKERS_TRIGGERED", evidence_ref: "Wikipedia crash timeline / market records"},
    {date: "2020-03-15", irreversible_action: "SURPRISE_RATE_DECISION", evidence_ref: "Fed FOMC statement"},
    {date: "2020-03-16", irreversible_action: "CIRCUIT_BREAKERS_TRIGGERED", evidence_ref: "Reuters circuit breaker explainer"},
    {date: "2020-03-23", irreversible_action: "EMERGENCY_LIQUIDITY_FACILITY_ACTIVATED", evidence_ref: "Fed PMCCF/SMCCF pages"}
  ],
  token_series: [
    {date: "2020-03-01..2020-03-08", tokens: [
      "IMPLIED_VOL_SPIKE_PERSISTENT",
      "CREDIT_SPREADS_WIDEN_SHARP",
      "REPO_STRESS_SPIKE"
    ]},
    {date: "2020-03-09", tokens: ["CIRCUIT_BREAKERS_TRIGGERED", "LIQUIDITY_WITHDRAWAL"]},
    {date: "2020-03-12", tokens: ["CIRCUIT_BREAKERS_TRIGGERED", "BID_ASK_WIDENS_SYSTEMIC"]},
    {date: "2020-03-15", tokens: ["SURPRISE_RATE_DECISION"]},
    {date: "2020-03-16", tokens: ["CIRCUIT_BREAKERS_TRIGGERED", "FORCED_DELEVERAGING_SIGNAL"]},
    {date: "2020-03-23", tokens: ["EMERGENCY_LIQUIDITY_FACILITY_ACTIVATED"]}   # PMCCF/SMCCF
  ],
  PS_fast_series: "to-fill (daily)",
  PS_confirmed_series: "to-fill (daily)",
  first_warning_date: "target: early March (pre-03-09)",
  crossing_date: "2020-03-09 (first circuit breaker)",
  false_spike_log: "to-fill",
  missed_signal_log: "to-fill",
  calibrated_changes: "to-fill"
}

		

Sources for the anchors: circuit breaker dates (Reuters); Fed rate cut (Federal Reserve); PMCCF/SMCCF (Federal Reserve).

Backtest-003 (Tech) — Smartphone Platform Inflection (iPhone → App ecosystem)

This backtest is about inflection mechanics: capability + platform deployment + ecosystem lock-in.

Truth-spine anchors:

Original iPhone released June 29, 2007. (Wikipedia)
App Store released in 2008 (platform ecosystem unlock). (Wikipedia)

			
BacktestRun := {
  event_name: "Smartphone platform inflection (iPhone + app ecosystem)",
  domain: "Tech",
  truth_spine_dates: [
    {date: "2007-06-29", irreversible_action: "DEPLOYMENT_AT_SCALE_CONFIRMED (platform launch)", evidence_ref: "iPhone release date"},
    {date: "2008-07 (App Store era)", irreversible_action: "PLATFORM_DEFAULT_INTEGRATION (ecosystem unlock)", evidence_ref: "App Store release reference"}
  ],
  token_series: [
    {date: "2007-01-09", tokens: ["BENCHMARK_BREAKTHROUGH_REPRODUCIBLE (product-class UI shift)"]},
    {date: "2007-06-29", tokens: ["DEPLOYMENT_AT_SCALE_CONFIRMED", "THROUGHPUT_METRICS_SUSTAINED (early adoption metrics)"]},
    {date: "2008-07..2009", tokens: [
      "PLATFORM_DEFAULT_INTEGRATION",
      "ENTERPRISE_MIGRATION_WAVE (industry shifts to touch+apps)",
      "HIRING_SPIKE_PROXY (mobile dev) (far-node, baseline required)"
    ]}
  ],
  PS_fast_series: "to-fill (monthly)",
  PS_confirmed_series: "to-fill (monthly)",
  first_warning_date: "target: early 2007 (pre-launch)",
  crossing_date: "2007-06-29",
  false_spike_log: "to-fill",
  missed_signal_log: "to-fill",
  calibrated_changes: "to-fill"
}

		

Sources for anchors: iPhone release and App Store timing (Wikipedia).

/phase-monitor/war/00-start-here (War Pack v1.0)

Start Here: War Phase Monitor (CivOS × VocabularyOS) (v1.0)

What this is

This monitor detects war-phase transitions using a convergence-gated lattice.
It outputs PS_fast (early warning) and PS_confirmed (actuation-gated).

The only rule

Words don’t move PS_confirmed. Actuation does.

Read the weekly snapshot like this

PS_fast = heat / early warning
PS_confirmed = real lever pulls (ORDER/ACT/KIN, T1/T2)
Confidence = evidence quality
Volatility = acceleration
ConvergenceGap = hype vs confirmation

Links (War Pack)

01 — War Sensor Pack v1.0: (link) /phase-monitor/war/01-sensor-pack-v1-0/
02 — War Token Dictionary v1.0: (link) /phase-monitor/war/02-token-dictionary-v1-0/
03 — War Backtests Index: (link) /phase-monitor/war/03-backtests-index/
04 — Weekly War Snapshots Index: (link) /phase-monitor/war/04-weekly-snapshots-index/
05 — Latest War Snapshot: (link) /phase-monitor/war/05-latest-snapshot/

Failure Mode Trace (required)

			
Proxy treated as proof → false alarms → trust decay → real actuation ignored → late response → irreversible phase crossing.

/phase-monitor/war/03-backtests-index (War)

War Backtests Index (Truth Spines + Calibration Logs) (v1.0)

Backtests table

Backtest	Event	Event Window	Crossing Date	First PS_fast Warning	First PS_confirmed Spike	False Spikes	Link
Backtest-001	US–Iran escalation (Soleimani)	2020-01-01..2020-01-10	2020-01-03	TBD	TBD	TBD	`/phase-monitor/war/backtest-001-soleimani-2020/`

Governance

Backtests are where weights change.
Snapshots are where we run the fixed model.
Every weight change must be validated on ≥3 cases before promotion.

/phase-monitor/war/backtest-001-soleimani-2020

Backtest-001: Soleimani 2020 (War) (v1.0)

Truth spine (ground truth)

2020-01-03: ATTRIBUTED_KINETIC_ACTION (crossing event)
2020-01-08: MISSILE_ATTACK_CONFIRMED (irreversibility confirmation)

Evidence refs: insert your Tier-1 sources (Reuters/AP/official) used in your prior calibration logs.

Token series (starter skeleton)

			
token_series := [
  {date:"2020-01-01", tokens:["C2_WAR_ROOM_TEMPO","CARRIER_STRIKE_GROUP_POSITIONING"]},
  {date:"2020-01-03", tokens:["ATTRIBUTED_KINETIC_ACTION"]},
  {date:"2020-01-04..2020-01-10", tokens:["RETALIATION_EXPECTED_OFFICIAL","TRAVEL_ADVISORY_LEAVE_IMMEDIATELY","EMBASSY_DRAWDOWN"]},
  {date:"2020-01-08", tokens:["MISSILE_ATTACK_CONFIRMED"]}
]

		

Expected behavior (calibration target)

PS_fast rises before 2020-01-03
PS_confirmed jumps ≥ +15 on 2020-01-03
RetaliationWindow clamp prevents premature decay until the window passes
PS_confirmed hits 80–100 band only on irreversibility tokens

Calibration log (fill)

			
calibrated_changes := [
  {token_id:"EMBASSY_BREACH_SIEGE", old_weight:__, new_weight:__, reason:"precursor strength", validated_on_cases:__},
  {token_id:"ATTRIBUTED_KINETIC_ACTION", old_weight:__, new_weight:__, reason:"phase-change dominance", validated_on_cases:__}
]

/phase-monitor/war/04-weekly-snapshots-index

Weekly War Snapshots Index (v1.0)

Index

Week Ending	Theatre	PS_fast	PS_confirmed	Confidence	Volatility	Link
YYYY-MM-DD	Iran–US	__	__	__	__	`/phase-monitor/war/snapshot-YYYY-MM-DD-iran-us/`

Latest snapshot pointer

/phase-monitor/war/05-latest-snapshot/ should always redirect to the newest row.

/phase-monitor/war/05-latest-snapshot

Latest War Snapshot (v1.0)

Link to newest snapshot: (insert permalink)

/phase-monitor/finance/00-start-here (Finance Pack v1.0)

Start Here: Finance Phase Monitor (CivOS × VocabularyOS) (v1.0)

What this is

This monitor detects financial regime shifts (liquidity/credit/policy phase changes), not daily price noise.

The only rule

Price moves don’t define regime shifts. Liquidity + policy actuation does.

Links (Finance Pack)

01 — Finance Sensor Pack v1.0: /phase-monitor/finance/01-sensor-pack-v1-0/
02 — Finance Token Dictionary v1.0: /phase-monitor/finance/02-token-dictionary-v1-0/
03 — Finance Backtests Index: /phase-monitor/finance/03-backtests-index/
04 — Weekly Finance Snapshots Index: /phase-monitor/finance/04-weekly-snapshots-index/
05 — Latest Finance Snapshot: /phase-monitor/finance/05-latest-snapshot/

Failure Mode Trace (required)

			
Price-only lens → misses funding stress → forced deleveraging begins → liquidity vanishes → crash appears “sudden.”

/phase-monitor/finance/03-backtests-index

Finance Backtests Index (v1.0)

Backtest	Event	Event Window	Crossing Date	First PS_fast Warning	First PS_confirmed Spike	False Spikes	Link
Backtest-002	March 2020 crash + policy actuation	2020-03-01..2020-03-31	2020-03-09	TBD	TBD	TBD	`/phase-monitor/finance/backtest-002-march-2020/`

/phase-monitor/finance/backtest-002-march-2020

Backtest-002: March 2020 Crash & Policy Actuation (Finance) (v1.0)

Truth spine anchors (ground truth)

2020-03-09: CIRCUIT_BREAKERS_TRIGGERED
2020-03-15: SURPRISE_RATE_DECISION (Fed emergency cut)
2020-03-23: EMERGENCY_LIQUIDITY_FACILITY_ACTIVATED (corporate credit facilities)

Token series (starter skeleton)

			
token_series := [
  {date:"2020-03-01..2020-03-08", tokens:["IMPLIED_VOL_SPIKE_PERSISTENT","CREDIT_SPREADS_WIDEN_SHARP","REPO_STRESS_SPIKE"]},
  {date:"2020-03-09", tokens:["CIRCUIT_BREAKERS_TRIGGERED","LIQUIDITY_WITHDRAWAL"]},
  {date:"2020-03-12", tokens:["CIRCUIT_BREAKERS_TRIGGERED","BID_ASK_WIDENS_SYSTEMIC"]},
  {date:"2020-03-15", tokens:["SURPRISE_RATE_DECISION"]},
  {date:"2020-03-16", tokens:["CIRCUIT_BREAKERS_TRIGGERED","FORCED_DELEVERAGING_SIGNAL"]},
  {date:"2020-03-23", tokens:["EMERGENCY_LIQUIDITY_FACILITY_ACTIVATED"]}
]

		

Expected behavior (calibration target)

PS_fast rises early March before first breaker
PS_confirmed spikes hard on breaker(s) + liquidity withdrawal
PS_confirmed rises again on emergency policy actuation (phase marker + stabilizer)

Calibration log (fill)

			
calibrated_changes := [
  {token_id:"REPO_STRESS_SPIKE", old_weight:__, new_weight:__, reason:"early funding precursor", validated_on_cases:__},
  {token_id:"EMERGENCY_LIQUIDITY_FACILITY_ACTIVATED", old_weight:__, new_weight:__, reason:"regime boundary marker", validated_on_cases:__}
]

/phase-monitor/finance/04-weekly-snapshots-index

Weekly Finance Snapshots Index (v1.0)

Week Ending	Lane	PS_fast	PS_confirmed	Confidence	Volatility	Link
YYYY-MM-DD	Global Liquidity	__	__	__	__	`/phase-monitor/finance/snapshot-YYYY-MM-DD-global-liquidity/`
YYYY-MM-DD	Credit Stress	__	__	__	__	`/phase-monitor/finance/snapshot-YYYY-MM-DD-credit-stress/`

/phase-monitor/finance/05-latest-snapshot

Latest Finance Snapshot (v1.0)

Link to newest snapshot: (insert permalink)

/phase-monitor/tech/00-start-here (Tech Pack v1.0)

Start Here: Technology Phase Monitor (CivOS × VocabularyOS) (v1.0)

What this is

This monitor detects technology inflection points: capability → deployment → adoption → capex/supply reroute → regulation → lock-in.

The only rule

Benchmarks don’t change civilisation until deployment + adoption actuate.

Links (Tech Pack)

01 — Tech Sensor Pack v1.0: /phase-monitor/tech/01-sensor-pack-v1-0/
02 — Tech Token Dictionary v1.0: /phase-monitor/tech/02-token-dictionary-v1-0/
03 — Tech Backtests Index: /phase-monitor/tech/03-backtests-index/
04 — Monthly Tech Snapshots Index: /phase-monitor/tech/04-monthly-snapshots-index/
05 — Latest Tech Snapshot: /phase-monitor/tech/05-latest-snapshot/

Failure Mode Trace (required)

			
Buzz-driven tracking → overestimates capability → misses adoption/capex lock-in → late recognition of true inflection → wrong allocation.

/phase-monitor/tech/03-backtests-index

Tech Backtests Index (v1.0)

Backtest	Event	Event Window	Crossing Date	First PS_fast Warning	First PS_confirmed Spike	False Spikes	Link
Backtest-003	Smartphone platform inflection	2007-01..2009-12	2007-06-29	TBD	TBD	TBD	`/phase-monitor/tech/backtest-003-smartphone-platform/`

/phase-monitor/tech/backtest-003-smartphone-platform

Backtest-003: Smartphone Platform Inflection (Tech) (v1.0)

Truth spine anchors (ground truth)

2007-06-29: DEPLOYMENT_AT_SCALE_CONFIRMED (platform launch)
2008 (App ecosystem unlock): PLATFORM_DEFAULT_INTEGRATION (lock-in accelerant)

Token series (starter skeleton)

			
token_series := [
  {date:"2007-01-09", tokens:["BENCHMARK_BREAKTHROUGH_REPRODUCIBLE"]},
  {date:"2007-06-29", tokens:["DEPLOYMENT_AT_SCALE_CONFIRMED","THROUGHPUT_METRICS_SUSTAINED"]},
  {date:"2008-07..2009", tokens:["PLATFORM_DEFAULT_INTEGRATION","ENTERPRISE_MIGRATION_WAVE","HIRING_SPIKE_PROXY"]}
]

		

Expected behavior (calibration target)

PS_fast rises pre-launch (capability + anticipation)
PS_confirmed jumps at deployment scale
PS_confirmed rises again at ecosystem integration (lock-in)

Calibration log (fill)

			
calibrated_changes := [
  {token_id:"PLATFORM_DEFAULT_INTEGRATION", old_weight:__, new_weight:__, reason:"lock-in dominance", validated_on_cases:__},
  {token_id:"CAPEX_REROUTE_SURGE", old_weight:__, new_weight:__, reason:"civilisation energy reroute marker", validated_on_cases:__}
]

/phase-monitor/tech/04-monthly-snapshots-index

Monthly Tech Snapshots Index (v1.0)

Month	Lane	PS_fast	PS_confirmed	Confidence	Volatility	Link
YYYY-MM	AI Capability Acceleration	__	__	__	__	`/phase-monitor/tech/snapshot-YYYY-MM-ai/`
YYYY-MM	Semiconductor Chokepoints	__	__	__	__	`/phase-monitor/tech/snapshot-YYYY-MM-chips/`
YYYY-MM	Energy Storage	__	__	__	__	`/phase-monitor/tech/snapshot-YYYY-MM-energy-storage/`

/phase-monitor/tech/05-latest-snapshot

Latest Tech Snapshot (v1.0)

Link to newest snapshot: (insert permalink)

Universal Snapshot Post Template (All Domains) (v1.0)

Permalink pattern:
/phase-monitor/{domain}/snapshot-YYYY-MM-DD-{theatre-or-lane}/

Title (fixed pattern)

Phase Snapshot (v1.0): {Domain} — {Theatre/Lane} — Week Ending {YYYY-MM-DD}

0) Snapshot Header (fixed)

Window: YYYY-MM-DD → YYYY-MM-DD (Timezone)
Domain: War / Finance / Tech / Social / Supply Chain
Theatre/Lane: (e.g., Iran–US / Global Liquidity / AI Capability Acceleration)
Engine Version: v1.0
Sources Policy: T1/T2 primary; T3/T4 capped fast-only

1) Scores (always 2)

PS_fast: _ / 100 PS_confirmed: _ / 100

Confidence: _ (0.00–1.00) Volatility: LOW / MED / HIGH Convergence Gap: |PS_fast − PS_confirmed| = _

Interpretation (fixed)

Gap > 15 → heat/noise regime (watch, don’t act)
Gap < 8 → confirmed regime (escalation or stabilisation)

2) Active TTC Windows

TTC_event: _ TTC_policy: _
TTC_market: __

Reaction Window Active? YES / NO
If YES: score decay is clamped unless StrongBrake exists.

3) Channel Readout (capped)

STRUCTURAL_POSTURE: _ / 25 LEVER_ACTUATION: _ / 20
IRREVERSIBLE_EVENTS: _ / 20 STABILIZERS_BRAKES: _ / 20 (subtractive)
TTC_COMPRESSION: __ / 15

4) Top Drivers (max 5)

TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref

5) Top Brakes / Stabilizers (max 5)

TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref

6) Far-Node Sensor Vector (optional; fast-only)

Only include if baseline + reproducible.

AIRSPACE_ACTUATION_PROXY: __/10
MARITIME_ACTUATION_PROXY: __/10
CIVIL_PROTECTION_POSTURE: __/10
LOGISTICS_RAMP: __/10
OSINT_TEMPO_PROXY: __/5
MARKET_RISK_SENSOR: __/5

Convergence Hit? YES / NO
If YES: state the convergent set (1 line max).

7) Trigger Watchlist (forward-looking, structured)

+10 triggers (moderate)

(list tokens/events that would raise confirmed meaningfully)

+25 triggers (strong)

(list actuation/irreversibility candidates)

80–100 band entry (irreversibility regime)

(state irreversibility token(s) + TTC condition)

8) Failure Mode Trace (required)

			
No actuation gating → PS_confirmed becomes hype-driven → false alarms → trust decay → real phase shift missed.

9) Notes (optional)

Short, unemotive, structural only.

10) How to run this with any LLM (copy block)

Prompt sequence:

Extract tokens in schema; assign tier/class.
Dedup same-event repeats.
Compute PS_fast / PS_confirmed using v1.0.
Output TopDrivers/Brakes + TTC windows + TriggerWatchlist.

Master Phase Monitor Hub (Z5 Surface Directory Style) (v1.0)

Permalink: /phase-monitor/

Phase Monitor (CivOS × VocabularyOS) — Global Regime Shift Tracker (v1.0)

What this is

A universal phase detector for:

War / geopolitics
Finance / market regime shifts
Technology inflection points
Social stability
Supply chain fractures

It uses a lattice model with:

tokenized signals (VocabularyOS)
reliability gating (T1–T4)
convergence rules
PS_fast vs PS_confirmed
TTC windows + irreversibility dominance

Global Rules (non-negotiable)

Far-node proxies never decide alone.
PS_confirmed is actuation-gated.
Irreversibility dominates 80–100.
Backtests govern weight changes.
Snapshot cadence stays fixed and comparable.

Domain Directories

War / Geopolitics

Start Here: /phase-monitor/war/00-start-here/
Latest Snapshot: /phase-monitor/war/05-latest-snapshot/
Weekly Index: /phase-monitor/war/04-weekly-snapshots-index/
Backtests: /phase-monitor/war/03-backtests-index/

Finance / Markets

Start Here: /phase-monitor/finance/00-start-here/
Latest Snapshot: /phase-monitor/finance/05-latest-snapshot/
Weekly Index: /phase-monitor/finance/04-weekly-snapshots-index/
Backtests: /phase-monitor/finance/03-backtests-index/

Technology / Inflections

Start Here: /phase-monitor/tech/00-start-here/
Latest Snapshot: /phase-monitor/tech/05-latest-snapshot/
Monthly Index: /phase-monitor/tech/04-monthly-snapshots-index/
Backtests: /phase-monitor/tech/03-backtests-index/

Output Contract (what every snapshot must include)

PS_fast, PS_confirmed
Confidence, Volatility, ConvergenceGap
TTC windows + ReactionWindow
TopDrivers + TopBrakes
TriggerWatchlist

If a post does not include these, it is not a Phase Snapshot.

Failure Mode Trace (required)

			
Unstructured monitoring → headline chasing → false alarms → trust collapse → real regime shift missed.

Social Stability Pack v1.0 (CivOS × VocabularyOS)

(S1) Social Stability Sensor Pack v1.0

Social / Governance Phase Shift Sensor Pack (v1.0)

Summary (5 lines)

Social stability shifts follow: grievance load → mobilisation → state posture → actuation controls → irreversibility.
This pack tracks stability regime change, not daily news.
Near-node sensors include communications controls, force mobilisation, legal actuation, institutional fractures.
Far-node sensors (chatter, small incidents) are capped and only matter via convergence.
Outputs feed PS Engine v1.0.

0) Hard rules

Protests alone ≠ regime change unless they couple to state actuation (controls/force/law).
Comms shutdown + emergency law are high-value actuation markers.
Institutional splits (security services, courts, parliament) are irreversibility precursors.
Far-node social media signals never move PS_confirmed alone.
Track TTC_policy: elections, court deadlines, confidence votes, budget votes.

1) Near-Node Sensors (highest value)

1.1 State control actuation (ACTUATION)

internet throttling/shutdown (verified)
curfews, emergency regulations
mass arrests / detention campaigns
bans on assembly with enforcement

Moves: PS_fast ✅ | PS_confirmed ✅ (+25 ladder)

1.2 Force posture & mobilisation (POSTURE/READINESS/ORDER)

riot police deployment at scale
military deployed domestically
national guard call-up
“rules of engagement” changes (order)

Moves: PS_fast ✅ | PS_confirmed ✅ (gated)

1.3 Institutional fracture (KINETIC equivalent)

leadership removal / coup attempt / mutiny
parliament dissolved / judiciary overridden
security service split / defection
election annulment

Moves: PS_fast ✅ | PS_confirmed ✅ (80–100 band candidates)

1.4 Civil protection signals

embassy drawdowns / evacuation advisories (if widespread)
border controls tightened
large transport cancellations

Moves: PS_fast ✅ | PS_confirmed ⚠️ via convergence

2) Far-Node Sensors (proxy, capped)

2.1 Mobilisation proxies

protest clustering reports (baseline required)
strike participation proxies
crowd size estimates from non-primary sources

Moves: PS_fast ✅ | PS_confirmed ❌ unless verified

2.2 Money/food stress proxies

ATM runs, cash shortages
sudden price spikes in essentials
supply queue patterns

Moves: PS_fast ✅ | PS_confirmed ⚠️ via convergence with controls

3) Convergence rule (Social)

			
SocialConvergence :=
  if (≥1 FarNode in {MOBILISATION_PROXY, ESSENTIALS_STRESS_PROXY})
  AND (≥2 NearNode tokens among {COMMS_SHUTDOWN_ACTUATED, EMERGENCY_LAW_DECLARED, DOMESTIC_MIL_DEPLOYED, MASS_ARRESTS_CAMPAIGN} with tier {T1,T2})
  AND (within TTC ≤ 72h)
  then:
    PS_confirmed += small_step (≤ +3)
    Confidence += +0.05
    Volatility := HIGH
else:
    far-nodes affect PS_fast only

		

4) Failure Mode Trace

			
Chatter-driven monitoring → overreacts to noise → misses state actuation → surprise emergency law → irreversible stability shift.

(S2) Social Stability Token Dictionary v1.0 (Copy/Paste) (v1.0)

Token format

TokenDef := { id, lane, class, polarity, base_weight, notes }

Irreversibility / 80–100 band drivers

COUP_OR_MUTINY_CONFIRMED

lane: GOV | class: KIN | polarity: ESCALATE | base_weight: 20

ELECTION_ANNULLED_OR_POSTPONED_FORCE

lane: GOV | class: KIN | polarity: ESCALATE | base_weight: 18

SECURITY_FORCES_SPLIT_DEFECT

lane: GOV | class: KIN | polarity: ESCALATE | base_weight: 18

PARLIAMENT_DISSOLVED_EXTRALEGAL

lane: GOV | class: KIN | polarity: ESCALATE | base_weight: 18

Actuation / +25 ladder

COMMS_SHUTDOWN_ACTUATED

lane: INFO | class: ACT | polarity: ESCALATE | base_weight: 16

EMERGENCY_LAW_DECLARED

lane: GOV | class: ACT | polarity: ESCALATE | base_weight: 16

CURFEW_ENFORCED

lane: GOV | class: ACT | polarity: ESCALATE | base_weight: 14

MASS_ARRESTS_CAMPAIGN

lane: GOV | class: ACT | polarity: ESCALATE | base_weight: 14

Force posture / readiness

DOMESTIC_MIL_DEPLOYED

lane: GOV | class: ACT | polarity: ESCALATE | base_weight: 14

RIOT_POLICE_MOBILIZED_SCALE

lane: GOV | class: READY | polarity: ESCALATE | base_weight: 10

ROE_DOMESTIC_SHIFT

lane: GOV | class: ORDER | polarity: ESCALATE | base_weight: 12

Stabilizers / brakes

NEGOTIATION_CHANNEL_OPENED

lane: GOV | class: POST | polarity: DEESCALATE | base_weight: 8

AMNESTY_OR_DETENTION_ROLLBACK

lane: GOV | class: ACT | polarity: DEESCALATE | base_weight: 12

ELECTION_MONITORING_ACCEPTED

lane: GOV | class: ACT | polarity: DEESCALATE | base_weight: 12

Far-node proxies (fast-only, capped)

PROTEST_CLUSTERING_PROXY

lane: SOC | class: POST | polarity: ESCALATE | base_weight: 5

ATM_RUNS_PROXY

lane: ECON | class: POST | polarity: ESCALATE | base_weight: 5

ESSENTIALS_PRICE_SPIKE_PROXY

lane: ECON | class: POST | polarity: ESCALATE | base_weight: 5

Failure Mode Trace

			
Counts protests → ignores control levers → misses comms shutdown → late recognition of regime shift.

Supply Chain Pack v1.0 (CivOS × VocabularyOS)

(SC1) Supply Chain Sensor Pack v1.0

Supply Chain / Infrastructure Phase Shift Sensor Pack (v1.0)

Summary (5 lines)

Supply chains fail by chokepoint stress → rerouting → capacity saturation → restrictions → prolonged disruption → structural redesign.
This pack detects regime shifts in trade/logistics, not everyday delays.
Near-nodes include export bans, port closures, insurance constraints, allocation regimes.
Far-nodes (spot freight spikes) are capped and require convergence.
Outputs feed PS Engine v1.0.

0) Hard rules

A one-day delay is not a phase shift.
Duration + scope (days → weeks, local → corridor) is the key.
Export bans / allocation regimes / port closures are actuation markers.
Irreversibility is a prolonged chokepoint disruption that forces structural rerouting.

1) Near-Node Sensors (highest value)

1.1 Chokepoint actuation (ACT)

canal closure / port closure
exclusion zones with enforcement
cargo interdictions
mandatory reroutes

Moves: PS_fast ✅ | PS_confirmed ✅ (+25 ladder)

1.2 Export restrictions / allocation regimes (ACT/ORDER)

export bans on critical goods
quotas, licensing constraints
rationing / allocation regimes

Moves: PS_fast ✅ | PS_confirmed ✅

1.3 Insurance / risk constraints (ACT)

war-risk premium surges (documented policy changes)
insurers refuse coverage in corridor

Moves: PS_fast ✅ | PS_confirmed ⚠️ via convergence (can be strong)

1.4 Structural redesign markers (irreversibility)

long-term corridor reconfiguration (new routes, new hubs)
new industrial policy forcing reshoring
sustained supply fragmentation

Moves: PS_fast ✅ | PS_confirmed ✅ (80–100 band candidates)

2) Far-Node Sensors (proxy, capped)

spot freight rate spikes (baseline required)
congestion indices (baseline required)
container imbalance signals

Moves: PS_fast ✅ | PS_confirmed ⚠️ via convergence

3) Convergence rule (Supply Chain)

			
SupplyConvergence :=
  if (≥1 FarNode in {FREIGHT_SPIKE_PROXY, CONGESTION_PROXY})
  AND (≥2 NearNode tokens among {PORT_CLOSURE_ACTUATED, EXPORT_BAN_ACTUATED, ALLOCATION_REGIME_CONFIRMED} with tier {T1,T2})
  AND (within TTC ≤ 7d)
  then:
    PS_confirmed += small_step (≤ +3)
    Confidence += +0.05
    Volatility := HIGH
else:
    far-nodes affect PS_fast only

		

4) Failure Mode Trace

			
Price-only shipping lens → misses export bans → corridor snaps → prolonged disruption becomes “surprise” → forced redesign happens late.

(SC2) Supply Chain Token Dictionary v1.0 (Copy/Paste) (v1.0)

Token format

TokenDef := { id, lane, class, polarity, base_weight, notes }

Irreversibility / 80–100 drivers

PROLONGED_CHOKEPOINT_DISRUPTION

lane: LOG | class: ACT | polarity: ESCALATE | base_weight: 20
notes: days→weeks disruption, corridor-wide

STRUCTURAL_CORRIDOR_REDIRECTION_CONFIRMED

lane: LOG/POLICY | class: KIN | polarity: ESCALATE | base_weight: 18

INDUSTRIAL_POLICY_RESHORING_ACTUATED

lane: POLICY | class: ACT | polarity: ESCALATE | base_weight: 16

Actuation / +25 ladder

PORT_CLOSURE_ACTUATED

lane: LOG | class: ACT | polarity: ESCALATE | base_weight: 16

EXPORT_BAN_ACTUATED

lane: POLICY | class: ACT | polarity: ESCALATE | base_weight: 16

ALLOCATION_REGIME_CONFIRMED

lane: POLICY/LOG | class: ACT | polarity: ESCALATE | base_weight: 14

MANDATORY_REROUTE_ENFORCED

lane: LOG | class: ACT | polarity: ESCALATE | base_weight: 14

Posture / readiness

CONGESTION_SATURATION_CONFIRMED

lane: LOG | class: READY | polarity: ESCALATE | base_weight: 10

INSURANCE_COVERAGE_WITHDRAWAL

lane: FIN/LOG | class: ACT | polarity: ESCALATE | base_weight: 12

Stabilizers / brakes

CORRIDOR_REOPENING_CONFIRMED

lane: LOG | class: ACT | polarity: DEESCALATE | base_weight: 12

CAPACITY_EXPANSION_FAST_TRACKED

lane: LOG | class: ACT | polarity: DEESCALATE | base_weight: 10

Far-node proxies (fast-only, capped)

FREIGHT_RATE_SPIKE_PROXY

lane: LOG | class: POST | polarity: ESCALATE | base_weight: 5

CONGESTION_INDEX_SPIKE_PROXY

lane: LOG | class: POST | polarity: ESCALATE | base_weight: 5

CONTAINER_IMBALANCE_PROXY

lane: LOG | class: POST | polarity: ESCALATE | base_weight: 4

Failure Mode Trace

			
Freight rates spike → mistaken as “the crisis” → ignores actuation (export bans) → corridor snaps → prolonged disruption locks in.

Master Token Registry (All Domains) (Machine-Readable) (v1.0)

Summary (5 lines)

This registry is the single canonical list of all Phase Monitor tokens.
Each token has a stable id, domain, lane, class, polarity direction, base weight, and flags.
All dictionaries (war/finance/tech/social/supply) must reference this registry.
Do not rename token ids. Version forward only.
If a token is not here, it should not appear in snapshots.

Registry Schema (canonical)

			
TokenRegistryItem := {
  id: STRING,
  domain: {WAR, FINANCE, TECH, SOCIAL, SUPPLY},
  lane: STRING,
  class_default: {RHET, POST, READY, ORDER, ACT, KIN},
  polarity_default: {ESCALATE, DEESCALATE},
  base_weight: FLOAT,
  flags: {
    proxy: BOOL,
    irreversibility: BOOL,
    brake: BOOL
  },
  notes: STRING
}

		

WAR Tokens (v1.0)

			
{ id:"ATTRIBUTED_KINETIC_ACTION", domain:WAR, lane:"MIL", class_default:KIN, polarity_default:ESCALATE, base_weight:20, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Confirmed strike/attack with attribution." }
{ id:"MISSILE_ATTACK_CONFIRMED", domain:WAR, lane:"MIL", class_default:KIN, polarity_default:ESCALATE, base_weight:20, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Missile/drone attack confirmed as attack (not test)." }
{ id:"NAVAL_ENGAGEMENT_CONFIRMED", domain:WAR, lane:"MIL", class_default:KIN, polarity_default:ESCALATE, base_weight:18, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Combat engagement at sea confirmed." }
{ id:"EMBASSY_BREACH_SIEGE", domain:WAR, lane:"CIV", class_default:KIN, polarity_default:ESCALATE, base_weight:18, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Embassy/compound breach or siege." }
{ id:"PROLONGED_CHOKEPOINT_CLOSURE", domain:WAR, lane:"ECON", class_default:ACT, polarity_default:ESCALATE, base_weight:18, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Chokepoint disruption extends hours→days+." }
{ id:"CHOKEPOINT_ACTUATION", domain:WAR, lane:"ECON/MIL", class_default:ACT, polarity_default:ESCALATE, base_weight:18, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Restriction/closure/exclusion at chokepoint (temporary)." }
{ id:"INTERDICTION_SEIZURE", domain:WAR, lane:"MIL/ECON", class_default:ACT, polarity_default:ESCALATE, base_weight:16, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Interdiction/boarding/seizure enforced." }
{ id:"AIRSPACE_RESTRICTION_ACTUATION", domain:WAR, lane:"MIL", class_default:ACT, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Enforceable airspace restriction." }
{ id:"SANCTIONS_ENFORCEMENT_STEP", domain:WAR, lane:"ECON", class_default:ACT, polarity_default:ESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Sanctions move from talk to enforceable action." }
{ id:"MASS_MOBILIZATION", domain:WAR, lane:"MIL", class_default:ACT, polarity_default:ESCALATE, base_weight:16, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Mobilization beyond routine readiness." }
{ id:"FULL_DEPLOYMENT_DIRECTIVE", domain:WAR, lane:"MIL", class_default:ORDER, polarity_default:ESCALATE, base_weight:15, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Formal deployment directive with deadline." }
{ id:"STRIKE_AUTHORIZATION_SIGNAL", domain:WAR, lane:"MIL", class_default:ORDER, polarity_default:ESCALATE, base_weight:16, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Authorization/ROE expansion/strike window set." }
{ id:"OPERATION_WEEKS_LONG_PLANNING", domain:WAR, lane:"MIL", class_default:ORDER, polarity_default:ESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Sustained ops planning." }
{ id:"RETALIATION_EXPECTED_OFFICIAL", domain:WAR, lane:"MIL", class_default:READY, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Official expectation of retaliation." }
{ id:"CARRIER_STRIKE_GROUP_POSITIONING", domain:WAR, lane:"MIL", class_default:POST, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Carrier positioning." }
{ id:"BOMBER_OR_FIGHTER_REDEPLOYMENT", domain:WAR, lane:"MIL", class_default:POST, polarity_default:ESCALATE, base_weight:9, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Air assets redeploy." }
{ id:"AIR_DEFENSE_REPOSITIONING", domain:WAR, lane:"MIL", class_default:POST, polarity_default:ESCALATE, base_weight:8, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Air defense reposition." }
{ id:"C2_WAR_ROOM_TEMPO", domain:WAR, lane:"MIL", class_default:READY, polarity_default:ESCALATE, base_weight:8, flags:{proxy:false, irreversibility:false, brake:false}, notes:"War-room tempo (T1/T2 only)." }
{ id:"LIVE_FIRE_DRILL_NEAR_CHOKEPOINT", domain:WAR, lane:"MIL", class_default:ACT, polarity_default:ESCALATE, base_weight:6, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Drills; stronger when paired with restrictions." }
{ id:"EMBASSY_DRAWDOWN", domain:WAR, lane:"CIV", class_default:ORDER, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Embassy drawdown/dependents departure." }
{ id:"TRAVEL_ADVISORY_LEAVE_IMMEDIATELY", domain:WAR, lane:"CIV", class_default:ORDER, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Urgent travel advisory." }
{ id:"EVACUATION_STAGING", domain:WAR, lane:"CIV/LOG", class_default:READY, polarity_default:ESCALATE, base_weight:9, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Evacuation staging." }
{ id:"TALKS_CONFIRMED", domain:WAR, lane:"DIP", class_default:POST, polarity_default:DEESCALATE, base_weight:8, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Talks/contacts confirmed." }
{ id:"PROPOSAL_SUBMITTED_WRITTEN", domain:WAR, lane:"DIP", class_default:ORDER, polarity_default:DEESCALATE, base_weight:9, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Written proposal submitted." }
{ id:"ENFORCEABLE_MONITORING_MECHANISM", domain:WAR, lane:"DIP", class_default:ACT, polarity_default:DEESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Verification mechanism established." }
{ id:"DECONFLICTION_HOTLINE_ACTIVE", domain:WAR, lane:"DIP/MIL", class_default:ACT, polarity_default:DEESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Deconfliction hotline active." }
{ id:"DRAW_DOWN_CONFIRMED", domain:WAR, lane:"MIL", class_default:ACT, polarity_default:DEESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Verified drawdown." }
{ id:"NOTAM_EXCLUSION_ZONE_PROXY", domain:WAR, lane:"MIL", class_default:ACT, polarity_default:ESCALATE, base_weight:6, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Only if NOTAM text sourced; baseline helps." }
{ id:"TANKER_SURGE_PROXY", domain:WAR, lane:"MIL/LOG", class_default:READY, polarity_default:ESCALATE, base_weight:5, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Baseline required." }
{ id:"AIS_REROUTE_PROXY", domain:WAR, lane:"ECON", class_default:POST, polarity_default:ESCALATE, base_weight:5, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Baseline required." }
{ id:"OSINT_TEMPO_PROXY_PIZZA_TRAFFIC", domain:WAR, lane:"INFO", class_default:POST, polarity_default:ESCALATE, base_weight:2, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Weak proxy; never moves confirmed alone." }
{ id:"MARKET_RISK_SENSOR_OIL_SPIKE", domain:WAR, lane:"ECON", class_default:POST, polarity_default:ESCALATE, base_weight:4, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Confirmation only; never decisive alone." }

		

FINANCE Tokens (v1.0)

			
{ id:"BANK_FAILURE_OR_RESOLUTION", domain:FINANCE, lane:"FIN", class_default:KIN, polarity_default:ESCALATE, base_weight:20, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Failure/resolution/forced merger/bail-in." }
{ id:"EXCHANGE_TRADING_HALT_OR_CLOSURE", domain:FINANCE, lane:"FIN", class_default:KIN, polarity_default:ESCALATE, base_weight:18, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Exchange halt/closure." }
{ id:"SOVEREIGN_DEFAULT_OR_PAYMENT_FAILURE", domain:FINANCE, lane:"FIN", class_default:KIN, polarity_default:ESCALATE, base_weight:20, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Default/payment failure." }
{ id:"CAPITAL_CONTROLS_ACTUATED", domain:FINANCE, lane:"POLICY/FIN", class_default:ACT, polarity_default:ESCALATE, base_weight:18, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Capital controls enacted." }
{ id:"DEPOSIT_GUARANTEE_EMERGENCY", domain:FINANCE, lane:"POLICY", class_default:ACT, polarity_default:DEESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Stabilizer; also regime boundary marker." }
{ id:"EMERGENCY_LIQUIDITY_FACILITY_ACTIVATED", domain:FINANCE, lane:"POLICY", class_default:ACT, polarity_default:DEESCALATE, base_weight:16, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Liquidity facility activation." }
{ id:"SURPRISE_RATE_DECISION", domain:FINANCE, lane:"POLICY", class_default:ACT, polarity_default:DEESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Emergency/surprise rate decision." }
{ id:"REGULATORY_SHORT_SELLING_BAN", domain:FINANCE, lane:"POLICY", class_default:ACT, polarity_default:DEESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Short-selling ban." }
{ id:"FORWARD_GUIDANCE_SHIFTS_HARD", domain:FINANCE, lane:"POLICY", class_default:ORDER, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Polarity depends on tighten/ease; set per case." }
{ id:"LIQUIDITY_WITHDRAWAL", domain:FINANCE, lane:"FIN", class_default:ACT, polarity_default:ESCALATE, base_weight:16, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Market-making retreat/liquidity drain." }
{ id:"REPO_STRESS_SPIKE", domain:FINANCE, lane:"FIN", class_default:ACT, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Repo/funding stress spike." }
{ id:"BID_ASK_WIDENS_SYSTEMIC", domain:FINANCE, lane:"FIN", class_default:ACT, polarity_default:ESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Systemic spread widening." }
{ id:"MARGIN_REQUIREMENTS_RAISED", domain:FINANCE, lane:"FIN", class_default:ORDER, polarity_default:ESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Margin requirements raised." }
{ id:"FORCED_DELEVERAGING_SIGNAL", domain:FINANCE, lane:"FIN", class_default:READY, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Forced unwind signs." }
{ id:"CREDIT_SPREADS_WIDEN_SHARP", domain:FINANCE, lane:"FIN", class_default:ACT, polarity_default:ESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Sharp spread widening." }
{ id:"CDS_BLOWOUT_SYSTEMIC_NAME", domain:FINANCE, lane:"FIN", class_default:ACT, polarity_default:ESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Systemic CDS blowout." }
{ id:"BANK_FUNDING_STRESS", domain:FINANCE, lane:"FIN", class_default:ACT, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Bank funding stress." }
{ id:"IMPLIED_VOL_SPIKE_PERSISTENT", domain:FINANCE, lane:"FIN", class_default:ACT, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Persistent implied vol spike." }
{ id:"CORRELATION_SPIKE_ONE_FACTOR", domain:FINANCE, lane:"FIN", class_default:READY, polarity_default:ESCALATE, base_weight:8, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Correlation spikes." }
{ id:"CIRCUIT_BREAKERS_TRIGGERED", domain:FINANCE, lane:"FIN", class_default:KIN, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Circuit breakers triggered." }
{ id:"FX_SWAP_BASIS_WIDENS", domain:FINANCE, lane:"FIN", class_default:ACT, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Swap basis widens." }
{ id:"RESERVE_DRAIN_ACCELERATES", domain:FINANCE, lane:"FIN/POLICY", class_default:ACT, polarity_default:ESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Reserve drain accelerates." }
{ id:"FX_CONTROLS_TIGHTENED", domain:FINANCE, lane:"POLICY", class_default:ACT, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:false}, notes:"FX controls tightened." }
{ id:"COORDINATED_CENTRAL_BANK_ACTION", domain:FINANCE, lane:"POLICY", class_default:ACT, polarity_default:DEESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Coordinated action." }
{ id:"SWAP_LINES_EXPANDED", domain:FINANCE, lane:"POLICY", class_default:ACT, polarity_default:DEESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Swap lines expanded." }
{ id:"BACKSTOP_PROGRAM_EXPANDED", domain:FINANCE, lane:"POLICY", class_default:ACT, polarity_default:DEESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Backstop program expanded." }
{ id:"OPTIONS_SKEW_SHIFT_PROXY", domain:FINANCE, lane:"FIN", class_default:READY, polarity_default:ESCALATE, base_weight:5, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Baseline required." }
{ id:"RUMORED_MARGIN_CALLS_PROXY", domain:FINANCE, lane:"INFO", class_default:RHET, polarity_default:ESCALATE, base_weight:3, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Never moves confirmed alone." }
{ id:"INSIDER_SELLING_CLUSTER_PROXY", domain:FINANCE, lane:"INFO", class_default:POST, polarity_default:ESCALATE, base_weight:4, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Confounded; baseline required." }
{ id:"REAL_ECON_FREIGHT_DISLOCATION_PROXY", domain:FINANCE, lane:"ECON", class_default:POST, polarity_default:ESCALATE, base_weight:5, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Proxy; convergence only." }

		

TECH Tokens (v1.0)

			
{ id:"STANDARD_LOCK_IN_CONFIRMED", domain:TECH, lane:"ADOPT", class_default:ACT, polarity_default:ESCALATE, base_weight:18, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Industry standard becomes default/enforced." }
{ id:"PLATFORM_DEFAULT_INTEGRATION", domain:TECH, lane:"DEPLOY", class_default:ACT, polarity_default:ESCALATE, base_weight:18, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Major platform makes tech default path." }
{ id:"ENTERPRISE_MIGRATION_WAVE", domain:TECH, lane:"DEPLOY", class_default:ACT, polarity_default:ESCALATE, base_weight:16, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Multiple large orgs migrate workflows." }
{ id:"MULTI_YEAR_ECOSYSTEM_COMMITMENTS", domain:TECH, lane:"CAPEX", class_default:ORDER, polarity_default:ESCALATE, base_weight:16, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Long-term contracts/procurement lock-in." }
{ id:"REGULATION_MANDATE_OR_BAN", domain:TECH, lane:"REG", class_default:ACT, polarity_default:ESCALATE, base_weight:16, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Mandate/ban/licensing regime with enforcement." }
{ id:"EXPORT_CONTROLS_ESCALATE", domain:TECH, lane:"REG/SUPPLY", class_default:ACT, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Export controls tightened." }
{ id:"ALLOCATION_REGIME_SUPPLY_CONSTRAINT", domain:TECH, lane:"SUPPLY", class_default:ACT, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Rationing/allocation becomes normal." }
{ id:"CAPEX_REROUTE_SURGE", domain:TECH, lane:"CAPEX", class_default:ACT, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Sustained capex shift." }
{ id:"DEPLOYMENT_AT_SCALE_CONFIRMED", domain:TECH, lane:"DEPLOY", class_default:ACT, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Deployment at scale." }
{ id:"INTEGRATION_IN_CRITICAL_WORKFLOWS", domain:TECH, lane:"DEPLOY", class_default:ORDER, polarity_default:ESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Embedded in mission-critical pipelines." }
{ id:"THROUGHPUT_METRICS_SUSTAINED", domain:TECH, lane:"DEPLOY", class_default:READY, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Sustained usage metrics." }
{ id:"BENCHMARK_BREAKTHROUGH_REPRODUCIBLE", domain:TECH, lane:"CAPABILITY", class_default:READY, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Reproducible benchmark breakthrough." }
{ id:"COST_PERFORMANCE_PARITY_CROSSED", domain:TECH, lane:"CAPABILITY", class_default:ACT, polarity_default:ESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Cost/performance parity crossing." }
{ id:"ROBUSTNESS_UNDER_STRESS_CONFIRMED", domain:TECH, lane:"CAPABILITY", class_default:READY, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Robust under stress." }
{ id:"EDUCATION_CURRICULUM_ADOPTION", domain:TECH, lane:"ADOPT", class_default:ORDER, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Education pipeline adoption." }
{ id:"WORKFORCE_RETRAINING_WAVE", domain:TECH, lane:"ADOPT", class_default:ACT, polarity_default:ESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Broad retraining wave." }
{ id:"COMPETITOR_CATCHUP_RACE", domain:TECH, lane:"ADOPT", class_default:READY, polarity_default:ESCALATE, base_weight:8, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Multiple rivals shift strategy." }
{ id:"REGULATORY_SLOWDOWN_OR_MORATORIUM", domain:TECH, lane:"REG", class_default:ACT, polarity_default:DEESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Moratorium/slowdown." }
{ id:"CAPEX_PULLBACK_CONFIRMED", domain:TECH, lane:"CAPEX", class_default:ACT, polarity_default:DEESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Capex pullback." }
{ id:"ADOPTION_BACKLASH_ENTERPRISE_PAUSE", domain:TECH, lane:"DEPLOY", class_default:ACT, polarity_default:DEESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Enterprise pause/backlash." }
{ id:"HIRING_SPIKE_PROXY", domain:TECH, lane:"ADOPT", class_default:POST, polarity_default:ESCALATE, base_weight:5, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Baseline required." }
{ id:"PATENT_CLUSTER_PROXY", domain:TECH, lane:"CAPABILITY", class_default:POST, polarity_default:ESCALATE, base_weight:5, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Baseline required." }
{ id:"VIRAL_DEMO_BUZZ_PROXY", domain:TECH, lane:"INFO", class_default:RHET, polarity_default:ESCALATE, base_weight:2, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Never moves confirmed alone." }

		

SOCIAL Tokens (v1.0)

			
{ id:"COUP_OR_MUTINY_CONFIRMED", domain:SOCIAL, lane:"GOV", class_default:KIN, polarity_default:ESCALATE, base_weight:20, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Coup/mutiny confirmed." }
{ id:"ELECTION_ANNULLED_OR_POSTPONED_FORCE", domain:SOCIAL, lane:"GOV", class_default:KIN, polarity_default:ESCALATE, base_weight:18, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Election annulled/postponed by force." }
{ id:"SECURITY_FORCES_SPLIT_DEFECT", domain:SOCIAL, lane:"GOV", class_default:KIN, polarity_default:ESCALATE, base_weight:18, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Security forces split/defection." }
{ id:"PARLIAMENT_DISSOLVED_EXTRALEGAL", domain:SOCIAL, lane:"GOV", class_default:KIN, polarity_default:ESCALATE, base_weight:18, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Parliament dissolved extra-legally." }
{ id:"COMMS_SHUTDOWN_ACTUATED", domain:SOCIAL, lane:"INFO", class_default:ACT, polarity_default:ESCALATE, base_weight:16, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Internet throttling/shutdown verified." }
{ id:"EMERGENCY_LAW_DECLARED", domain:SOCIAL, lane:"GOV", class_default:ACT, polarity_default:ESCALATE, base_weight:16, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Emergency law declared." }
{ id:"CURFEW_ENFORCED", domain:SOCIAL, lane:"GOV", class_default:ACT, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Curfew enforced." }
{ id:"MASS_ARRESTS_CAMPAIGN", domain:SOCIAL, lane:"GOV", class_default:ACT, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Mass arrests campaign." }
{ id:"DOMESTIC_MIL_DEPLOYED", domain:SOCIAL, lane:"GOV", class_default:ACT, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Military deployed domestically." }
{ id:"RIOT_POLICE_MOBILIZED_SCALE", domain:SOCIAL, lane:"GOV", class_default:READY, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Riot police mobilized at scale." }
{ id:"ROE_DOMESTIC_SHIFT", domain:SOCIAL, lane:"GOV", class_default:ORDER, polarity_default:ESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Domestic ROE shift." }
{ id:"NEGOTIATION_CHANNEL_OPENED", domain:SOCIAL, lane:"GOV", class_default:POST, polarity_default:DEESCALATE, base_weight:8, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Negotiation channel opened." }
{ id:"AMNESTY_OR_DETENTION_ROLLBACK", domain:SOCIAL, lane:"GOV", class_default:ACT, polarity_default:DEESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Amnesty/rollback." }
{ id:"ELECTION_MONITORING_ACCEPTED", domain:SOCIAL, lane:"GOV", class_default:ACT, polarity_default:DEESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Monitoring accepted." }
{ id:"PROTEST_CLUSTERING_PROXY", domain:SOCIAL, lane:"SOC", class_default:POST, polarity_default:ESCALATE, base_weight:5, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Proxy; baseline required." }
{ id:"ATM_RUNS_PROXY", domain:SOCIAL, lane:"ECON", class_default:POST, polarity_default:ESCALATE, base_weight:5, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Proxy; baseline required." }
{ id:"ESSENTIALS_PRICE_SPIKE_PROXY", domain:SOCIAL, lane:"ECON", class_default:POST, polarity_default:ESCALATE, base_weight:5, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Proxy; baseline required." }

		

SUPPLY Tokens (v1.0)

			
{ id:"PROLONGED_CHOKEPOINT_DISRUPTION", domain:SUPPLY, lane:"LOG", class_default:ACT, polarity_default:ESCALATE, base_weight:20, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Days→weeks disruption, corridor-wide." }
{ id:"STRUCTURAL_CORRIDOR_REDIRECTION_CONFIRMED", domain:SUPPLY, lane:"LOG/POLICY", class_default:KIN, polarity_default:ESCALATE, base_weight:18, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Structural corridor redesign confirmed." }
{ id:"INDUSTRIAL_POLICY_RESHORING_ACTUATED", domain:SUPPLY, lane:"POLICY", class_default:ACT, polarity_default:ESCALATE, base_weight:16, flags:{proxy:false, irreversibility:true, brake:false}, notes:"Reshoring policy enacted." }
{ id:"PORT_CLOSURE_ACTUATED", domain:SUPPLY, lane:"LOG", class_default:ACT, polarity_default:ESCALATE, base_weight:16, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Port closure enforced." }
{ id:"EXPORT_BAN_ACTUATED", domain:SUPPLY, lane:"POLICY", class_default:ACT, polarity_default:ESCALATE, base_weight:16, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Export ban enacted." }
{ id:"ALLOCATION_REGIME_CONFIRMED", domain:SUPPLY, lane:"POLICY/LOG", class_default:ACT, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Allocation/quota regime confirmed." }
{ id:"MANDATORY_REROUTE_ENFORCED", domain:SUPPLY, lane:"LOG", class_default:ACT, polarity_default:ESCALATE, base_weight:14, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Mandatory reroute enforced." }
{ id:"CONGESTION_SATURATION_CONFIRMED", domain:SUPPLY, lane:"LOG", class_default:READY, polarity_default:ESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Congestion saturation confirmed." }
{ id:"INSURANCE_COVERAGE_WITHDRAWAL", domain:SUPPLY, lane:"FIN/LOG", class_default:ACT, polarity_default:ESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:false}, notes:"Insurance withdrawal documented." }
{ id:"CORRIDOR_REOPENING_CONFIRMED", domain:SUPPLY, lane:"LOG", class_default:ACT, polarity_default:DEESCALATE, base_weight:12, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Reopening confirmed." }
{ id:"CAPACITY_EXPANSION_FAST_TRACKED", domain:SUPPLY, lane:"LOG", class_default:ACT, polarity_default:DEESCALATE, base_weight:10, flags:{proxy:false, irreversibility:false, brake:true}, notes:"Capacity expansion fast-tracked." }
{ id:"FREIGHT_RATE_SPIKE_PROXY", domain:SUPPLY, lane:"LOG", class_default:POST, polarity_default:ESCALATE, base_weight:5, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Proxy; baseline required." }
{ id:"CONGESTION_INDEX_SPIKE_PROXY", domain:SUPPLY, lane:"LOG", class_default:POST, polarity_default:ESCALATE, base_weight:5, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Proxy; baseline required." }
{ id:"CONTAINER_IMBALANCE_PROXY", domain:SUPPLY, lane:"LOG", class_default:POST, polarity_default:ESCALATE, base_weight:4, flags:{proxy:true, irreversibility:false, brake:false}, notes:"Proxy; baseline required." }

		

Failure Mode Trace (required)

			
No registry → token id drift → duplicates masquerade as “new signals” → scores inflate → accuracy collapses.

Iran–US positioning snapshot (as of Thu, 19 Feb 2026 SG time) — CivOS Phase Monitor v1.0

What’s new (T1/T2-weighted):

Indirect US–Iran talks (Geneva) are ongoing, and Iran is expected to submit a written proposal; senior US officials are simultaneously signaling military action remains an option. (Reuters)
The US is building out combat capability “by mid-March” (that’s an explicit TTC window / deadline-like posture), and AP reports two carrier groups + significant air/ship assets being positioned. (AP News)
Russia (Lavrov) publicly warned against new US strikes on Iran—a useful read as a “diplomatic temperature” proxy, but not actuation by itself. (Reuters)
WSJ reports the US is withdrawing remaining troops from Syria (big regional posture change, but not framed as Iran-related by the piece). (The Wall Street Journal)

⚠️ I’m not treating tabloid claims (e.g., “Hormuz closed”) as confirmed actuation unless Reuters/AP/official notices corroborate. (Right now I only see that claim in low-quality sources.) (The Sun)

Tokenization (what moved the scores)

Near-node tokens (count most)

ESCALATE

CARRIER_STRIKE_GROUP_POSITIONING (POST/READY) — multi-carrier posture reported (AP News)
FULL_DEPLOYMENT_DIRECTIVE-like signal (ORDER/READY) — “combat capabilities in place by mid-March” (AP News)
RETALIATION_EXPECTED_OFFICIAL / “military action remains an option” (READY/RHET, capped) (Barron’s)

DEESCALATE / BRAKES

TALKS_CONFIRMED (POST) — indirect talks + written proposal path (AP News)

Far-node proxies (capped; can’t move confirmed alone)

Oil price uptick / market tension = proxy confirmation only (Barron’s)
“Pizza / fast-food / other quirky proxies” = T4 proxy; useful only if it converges with T1/T2 actuation. (Explainer coverage exists, but it’s not a reliable signal by itself.) (euronews)

Scores (new) — Iran–US theatre

PS_fast: 68 / 100
PS_confirmed: 52 / 100
Confidence: 0.72 (because we have multiple T1/T2 items, but no direct KIN event reported in these sources)
Volatility: HIGH (compressed TTC window: “mid-March” + heavy posture)
ConvergenceGap: 16 (heat > confirmation → classic P1/P2 edge)

Interpretation in CivOS terms:
You’re in P2→P1 boundary behavior: high posture + deadline-like readiness, while diplomacy still runs. No verified KIN token in the evidence we pulled.

“New score vs before”

I don’t have your previous numeric baseline saved in this chat thread, so I’m comparing to the canonical calibration anchors we built:

vs Soleimani-style crossing (where PS_confirmed would jump into 80–100 on KIN tokens), today’s 52 is materially lower (posture + readiness, not irreversible contact).
vs a “routine tension” baseline (~30–40 confirmed), today’s 52 is higher due to (a) multi-carrier posture reporting and (b) explicit “mid-March” readiness window. (AP News)

If you paste your last run’s numbers, I’ll compute the exact delta line-by-line (drivers/brakes).

How to increase accuracy (not just the score)

1) Upgrade the T1/T2 feed density (biggest accuracy gain)

Build a fixed ingest list per lane:
Official: CENTCOM releases, DoD briefings, State Dept statements
Wire: Reuters/AP (fastest T1/T2 consolidation)
Result: Confidence rises, PS_confirmed becomes less noisy.

2) Force actuation gating harder (reduces false positives)

Require ≥2 ORDER/ACT tokens (T1/T2) inside 72h before any PS_confirmed step-up above 55.
This prevents “proxy storms” (social media, pizza chatter, vibes) from contaminating confirmation.

3) Baseline every proxy (so “far-node sensors” become usable)

For each proxy (pizza, unusual local traffic, Google Trends, etc.):

Establish a 30–90 day baseline and only count z-score anomalies
Otherwise it stays T4 noise.

4) Add “posture resolution” sensors that are still legitimate

Use verifiable posture signals rather than folklore:

air/naval deployment announcements (official / credible)
NOTAM/airspace restrictions only when sourced as documents
embassy travel advisories / drawdowns (official)

5) Backtest 3+ cases per token weight change

This is how you stop “today’s war” from rewriting your model:

validate token weights across Soleimani 2020 + at least 2 other escalation cycles

Phase Snapshot (v1.0): War — Iran–US Theatre

Week Ending: 19 Feb 2026 (SGT)
Engine Version: v1.0 (Master Token Registry locked)

0) Snapshot Header

Window: 13 Feb → 19 Feb 2026
Domain: WAR
Theatre: Iran–US (Gulf / Levant coupling)
Tiers Used: T1/T2 primary wires & official statements only for confirmation gating
Proxies: capped (fast-only)

1) Scores

PS_fast: 68 / 100
PS_confirmed: 52 / 100

Confidence: 0.72
Volatility: HIGH
Convergence Gap: 16

Interpretation

Gap > 15 → heat > confirmation
This is loaded posture regime, not irreversible contact
P2 → early P1 boundary behavior

2) Active TTC Windows

TTC_event: ~2–4 weeks (explicit readiness by mid-March reported)
TTC_policy: open (talks ongoing)
TTC_market: active (energy risk premium proxy visible)

Reaction Window Active? YES
(Deployment tempo + diplomatic channel simultaneously live)

3) Channel Readout

STRUCTURAL_POSTURE (↑)

Carrier strike group positioning (T1/T2)
Air/naval asset concentration

LEVER_ACTUATION (moderate)

Deployment deadlines implied
No confirmed new enforceable chokepoint restrictions

IRREVERSIBLE_EVENTS (none confirmed in sources reviewed)

No verified KIN token this window

STABILIZERS / BRAKES (present)

Talks confirmed
Proposal path active

TTC_COMPRESSION (↑)

Public readiness timeline compresses optionality window

4) Top Drivers (Escalation)

CARRIER_STRIKE_GROUP_POSITIONING
FULL_DEPLOYMENT_DIRECTIVE-like readiness signal (deadline implied)
RETALIATION_EXPECTED_OFFICIAL
C2_WAR_ROOM_TEMPO (T1/T2 only instances counted)

5) Top Brakes

TALKS_CONFIRMED
PROPOSAL_SUBMITTED_WRITTEN (path signal)
DECONFLICTION_HOTLINE_ACTIVE (if verified; currently limited evidence)

6) Far-Node Sensor Vector (Capped)

Oil risk premium proxy ↑
OSINT chatter ↑
“Pizza traffic” / anomaly chatter → T4 proxy (ignored for confirmed)

Convergence Hit? NO
(No 2+ T1/T2 actuation tokens converging within 72h)

7) Trigger Watchlist

+10 (moderate move to confirmed ~60–65)

Enforceable exclusion zone declared
Sanctions enforcement escalated materially
Embassy drawdown broadens to “leave immediately” level across multiple nodes

+25 (strong move to confirmed ~75+)

Verified interdiction/seizure
Missile/drone strike confirmed
Mandatory reroute or chokepoint restriction enforced

80–100 band entry (irreversibility regime)

ATTRIBUTED_KINETIC_ACTION
NAVAL_ENGAGEMENT_CONFIRMED
PROLONGED_CHOKEPOINT_CLOSURE

8) Failure Mode Trace

			
Proxy signals (oil spike, pizza chatter) treated as confirmation
→ PS_confirmed inflated
→ fatigue sets in
→ real kinetic actuation later ignored.

9) Structural Assessment (CivOS Lens)

You are observing:

High posture density
Active diplomatic channel
Compressed TTC window
No irreversible token yet

This is classic deterrence brink zone, not open conflict.

Civilisation-level implication:

Energy + finance lanes sensitive
Supply lane coupling moderate
Education / city stability lanes unaffected unless escalation crosses into kinetic domain

10) What Would Increase Accuracy Further (Operational)

Add fixed ingestion of CENTCOM + DoD + State releases (automated T1 feed)
Add NOTAM document ingestion (actual text, not summaries)
Baseline AIS + tanker traffic statistically before counting anomalies
Require ≥2 ORDER/ACT T1/T2 within 72h before any confirmed move >55
Log every proxy spike that did NOT convert (false-spike log)

Delta vs Soleimani-style crossing

Soleimani scenario would have:
PS_fast ~75–85
PS_confirmed 85–100 immediately on KIN token
Today: posture heavy, but no KIN token confirmed

Phase Snapshot (v1.0): Finance — War→Energy→Liquidity Coupling (Iran–US)

Week Ending: 19 Feb 2026 (SGT)
Engine: Phase Monitor v1.0 (Finance pack) + War-coupling overlays

0) Snapshot Header

Window: 13 Feb → 19 Feb 2026
Domain: FINANCE
Lane: Energy Risk Premium × USD × Rates (risk-off / inflation impulse)
Sources Policy: T1/T2 for PS_confirmed; proxies capped fast-only

1) Scores

PS_fast: 61 / 100
PS_confirmed: 44 / 100

Confidence: 0.70
Volatility: HIGH
Convergence Gap: 17

Interpretation: Markets are pricing geopolitical energy risk (fast), but we do not see a finance “fracture token” (bank failure / circuit breakers / capital controls). So confirmed stays mid.

2) Active TTC Windows

TTC_event: days → weeks (war posture + Hormuz anxiety drives quick repricing) (Reuters)
TTC_policy: weeks (Fed path uncertain; “not in a rush to cut” tone increases inflation sensitivity to oil) (MarketScreener)
TTC_market: active now (oil move feeds inflation expectations & risk sentiment)

Reaction Window Active? YES (energy shock + rates narrative simultaneously live)

3) Channel Readout

STRUCTURAL_POSTURE: ↑

Energy corridor fear (Hormuz risk premium) repricing (Reuters)

LEVER_ACTUATION: low–moderate

No liquidity facility activation / capital controls / forced closures observed in T1/T2 this week

IRREVERSIBLE_EVENTS: none confirmed

No BANK_FAILURE_OR_RESOLUTION, no EXCHANGE_TRADING_HALT_OR_CLOSURE type tokens

STABILIZERS / BRAKES: mixed

Inventory draw narrative adds to oil pressure (not a stabilizer) (Reuters)
No decisive de-escalation token in the finance lane itself

TTC_COMPRESSION: ↑

Oil jumped sharply; repricing is fast (Reuters)

4) Top Drivers (max 5)

MARKET_RISK_SENSOR_OIL_SPIKE (proxy-confirmation) — Brent/WTI up sharply on conflict fears (Reuters)
IMPLIED_VOL_SPIKE_PERSISTENT (partial / indirect) — risk sentiment more fragile when oil shocks hit (watchlist) (Reuters)
FORWARD_GUIDANCE_SHIFTS_HARD (rates path “not rushing to cut” tone) (MarketScreener)
DOLLAR_STRENGTH_RISK_OFF (USD bid on data + risk) (Reuters)

5) Top Brakes (max 5)

NO_SYSTEMIC_LIQUIDITY_ACTUATION (implicit brake) — no facility / capital controls / forced closures in evidence set
CREDIT_SPREADS_TIGHT_BASELINE (context brake) — IG spreads recently described as historically tight/low, limiting “already-fractured” interpretation (Reuters)

6) Far-Node Sensor Vector (capped; fast-only)

Energy headlines & social proxies (including “pizza theory” type chatter): ignored for confirmed unless they converge with ORDER/ACT tokens
HY spread level (data-series proxy): watch, but not a fracture signal by itself (still relatively low vs long-run averages)

Convergence Hit? NO
(We have strong energy repricing, but not ≥2 T1/T2 finance actuation tokens inside 72h.)

7) Trigger Watchlist

+10 triggers (PS_confirmed → ~55)

REPO_STRESS_SPIKE confirmed in T1/T2 (funding strain headlines / official measures)
BID_ASK_WIDENS_SYSTEMIC confirmed across credit markets
sustained oil move plus clear “inflation re-acceleration” prints (tightening fears)

+25 triggers (PS_confirmed → ~70+)

CAPITAL_CONTROLS_ACTUATED (anywhere systemic)
BANK_FUNDING_STRESS confirmed + emergency backstop talk
EXCHANGE_TRADING_HALT_OR_CLOSURE / repeated breakers (equity-side fracture)

80–100 band entry (irreversibility regime)

BANK_FAILURE_OR_RESOLUTION (systemic institution)
SOVEREIGN_DEFAULT_OR_PAYMENT_FAILURE
widespread CAPITAL_CONTROLS_ACTUATED

8) Failure Mode Trace

			
Oil headline shock → interpret as “market collapse”
→ over-rotate portfolios → whipsaw losses
→ ignore real funding stress later → late response to true fracture.

9) CivOS read (why this matters)

War posture is pushing an energy price impulse. Finance can absorb it until it couples into:

inflation expectations → rate-path hardening, or
funding stress → liquidity withdrawal.

Right now: pricing pressure without finance fracture. (Reuters)

10) How to raise accuracy further (finance lane)

Add a fixed “Funding Plumbing” panel (T1/T2 only): repo operations, Treasury auction tails, official facility talk.
Add daily HY OAS + IG OAS from an authoritative time series (FRED/ICE where possible) and log changes, not anecdotes.
Enforce a hard rule: PS_confirmed can’t exceed 55 unless there’s at least one ACT/KIN finance token (facility, failure, control, halt).

Phase Snapshot (v1.0): Supply Chain — Strait of Hormuz Corridor Stress (Iran–US Coupling)

Week Ending: 19 Feb 2026 (SGT)
Engine: Supply Chain Pack v1.0 (actuation-gated) + War-coupling overlays

0) Snapshot Header

Window: 13 Feb → 19 Feb 2026
Domain: SUPPLY
Corridor: Strait of Hormuz (oil/LNG + tanker logistics + insurance)
Sources Policy: T1/T2 only for PS_confirmed gating; proxies capped fast-only

1) Scores

PS_fast: 64 / 100
PS_confirmed: 46 / 100

Confidence: 0.74
Volatility: HIGH
Convergence Gap: 18

Interpretation: Shipping stress is pricing in risk (fast), and there is official navigation guidance (confirmed lever), but we do not have a verified PORT_CLOSURE_ACTUATED / MANDATORY_REROUTE_ENFORCED / PROLONGED_CHOKEPOINT_DISRUPTION event in the T1/T2 set for this week.

2) Active TTC Windows

TTC_event: days → weeks (posture + risk premium; the corridor can reprice quickly) (Reuters)
TTC_policy: days (navigation/security guidance updates can change rapidly) (Reuters)
TTC_market: active now (freight rates + war-risk repricing moves fast)

Reaction Window Active? YES

3) Channel Readout

STRUCTURAL_POSTURE (↑)

Market focus on Hormuz as a chokepoint and risk premium embedded in oil pricing (Reuters)

LEVER_ACTUATION (moderate)

US Maritime Administration guidance for U.S.-flagged vessels: route as far as safely possible from Iranian waters; how to respond to boarding requests (this is operational navigation guidance, i.e., real lever movement—not just commentary) (Reuters)

IRREVERSIBLE EVENTS (none confirmed in T1/T2)

No verified sustained closure / enforced corridor shutdown in the sources used for confirmation gating

STABILIZERS / BRAKES (mixed)

Corridor remains open (no confirmed enforced closure in the evidence set)
Diplomacy signals exist (outside this lane) but do not, by themselves, restore corridor certainty

TTC_COMPRESSION (↑)

Tight tanker supply + tension = spot rate spikes (proxy that stress is translating into logistics cost) (Bloomberg.com)

4) Top Drivers (max 5)

FREIGHT_RATE_SPIKE_PROXY — Baltic Exchange route earnings / tanker rates spike (proxy, baseline required) (Bloomberg.com)
INSURANCE_COVERAGE_WITHDRAWAL (watchlist) — not confirmed as a withdrawal this week, but insurance/risk pricing is a key hinge (see triggers below)
MANDATORY_REROUTE_ENFORCED (not confirmed; only upgrades if enforceable restrictions appear)
MARKET_RISK_SENSOR_OIL_SPIKE — oil risk premium focuses attention on Hormuz corridor (proxy-confirmation only) (Reuters)
CONGESTION_INDEX_SPIKE_PROXY (not confirmed this week; keep capped unless you have a baseline series)

5) Top Brakes (max 5)

NO_PORT_CLOSURE_ACTUATED (implicit brake) — no T1/T2-confirmed port/strait closure actuation in the confirmation set
CORRIDOR_REOPENING_CONFIRMED not applicable (because closure not confirmed)
“Insurance premiums have yet to rise” (context brake per industry reporting; treat as conditional because this can flip quickly) (Lloyd’s List)

6) Far-Node Sensor Vector (capped; fast-only)

Oil risk premium up (proxy) (Reuters)
Tanker spot rates up (proxy; baseline required) (Bloomberg.com)
“Pizza/odd proxies”: remain T4; ignored for confirmed unless they converge with T1/T2 actuation

Convergence Hit? PARTIAL
We have a real operational guidance token (T1) plus freight proxy stress, but we do not yet have ≥2 additional T1/T2 actuation/closure/restriction tokens in the last 72h to promote PS_confirmed meaningfully.

7) Trigger Watchlist

+10 triggers (PS_confirmed → ~55)

INSURANCE_COVERAGE_WITHDRAWAL documented by major insurers/market bulletins (T1/T2)
CONGESTION_SATURATION_CONFIRMED across key Gulf load/discharge ports (T1/T2)
Repeated official navigation warnings expanding in scope (multiple flag states / coalitions)

+25 triggers (PS_confirmed → ~70+)

INTERDICTION_SEIZURE (boarding/seizure) confirmed in T1/T2
AIRSPACE_RESTRICTION_ACTUATION / enforced maritime exclusion zones affecting routing
EXPORT_BAN_ACTUATED / ALLOCATION_REGIME_CONFIRMED on critical energy products

80–100 band entry (irreversibility regime)

PROLONGED_CHOKEPOINT_DISRUPTION (days→weeks, corridor-wide)
STRUCTURAL_CORRIDOR_REDIRECTION_CONFIRMED (multi-month reroute normalization)
Formal expansion of “Listed Areas” / war-risk designation changes that structurally reprice the corridor (watch the London market machinery—e.g., Joint War Committee processes) (lmalloyds.com)

8) Failure Mode Trace

			
Oil headline + proxy chatter → assume “Hormuz closed”
→ overreact (reroute/hoard) → self-inflicted congestion
→ real interdiction/insurance withdrawal arrives later → too late to adapt.

9) CivOS Read (why this lane matters)

This is the bridge lane where war posture becomes real economy load:

If Hormuz risk converts into insurance withdrawal + enforced reroutes, you get structural cost and delay (Supply P2→P1→P0 corridor).
Right now you have pricing + guidance, not confirmed prolonged disruption. (Reuters)

10) How to raise accuracy further (Supply lane)

Add a weekly “War-Risk Insurance Panel” (T1/T2 only): quoted additional premium ranges, listed area changes, insurer advisories. (Tie to JWC “Listed Areas” updates.) (lmalloyds.com)
Create a baseline series for TD3C / Baltic Exchange and only count z-score anomalies for FREIGHT_RATE_SPIKE_PROXY. (Bloomberg.com)
Add a strict rule: PS_confirmed cannot exceed 55 without at least one of: PORT_CLOSURE_ACTUATED, INTERDICTION_SEIZURE, INSURANCE_COVERAGE_WITHDRAWAL (T1/T2).

Iran–US System State Dashboard (v1.0)

Week Ending: 19 Feb 2026 (SGT)
Engine: Phase Monitor v1.0 (War + Finance + Supply)

0) Core scores (this week)

Domain	PS_fast	PS_confirmed	Confidence	Volatility	Convergence Gap
War (Iran–US)	68	52	0.72	HIGH	16
Finance (Energy→Liquidity)	61	44	0.70	HIGH	17
Supply (Hormuz corridor)	64	46	0.74	HIGH	18

System read: high heat everywhere, but actuation-gated confirmation is still mid-range.

1) Coupled-Lane Composite Score

Composite (confirmed)

I’m using a strict multiplicative coupling (your “lattice coupling” idea):
[
\text{Composite}_{confirmed}=\left(\frac{52}{100}\right)\left(\frac{46}{100}\right)\left(\frac{44}{100}\right)\times 100
\approx \mathbf{10.5}
]

Composite_confirmed: 10.5 / 100

Composite (fast)

[
\text{Composite}_{fast}=\left(\frac{68}{100}\right)\left(\frac{64}{100}\right)\left(\frac{61}{100}\right)\times 100
\approx \mathbf{26.5}
]

Composite_fast: 26.5 / 100

Interpretation

Fast > Confirmed is exactly what you want in a non-kinetic brink regime: the system is hot, but not yet locked into irreversibility.
The multiplicative form means: you only get a high composite when all three lanes actuate together (war + logistics + finance plumbing).

2) What’s actually driving the system (one-line each)

War lane (confirmed 52): posture density + deadline-like readiness window, but no verified KIN token.
Supply lane (confirmed 46): corridor risk + operational guidance, but no enforced closure / interdiction / insurance withdrawal.
Finance lane (confirmed 44): energy repricing + risk sentiment, but no funding/credit fracture token (no facility activation, no failures, no halts).

3) The 3 “hinge” triggers that would jump the composite

These are the minimum set that would push the coupled system up meaningfully:

Hinge A — War becomes irreversible

ATTRIBUTED_KINETIC_ACTION / MISSILE_ATTACK_CONFIRMED / NAVAL_ENGAGEMENT_CONFIRMED

Hinge B — Hormuz becomes operationally constrained

INTERDICTION_SEIZURE or INSURANCE_COVERAGE_WITHDRAWAL or MANDATORY_REROUTE_ENFORCED

Hinge C — Finance shows plumbing stress (not just oil up)

REPO_STRESS_SPIKE or LIQUIDITY_WITHDRAWAL / systemic BID_ASK_WIDENS_SYSTEMIC

If you see any 2 of these within 72h (T1/T2), PS_confirmed in multiple lanes will step up and Composite_confirmed will climb sharply.

4) Accuracy guardrails (so this dashboard doesn’t drift)

Hard caps:

Composite_confirmed should not rise materially unless at least one ACT/KIN token appears in two of the three lanes inside 72h.
Proxies (oil spikes, chatter, “pizza”) can raise Composite_fast, never Composite_confirmed.

Composite Token Router v1.0 (Almost-Code)

War ↔ Supply ↔ Finance Coupling Matrix + Trigger Ladder (v1.0)

0) Purpose

Convert single-lane signals into a coupled system state without double-counting hype.

War tokens can route into Supply + Finance via chokepoints/insurance/energy.
Supply tokens can route into Finance via logistics cost + inflation + funding stress.
Finance tokens can amplify War/Supply volatility (risk-off feedback), but do not “cause” war.

1) Canonical Objects

			
Lane := { WAR, SUPPLY, FINANCE }
State := {
  PS_fast[Lane]      : 0..100,
  PS_confirmed[Lane] : 0..100,
  Confidence[Lane]   : 0..1,
  Volatility[Lane]   : {LOW, MED, HIGH}
}
Token := { id, lane, class, tier, polarity, base_weight, proxy_flag, timestamp }
Class := { RHET, POST, READY, ORDER, ACT, KIN }
Tier  := { T1, T2, T3, T4 }

		

2) Bridge Binds (the only allowed cross-lane routes)

WAR → SUPPLY (chokepoint / interdiction / insurance)

			
BridgeBind WAR_SUPPLY := {
  allowed_tokens: [
    CHOKEPOINT_ACTUATION,
    INTERDICTION_SEIZURE,
    AIRSPACE_RESTRICTION_ACTUATION,
    PROLONGED_CHOKEPOINT_CLOSURE,
    NAVAL_ENGAGEMENT_CONFIRMED
  ],
  weight: 0.70,
  gate: requires (class ∈ {ORDER, ACT, KIN}) AND (tier ∈ {T1, T2})
}

		

WAR → FINANCE (energy risk premium → risk-off / inflation impulse)

			
BridgeBind WAR_FIN := {
  allowed_tokens: [
    ATTRIBUTED_KINETIC_ACTION,
    MISSILE_ATTACK_CONFIRMED,
    NAVAL_ENGAGEMENT_CONFIRMED,
    PROLONGED_CHOKEPOINT_CLOSURE,
    SANCTIONS_ENFORCEMENT_STEP
  ],
  weight: 0.55,
  gate: requires (class ∈ {ACT, KIN}) AND (tier ∈ {T1, T2})
}

		

SUPPLY → FINANCE (logistics cost → inflation expectations → policy/funding strain)

			
BridgeBind SUPPLY_FIN := {
  allowed_tokens: [
    PORT_CLOSURE_ACTUATED,
    EXPORT_BAN_ACTUATED,
    ALLOCATION_REGIME_CONFIRMED,
    INSURANCE_COVERAGE_WITHDRAWAL,
    PROLONGED_CHOKEPOINT_DISRUPTION,
    STRUCTURAL_CORRIDOR_REDIRECTION_CONFIRMED
  ],
  weight: 0.65,
  gate: requires (class ∈ {ACT, KIN}) AND (tier ∈ {T1, T2})
}

		

No other cross-lane routes are permitted (prevents narrative leakage).

3) Coupling Matrix (system-level)

			
CouplingMatrix K :=
  WAR→SUPPLY   = 0.70
  WAR→FINANCE  = 0.55
  SUPPLY→FIN   = 0.65
  (all other directions default 0.00)

		

4) Routing Function (how a token affects other lanes)

			
Route(token t):
  if t.proxy_flag == true:
      return  # proxies never route into confirmed states
  # Only route if token passes the bind gate
  for each bind B where t.lane == B.source_lane and t.id ∈ B.allowed_tokens:
      if GatePass(t, B.gate):
          routed_impact := Impact(t) * B.weight
          AddToCrossLaneBuffer(B.target_lane, routed_impact, ttl=72h)

		

Where:

Impact(t) := base_weight * Rel(t.tier) * Act(t.class) * Sign(t.polarity)

5) Cross-Lane Buffer Integration (prevents double counting)

			
IntegrateCrossLane(Lane L):
  cross := Sum(CrossLaneBuffer[L] within last 72h)
  # cross only modifies PS_fast by default
  PS_fast[L] += clamp(cross, -5, +5)
  # cross modifies PS_confirmed ONLY if L has its own actuation gate satisfied
  if ConfirmedGateSatisfied(L, last72h):
      PS_confirmed[L] += clamp(0.50*cross, -3, +3)
  else:
      # damped: do not “confirm” via routing alone
      PS_confirmed[L] += 0

		

Rule: A lane must earn its own confirmation (ORDER/ACT/KIN + T1/T2) before routing can lift its confirmed score.

6) Composite Score (coupled system)

			
Composite_confirmed :=
  (PS_confirmed[WAR]/100) *
  (PS_confirmed[SUPPLY]/100) *
  (PS_confirmed[FINANCE]/100) * 100
Composite_fast :=
  (PS_fast[WAR]/100) *
  (PS_fast[SUPPLY]/100) *
  (PS_fast[FINANCE]/100) * 100

		

7) Composite Trigger Ladder (system-level)

+10 Composite_confirmed move (moderate)

Requires 2-of-3 lanes with new T1/T2 ORDER/ACT tokens within 72h.

			
Condition_Mod :=
  CountLanesWithNewActuationTokens(last72h) ≥ 2

+25 Composite_confirmed move (strong)

Requires (WAR KIN) OR (SUPPLY ACT chokepoint) plus one more lane actuation within 72h.

			
Condition_Strong :=
  (Exists WAR token class=KIN tier∈{T1,T2} last72h)
  OR
  (Exists SUPPLY token id∈{PORT_CLOSURE_ACTUATED, INTERDICTION_SEIZURE, INSURANCE_COVERAGE_WITHDRAWAL} class∈{ACT,KIN} tier∈{T1,T2} last72h)
  AND
  CountLanesWithNewActuationTokens(last72h) ≥ 2

		

80–100 band entry (irreversibility regime)

Requires WAR KIN + SUPPLY disruption or WAR KIN + FINANCE plumbing stress.

			
Condition_Irreversible :=
  (Exists WAR KIN tier∈{T1,T2})
  AND
  (
    Exists SUPPLY token id∈{PROLONGED_CHOKEPOINT_DISRUPTION, PORT_CLOSURE_ACTUATED, STRUCTURAL_CORRIDOR_REDIRECTION_CONFIRMED} class∈{ACT,KIN} tier∈{T1,T2}
    OR
    Exists FINANCE token id∈{REPO_STRESS_SPIKE, LIQUIDITY_WITHDRAWAL, BANK_FAILURE_OR_RESOLUTION, EXCHANGE_TRADING_HALT_OR_CLOSURE} class∈{ACT,KIN} tier∈{T1,T2}
  )

		

8) Failure Mode Trace (required)

			
Unrestricted routing → war headlines “confirm” finance/supply → composite inflates → false alarms → trust decay → real coupled actuation ignored.

9) Minimal “Run” Prompt (for any LLM)

Tokenize each lane separately (T1–T4, RHET–KIN).
Compute lane PS_fast / PS_confirmed with gating.
Route only allowed bridge tokens through binds into cross-lane buffers.
Integrate buffers with confirmed-gate rule.
Output Composite_fast / Composite_confirmed + Trigger Ladder status.

Coupling Backtest Template (WAR→SUPPLY→FIN) (Evidence-Locked) (v1.0)

Purpose

This template validates the Coupling Matrix K and Bridge Binds so routing doesn’t become narrative drift.
We don’t “tune to headlines.” We tune to truth spines + lane actuation and measure lead/lag accuracy.

0) What a coupling backtest must prove

A valid coupling backtest shows WAR actuation → SUPPLY actuation → FINANCE actuation (or WAR→FIN) with:

correct ordering (lead/lag)
correct gating (confirmed doesn’t move without ORDER/ACT/KIN)
correct composite behavior (fast rises early; confirmed rises only on actuations)
low false positives

1) Backtest Object (canonical)

			
CouplingBacktest := {
  id: STRING,
  name: STRING,
  event_window: {start: YYYY-MM-DD, end: YYYY-MM-DD},
  theatres: [STRING...],
  lanes: [WAR, SUPPLY, FINANCE],
  truth_spine: {
    WAR:    [TruthEvent...],
    SUPPLY: [TruthEvent...],
    FIN:    [TruthEvent...]
  },
  token_series: {
    WAR:    [TokenDay...],
    SUPPLY: [TokenDay...],
    FIN:    [TokenDay...]
  },
  run_series: {
    WAR:    [RunDay...],
    SUPPLY: [RunDay...],
    FIN:    [RunDay...],
    COMPOSITE: [CompositeDay...]
  },
  evaluation: {
    lead_lag_days: { WAR_to_SUPPLY, WAR_to_FIN, SUPPLY_to_FIN },
    detection: { first_PS_fast_warning, first_PS_confirmed_crossing },
    false_spikes: [Spike...],
    missed_signals: [Miss...],
    routing_audit: [RoutingAudit...],
    weight_updates: [WeightUpdate...]
  }
}

		

2) Truth Event (ground truth spine)

Truth events are irreversible lane markers (not commentary).

			
TruthEvent := {
  date: YYYY-MM-DD,
  lane: WAR|SUPPLY|FINANCE,
  label: STRING,                     # e.g. "interdiction confirmed", "facility activated"
  class: ACT|KIN,                     # truth spine uses only ACT/KIN
  evidence_ref: STRING                # T1 source reference
}

		

3) Daily Token List (per lane)

			
TokenDay := {
  date: YYYY-MM-DD,
  tokens: [Token...]
}

Token schema uses your Master Grammar:

			
Token := { id, lane, class, tier, polarity, base_weight, proxy_flag, evidence_ref }

4) Daily Run Output (per lane)

			
RunDay := {
  date: YYYY-MM-DD,
  PS_fast: 0..100,
  PS_confirmed: 0..100,
  Confidence: 0..1,
  Volatility: LOW|MED|HIGH,
  TopDrivers: [token_id...],
  TopBrakes:  [token_id...]
}

		

Composite:

			
CompositeDay := {
  date: YYYY-MM-DD,
  Composite_fast: 0..100,
  Composite_confirmed: 0..100,
  TriggerStatus: {MOD, STRONG, IRREVERSIBLE, NONE},
  ConvergenceNote: STRING
}

		

5) Routing Audit (the most important piece)

This proves routing didn’t “invent confirmation.”

			
RoutingAudit := {
  date: YYYY-MM-DD,
  routed_tokens: [
    {
      source_lane: WAR|SUPPLY|FINANCE,
      token_id: STRING,
      target_lane: WAR|SUPPLY|FINANCE,
      bind: "WAR_SUPPLY"|"WAR_FIN"|"SUPPLY_FIN",
      gate_passed: BOOL,
      routed_impact: FLOAT,           # post-weight
      applied_to: "fast_only"|"confirmed_allowed"|"blocked",
      reason: STRING
    } ...
  ]
}

		

Hard rule: any routed token with proxy_flag=true must show applied_to="blocked" for confirmed.

6) Evaluation Metrics (evidence-lock)

6.1 Lead/Lag (expected ordering)

			
lead_lag_days :=
  WAR_to_SUPPLY   = date_of_first_SUPPLY_confirmed_jump - date_of_first_WAR_confirmed_jump
  WAR_to_FIN      = date_of_first_FIN_confirmed_jump    - date_of_first_WAR_confirmed_jump
  SUPPLY_to_FIN   = date_of_first_FIN_confirmed_jump    - date_of_first_SUPPLY_confirmed_jump

6.2 Detection

			
first_PS_fast_warning :=
  earliest date where Composite_fast ≥ 15
first_PS_confirmed_crossing :=
  earliest date where Composite_confirmed ≥ 15

(Adjust thresholds per your historical distribution later; start here.)

6.3 False Spike Definition

			
Spike := {
  date: YYYY-MM-DD,
  lane: WAR|SUPPLY|FINANCE|COMPOSITE,
  type: "FAST_FALSE"|"CONFIRMED_FALSE",
  magnitude: FLOAT,
  cause_tokens: [token_id...],
  why_false: STRING
}

		

A confirmed false occurs if PS_confirmed crosses your action threshold without a matching truth-spine ACT/KIN event within ±3 days.

6.4 Miss Definition

			
Miss := {
  truth_date: YYYY-MM-DD,
  lane: WAR|SUPPLY|FINANCE,
  truth_label: STRING,
  expected_signal: "PS_fast"|"PS_confirmed",
  miss_reason: STRING,
  missing_tokens: [token_id...]
}

		

7) Weight Update Governance (non-negotiable)

			
WeightUpdate := {
  token_id: STRING,
  component: "base_weight"|"bind_weight",
  old: FLOAT,
  new: FLOAT,
  reason: STRING,
  validated_on_backtests: [BacktestID...],    # MUST be ≥3 before promotion
  promotion_status: "PROPOSED"|"PROMOTED"
}

		

Rule: no change is promoted unless validated on ≥3 coupling backtests.

8) Standard Coupling Backtest Cases (starter set)

Use any 3+ you like; the point is diversity.

Case types you need (not optional)

WAR→SUPPLY dominant: interdictions / chokepoint stress
SUPPLY→FIN dominant: export bans / prolonged disruption → inflation/rates/funding
WAR→FIN dominant: kinetic event → risk-off/funding stress (if it happens)

9) Failure Mode Trace (required)

			
No coupling backtests → bind weights tuned to one crisis → routing “confirms” other lanes → composite inflation → false alarms → system ignored when real coupling arrives.

10) Minimal “Backtest Run” Procedure (Operator playbook)

Lock the event window + truth spines (T1 only).
Tokenize daily per lane (dedup + tier + class).
Compute lane runs (PS_fast/confirmed).
Run routing (Bridge Binds only) + audit every routed token.
Compute composite series + trigger status.
Score lead/lag, false spikes, misses.
Propose weight updates (but don’t promote until 3+ cases).

Backtest-004 (Coupling) — Gulf Tanker Seizure Cycle 2019 (WAR→SUPPLY→FIN) (v1.0)

Backtest ID: BT-004
Event Window: 2019-05-10 → 2019-08-05
Theatre: Strait of Hormuz / Gulf of Oman (Iran–US/UK corridor coupling)
Goal: Validate WAR→SUPPLY→FIN routing + confirm the actuation gates prevent proxy-driven false confirmation.

0) Why this is a good coupling case (1 paragraph)

This cycle has clean bridge binds:

WAR lane: ship seizures / interdiction escalation (kinetic contact in maritime domain)
SUPPLY lane: war-risk insurance “Listed Areas” expansion (risk reclassification) + navigation risk + reroute pressure
FIN lane: oil risk premium repricing (not a banking fracture, but a finance response)

It’s ideal for validating: war actuation pushes supply constraints (insurance risk regime), which pushes finance pricing — without requiring a full financial plumbing crisis.

1) Truth Spine (T1/T2 only; irreversible/actuation markers)

Rule: truth events must be ACT/KIN, not commentary.

WAR Truth Events

2019-07-19 — INTERDICTION_SEIZURE / seizure of British-flagged Stena Impero (KIN) (The Guardian)
2019-07-04 — UK seizure of Iranian tanker Grace 1 (ACT/KIN context precursor) (U.S. Naval Institute)

SUPPLY Truth Events (insurance / risk reclassification)

2019-05-17 — Joint War Committee expands “Listed Areas” to include Oman/UAE and Gulf waters (ACT: risk regime change) (Baltic Exchange Consumer)

FINANCE Truth Events (pricing regime response)

2019-07-18/22 — oil price jump linked to tanker seizure escalation (ACT-ish market reaction; still not “plumbing fracture”) (Bloomberg.com)

2) Backtest Inputs (paste-ready)

2.1 Coupling Matrix (locked for this backtest)

			
K:
  WAR→SUPPLY  = 0.70
  WAR→FIN     = 0.55
  SUPPLY→FIN  = 0.65

2.2 Allowed Bridge Binds (locked)

			
WAR→SUPPLY allowed: CHOKEPOINT_ACTUATION, INTERDICTION_SEIZURE, AIRSPACE_RESTRICTION_ACTUATION,
                    PROLONGED_CHOKEPOINT_CLOSURE, NAVAL_ENGAGEMENT_CONFIRMED
WAR→FIN allowed:    ATTRIBUTED_KINETIC_ACTION, MISSILE_ATTACK_CONFIRMED, NAVAL_ENGAGEMENT_CONFIRMED,
                    PROLONGED_CHOKEPOINT_CLOSURE, SANCTIONS_ENFORCEMENT_STEP
SUPPLY→FIN allowed: PORT_CLOSURE_ACTUATED, EXPORT_BAN_ACTUATED, ALLOCATION_REGIME_CONFIRMED,
                    INSURANCE_COVERAGE_WITHDRAWAL, PROLONGED_CHOKEPOINT_DISRUPTION,
                    STRUCTURAL_CORRIDOR_REDIRECTION_CONFIRMED

		

3) Token Series (Filled Skeleton: key days filled, rest templated)

Operator note: You only need to fill tokens on “signal days.” For quiet days, keep empty arrays.

3.1 WAR tokens (key days)

			
[
  {
    "date": "2019-07-04",
    "tokens": [
      {
        "id": "INTERDICTION_SEIZURE",
        "lane": "WAR",
        "class": "ACT",
        "tier": "T2",
        "polarity": "ESCALATE",
        "base_weight": 16,
        "proxy_flag": false,
        "evidence_ref": "USNI: Grace 1 seized at Gibraltar (context precursor)"
      }
    ]
  },
  {
    "date": "2019-07-19",
    "tokens": [
      {
        "id": "INTERDICTION_SEIZURE",
        "lane": "WAR",
        "class": "KIN",
        "tier": "T2",
        "polarity": "ESCALATE",
        "base_weight": 16,
        "proxy_flag": false,
        "evidence_ref": "Seizure of Stena Impero (Guardian/USNI/Economist)"
      }
    ]
  }
]

		

Evidence: (U.S. Naval Institute)

3.2 SUPPLY tokens (key days)

			
[
  {
    "date": "2019-05-17",
    "tokens": [
      {
        "id": "INSURANCE_COVERAGE_WITHDRAWAL",
        "lane": "SUPPLY",
        "class": "ACT",
        "tier": "T2",
        "polarity": "ESCALATE",
        "base_weight": 12,
        "proxy_flag": false,
        "evidence_ref": "JWC Listed Areas expanded (risk regime change)"
      }
    ]
  }
]

		

Evidence: (Lloyd’s List)

Note: If you prefer to keep INSURANCE_COVERAGE_WITHDRAWAL only for literal withdrawal, swap this token to a dedicated one like WAR_RISK_LISTED_AREA_EXPANSION (recommended as a v1.1 token). For v1.0 skeleton, we park it here as “insurance actuation.”

3.3 FINANCE tokens (key days)

			
[
  {
    "date": "2019-07-18",
    "tokens": [
      {
        "id": "MARKET_RISK_SENSOR_OIL_SPIKE",
        "lane": "FINANCE",
        "class": "POST",
        "tier": "T2",
        "polarity": "ESCALATE",
        "base_weight": 4,
        "proxy_flag": true,
        "evidence_ref": "Oil jumped as tanker seizures escalated"
      }
    ]
  },
  {
    "date": "2019-07-22",
    "tokens": [
      {
        "id": "MARKET_RISK_SENSOR_OIL_SPIKE",
        "lane": "FINANCE",
        "class": "POST",
        "tier": "T2",
        "polarity": "ESCALATE",
        "base_weight": 4,
        "proxy_flag": true,
        "evidence_ref": "Oil prices rose after tanker seizure"
      }
    ]
  }
]

		

Evidence: (Bloomberg.com)

4) Routing Audit (Filled Skeleton: show that routing does NOT “confirm” other lanes)

4.1 Routing audit — 2019-07-19

			
{
  "date": "2019-07-19",
  "routed_tokens": [
    {
      "source_lane": "WAR",
      "token_id": "INTERDICTION_SEIZURE",
      "target_lane": "SUPPLY",
      "bind": "WAR_SUPPLY",
      "gate_passed": true,
      "routed_impact": "+(Impact)*0.70",
      "applied_to": "fast_only",
      "reason": "SUPPLY confirmed gate not satisfied by its own ORDER/ACT/KIN token in last 72h (unless insurance actuation logged in-window)."
    },
    {
      "source_lane": "WAR",
      "token_id": "INTERDICTION_SEIZURE",
      "target_lane": "FINANCE",
      "bind": "WAR_FIN",
      "gate_passed": true,
      "routed_impact": "+(Impact)*0.55",
      "applied_to": "fast_only",
      "reason": "Finance lane has no ACT/KIN plumbing token; price proxies remain proxy_flag=true and cannot confirm."
    }
  ]
}

		

4.2 Routing audit — 2019-05-17

			
{
  "date": "2019-05-17",
  "routed_tokens": [
    {
      "source_lane": "SUPPLY",
      "token_id": "INSURANCE_COVERAGE_WITHDRAWAL",
      "target_lane": "FINANCE",
      "bind": "SUPPLY_FIN",
      "gate_passed": true,
      "routed_impact": "+(Impact)*0.65",
      "applied_to": "fast_only",
      "reason": "Finance confirmed gate not satisfied by ACT/KIN finance token; routed impact can only lift PS_fast."
    }
  ]
}

		

5) Run Series (Filled Skeleton: expected shape)

You can paste real computed values later. For now, this is the expected pattern that validates the model.

5.1 Expected lane behavior

WAR: PS_confirmed spikes on 2019-07-19 (KIN seizure) (The Guardian)
SUPPLY: PS_fast rises on war-risk Listed Areas expansion (2019-05-17) (Lloyd’s List)
FINANCE: PS_fast rises with oil jump, but PS_confirmed stays capped (no funding/plumbing ACT/KIN) (Bloomberg.com)

5.2 Composite expected shape

Composite_fast: climbs to moderate levels (war + supply + finance pricing)
Composite_confirmed: stays low (because finance + supply confirmed remain below actuation thresholds)

This is a good result: it proves the model does not scream “systemic” when only pricing is reacting.

6) Evaluation (Filled Skeleton)

6.1 Lead/Lag (qualitative for BT-004)

WAR→SUPPLY: same-day / next-week depending on which supply token you treat as actuation (insurance listing was earlier; seizures amplify) (Lloyd’s List)
WAR→FIN: same-day fast repricing (oil) (Bloomberg.com)
SUPPLY→FIN: fast repricing; confirmed should still not exceed cap unless finance plumbing actuates

6.2 False spikes (what you should see: NONE in confirmed)

Any spike in Composite_confirmed without a finance ACT/KIN token is a failure.

6.3 Misses (what to check)

If your WAR confirmed didn’t jump on 2019-07-19, your WAR tokenization is broken.
If your SUPPLY lane never reacts to war-risk listing expansion, you need a dedicated token in v1.1.

7) Weight Update Proposals (v1.0 → v1.1 candidates)

Proposal 1: Add a dedicated supply token:

WAR_RISK_LISTED_AREA_EXPANSION (SUPPLY / ACT / base_weight ~12)
Supported by JWC listing changes coverage. (Lloyd’s List)

Proposal 2: Keep MARKET_RISK_SENSOR_OIL_SPIKE as proxy-only forever

Oil price is a confirmation of fear, not confirmation of actuation.

8) Failure Mode Trace (required)

			
Oil spikes treated as confirmation → composite_confirmed inflates → repeated false alarms → trust collapses → real interdiction/closure later gets ignored.

9) Operator “Fill-in” Checklist (what you paste next)

[ ] Daily token arrays (only key days needed)
[ ] Evidence refs (T1/T2 links) for each key token
[ ] Computed PS series (optional; can be added later)
[ ] Routing audit JSON entries for any routed token

Backtest-005 (Coupling) — Energy Supply Shock → Utility Liquidity / Bailouts 2022 (SUPPLY→FIN confirmed) (v1.0)

Backtest ID: BT-005
Event Window: 2022-06-01 → 2022-12-31
Theatre: Europe energy corridor (gas/power)
Goal: Validate SUPPLY→FIN routing where logistics/energy constraints become confirmed finance actuation (bailouts, emergency credit lines, collateral/liquidity stress).

This is the missing half of your coupling validation set: a case where supply disruption is not just “prices up” but produces finance plumbing actions.

0) Why this is a good coupling case (1 paragraph)

In 2022, energy supply constraints (pipeline reductions, allocation/rationing policies, emergency market rules, extreme power/gas prices) created liquidity/collateral crises for utilities and forced state-backed support measures (bailouts, guarantees, credit lines). This is exactly SUPPLY→FIN confirmed coupling: actuation in supply drives actuation in finance, not merely proxy price movement.

1) Truth Spine (ACT/KIN only; T1 evidence refs you paste)

SUPPLY Truth Events (actuation in the corridor)

Choose 2–4 concrete anchors (examples):

ALLOCATION_REGIME_CONFIRMED — rationing / emergency allocation rules enacted
EXPORT_BAN_ACTUATED — export restrictions on energy / critical inputs (if applicable)
PROLONGED_CHOKEPOINT_DISRUPTION — sustained supply reduction beyond routine variability
STRUCTURAL_CORRIDOR_REDIRECTION_CONFIRMED — multi-month corridor redesign (new terminals, long-term sourcing shifts)

TruthEvent skeleton

			
{ date:"YYYY-MM-DD", lane:SUPPLY, label:"...", class:ACT, evidence_ref:"T1 link" }

FINANCE Truth Events (confirmed plumbing / institutional actions)

Pick anchors that are clearly ACT/KIN:

BACKSTOP_PROGRAM_EXPANDED (or EMERGENCY_LIQUIDITY_FACILITY_ACTIVATED) — government/central bank/treasury support program
BANK_FUNDING_STRESS / LIQUIDITY_WITHDRAWAL (if documented at systemic level)
BANK_FAILURE_OR_RESOLUTION (only if actually in window; not required)
Utility bailout / nationalization / guarantee (treat as BACKSTOP_PROGRAM_EXPANDED in v1.0)

TruthEvent skeleton

			
{ date:"YYYY-MM-DD", lane:FINANCE, label:"...", class:ACT, evidence_ref:"T1 link" }

2) Coupling Inputs (locked)

2.1 Coupling Matrix

			
K:
  WAR→SUPPLY  = 0.70
  WAR→FIN     = 0.55
  SUPPLY→FIN  = 0.65

2.2 Bridge Bind used (primary)

			
SUPPLY→FIN allowed:
  PORT_CLOSURE_ACTUATED,
  EXPORT_BAN_ACTUATED,
  ALLOCATION_REGIME_CONFIRMED,
  INSURANCE_COVERAGE_WITHDRAWAL,
  PROLONGED_CHOKEPOINT_DISRUPTION,
  STRUCTURAL_CORRIDOR_REDIRECTION_CONFIRMED
gate: class ∈ {ACT,KIN} AND tier ∈ {T1,T2}

		

3) Token Series (Filled Skeleton: you paste evidence refs)

3.1 SUPPLY tokens (key days only)

			
[
  {
    "date": "2022-06-15",
    "tokens": [
      {
        "id": "PROLONGED_CHOKEPOINT_DISRUPTION",
        "lane": "SUPPLY",
        "class": "ACT",
        "tier": "T1",
        "polarity": "ESCALATE",
        "base_weight": 20,
        "proxy_flag": false,
        "evidence_ref": "PASTE T1: sustained supply cut / constraint confirmed"
      }
    ]
  },
  {
    "date": "2022-08-10",
    "tokens": [
      {
        "id": "ALLOCATION_REGIME_CONFIRMED",
        "lane": "SUPPLY",
        "class": "ACT",
        "tier": "T1",
        "polarity": "ESCALATE",
        "base_weight": 14,
        "proxy_flag": false,
        "evidence_ref": "PASTE T1: allocation/rationing/emergency market rule enacted"
      }
    ]
  }
]

		

3.2 FINANCE tokens (key days only)

			
[
  {
    "date": "2022-09-05",
    "tokens": [
      {
        "id": "BACKSTOP_PROGRAM_EXPANDED",
        "lane": "FINANCE",
        "class": "ACT",
        "tier": "T1",
        "polarity": "DEESCALATE",
        "base_weight": 12,
        "proxy_flag": false,
        "evidence_ref": "PASTE T1: government guarantee / bailout / emergency credit line"
      }
    ]
  },
  {
    "date": "2022-09-06",
    "tokens": [
      {
        "id": "BID_ASK_WIDENS_SYSTEMIC",
        "lane": "FINANCE",
        "class": "ACT",
        "tier": "T2",
        "polarity": "ESCALATE",
        "base_weight": 12,
        "proxy_flag": false,
        "evidence_ref": "PASTE T2: documented market liquidity stress (if available)"
      }
    ]
  }
]

		

3.3 Proxy tokens (allowed, fast-only)

			
[
  {
    "date": "2022-08-20",
    "tokens": [
      {
        "id": "MARKET_RISK_SENSOR_OIL_SPIKE",
        "lane": "FINANCE",
        "class": "POST",
        "tier": "T2",
        "polarity": "ESCALATE",
        "base_weight": 4,
        "proxy_flag": true,
        "evidence_ref": "PASTE T2: energy prices spike headline"
      }
    ]
  }
]

		

4) Routing Audit (this is the proof)

4.1 Routing audit — supply actuation routes into finance

			
{
  "date": "2022-06-15",
  "routed_tokens": [
    {
      "source_lane": "SUPPLY",
      "token_id": "PROLONGED_CHOKEPOINT_DISRUPTION",
      "target_lane": "FINANCE",
      "bind": "SUPPLY_FIN",
      "gate_passed": true,
      "routed_impact": "+(Impact)*0.65",
      "applied_to": "fast_only",
      "reason": "Finance confirmed gate not yet satisfied by its own ACT/KIN token inside 72h."
    }
  ]
}

		

4.2 Routing audit — once finance actuation appears, routing may lift confirmed slightly

			
{
  "date": "2022-09-05",
  "routed_tokens": [
    {
      "source_lane": "SUPPLY",
      "token_id": "ALLOCATION_REGIME_CONFIRMED",
      "target_lane": "FINANCE",
      "bind": "SUPPLY_FIN",
      "gate_passed": true,
      "routed_impact": "+(Impact)*0.65",
      "applied_to": "confirmed_allowed",
      "reason": "Finance confirmed gate satisfied by BACKSTOP_PROGRAM_EXPANDED (T1 ACT) within 72h."
    }
  ]
}

		

Hard rule check: any proxy token must show applied_to:"blocked" for confirmed.

5) Expected Run Shape (calibration target)

SUPPLY lane

PS_fast rises early on supply constraint news
PS_confirmed rises on ACT tokens: allocation regime / prolonged disruption / enforceable rules

FINANCE lane

PS_fast rises with energy repricing (proxy)
PS_confirmed rises only when ACT finance measures appear:
BACKSTOP_PROGRAM_EXPANDED / EMERGENCY_LIQUIDITY_FACILITY_ACTIVATED
or systemic funding stress tokens

Composite behavior

Composite_fast climbs early
Composite_confirmed stays low until both supply actuation and finance actuation occur
When both occur inside 72h, composite_confirmed steps up materially

6) Evaluation (what “success” looks like)

Lead/Lag expectations

SUPPLY confirmed should lead FINANCE confirmed by 0–21 days (depending on policy response speed)

False spike constraints

If FINANCE PS_confirmed jumps above 55 without a finance ACT/KIN truth event, mark as CONFIRMED_FALSE

Miss constraints

If finance support actions occur but PS_confirmed remains flat, tokenization is missing or gating too strict.

7) Weight Update Proposals (v1.1 candidates)

This backtest almost always reveals the need for one new token:

Add

UTILITY_LIQUIDITY_BACKSTOP_ACTUATED (FINANCE / ACT / base_weight ~12 / brake=true)
Reason: utility rescue is finance-lane actuation distinct from classic bank facilities.

Keep proxy-only forever

MARKET_RISK_SENSOR_OIL_SPIKE remains proxy (fast-only)

8) Failure Mode Trace

			
Energy prices spike → treated as finance confirmation → false alarm
→ later collateral/liquidity crisis hits utilities → actual backstop arrives → model credibility already damaged.

9) Operator Fill Checklist

[ ] Paste T1 evidence refs for SUPPLY truth events (allocation/disruption)
[ ] Paste T1 evidence refs for FINANCE actuation (backstop/guarantees)
[ ] Tokenize only key days (don’t spam)
[ ] Produce routing audit JSON on each routed day
[ ] Compute lead/lag + false spikes + misses

Composite Monitor Publish Pack (WordPress-ready) (v1.0)

Dashboard Page + Backtest Index + Governance Block (CivOS × VocabularyOS)

1) Master Dashboard Page Template (copy/paste)

Permalink: /phase-monitor/war-iran-us-system-state/
Title: Iran–US System State (War × Supply × Finance) — Weekly Dashboard (v1.0)

0) Hero Summary (5 lines)

This page tracks the coupled system state of the Iran–US theatre across:
War posture, Hormuz supply corridor, and Finance (energy→liquidity).
It uses PS_fast vs PS_confirmed so rumor proxies don’t hijack decisions.
Composite_confirmed only rises when multiple lanes actuate (ORDER/ACT/KIN + T1/T2).
Updated weekly.

1) Week Header (fixed)

Week Ending: YYYY-MM-DD (SGT)
Engine: Phase Monitor v1.0
Composite Type: multiplicative coupling (WAR × SUPPLY × FIN)
Convergence Rule: proxies capped, routing gated

2) Core Score Table (fixed)

Domain	PS_fast	PS_confirmed	Confidence	Volatility	Gap
War	__	__	__	__	__
Supply	__	__	__	__	__
Finance	__	__	__	__	__

3) Composite (fixed)

Composite_fast: _ / 100 Composite_confirmed: _ / 100

Trigger Status: NONE / MOD / STRONG / IRREVERSIBLE

Interpretation (fixed)

Composite_confirmed < 15 → multi-lane actuation not present
15–30 → coupled risk rising (watch TTC + triggers)
30–60 → active coupled stress (prepare defensive actions)
> 60 → irreversible coupling likely (actuation dominates)

4) TTC Windows (fixed)

TTC_event: _ TTC_policy: _
TTC_market: __
Reaction Window Active? YES / NO

5) What moved this week (fixed)

Top Drivers (max 5)

TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref

Top Brakes (max 5)

TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref
TOKEN_ID — evidence_ref

6) Trigger Watchlist (fixed)

+10 (moderate)

+25 (strong)

80–100 (irreversibility regime)

7) Far-node proxies (fixed policy block)

Proxies (oil spikes, viral chatter, “pizza theory” etc.) may increase PS_fast only.
They cannot increase PS_confirmed unless convergence rules are met.

8) Failure Mode Trace (required)

			
Proxy-driven monitoring → false alarms → trust decay → real multi-lane actuation missed → irreversible coupling arrives late.

9) “Run with any LLM” (paste)

Tokenize sources with Master Token Registry.
Tier + class; dedup.
Compute PS_fast/PS_confirmed per lane with gating.
Route only via Bridge Binds.
Output Composite + TriggerStatus + Watchlist.

2) Coupled Backtests Index Page (copy/paste)

Permalink: /phase-monitor/coupled-backtests/
Title: Coupled Backtests Index (WAR × SUPPLY × FIN) (v1.0)

Why these exist

Coupling weights and bridge binds are not opinions.
They are evidence-locked through backtests.

Index

BT-004: Gulf Tanker Seizure Cycle 2019 (WAR→SUPPLY→FIN fast; confirmed stays disciplined)
BT-005: Europe Energy Shock → Utility Liquidity / Bailouts 2022 (SUPPLY→FIN confirmed)
BT-006 (planned): Finance plumbing fracture case (Repo stress / facility activation)
BT-007 (planned): Prolonged chokepoint disruption case (days→weeks closure)

Governance rule (non-negotiable)

No weight changes are promoted without validation across ≥3 backtests.

3) Governance Block (the “no drift” lock) (copy/paste)

Permalink: /phase-monitor/governance/
Title: Phase Monitor Governance (No Drift) (v1.0)

The rule

Weights do not change because of one crisis.
They change only after repeated validation.

Allowed changes

Add a new token id (version forward)
Change a token base_weight
Change a bind weight in the Coupling Matrix

Promotion requirement

A change is PROMOTED only if:

it improves accuracy on ≥3 backtests, and
it reduces confirmed false spikes, and
it does not increase missed irreversibility events.

Failure Mode Trace

			
No governance → weights chase headlines → model breaks → outputs lose credibility → operators stop using it.

Start Here:

eduKateSG Learning Systems: