Methodology & Settings

How the system works, what data is fresh, and what is configurable

Freshness: waiting for data · Model: --

1. Executive Summary — What Regime Signal Is and What It Does

Regime Signal is a revision-aware weekly intelligence framework that helps investors detect where automation intensity is rising across labor clusters, then translate that neutral signal through capture profile into likely tailwinds, headwinds, or mixed outcomes. It is a directional decision-support system, not a causal engine or a standalone trading model.

2. Problem Statement — Why This Framework Exists

Traditional labor data is broad, lagged, and often noisy. Regime Signal exists to give institutional users a faster, more structured way to interpret whether automation intensity is broadening, narrowing, or shifting across roles and sectors before consensus margins, staffing assumptions, and sell-side narratives fully adjust.

Typical uses

Weekly strategy review, automation-intensity research, sector diligence, and structured memo generation.

Decision context

Answering what is changing, where it is changing first, which capture profiles benefit or suffer, and what would invalidate the current read.

3. Intended Use and Scope Boundaries — What This Is and Is Not
In scope
  • Directional regime monitoring
  • Cross-sectional automation-intensity mapping
  • Capture-aware weekly decision briefs for investors and analysts
Out of scope
  • Causal attribution of AI adoption
  • Point-forecast precision
  • Standalone portfolio automation
4. Data Architecture — Sources, Governance, and Coverage
SourceRoleCadence
FRED Indeed IndexEarly labor-demand timingHigh frequency
Anthropic Economic IndexOccupation exposure mappingSnapshot
BLS OOHOccupation structure and employment referenceQuarterly/annual
PAYEMSEmployment benchmark for divergenceMonthly
UNRATE / U-6Labor confirmation layerMonthly
SEC EDGARCorporate disclosure corroborationEvent-driven
Curated company attributesBusiness-model, capture-profile, and labor-intensity overrides for selected namesManual refresh
Curated cluster relevance weightsWorkforce-relevance weighting for selected ticker-cluster pairsManual refresh
Curated efficiency metricsRevenue-per-employee confirmation layer for selected namesManual refresh
Weekly vintagesImmutable snapshot bundles for point-in-time review and backtest assemblyWeekly

Current portfolio mapping universe includes 520 public tickers, 756 exposure occupations, and 342 BLS occupation profiles. Portfolio v5 layers curated company attributes, workforce relevance weights, capture profiles, software-enabler displacement risk, and efficiency confirmation for selected names. SEC disclosure scoring remains on its separate 517-name backend universe until that layer is expanded. Immutable weekly vintages are now written for point-in-time review and future backtests. Unemployment confirmation, SEC filings, and occupation structure support interpretation, but do not all enter the top-line composite directly.

5. Core Regime Signal Construction — How the Composite Score Is Built
  1. Smooth high-frequency labor demand signals.
  2. Standardize them relative to trailing baseline context.
  3. Aggregate them into a composite regime score.
  4. Translate the score into Stable / Watch / Warning / Alarm states.
s_t = smooth(x_t)
z_t = (s_t - mean_t) / stdev_t
C_t = Σ w_i z_i / Σ w_i
StateThresholdMeaning
Stable< 1.0No elevated automation intensity beyond normal variation
Watch≥ 1.0Early intensification worth monitoring
Warning≥ 1.5Broader and more durable intensification
Alarm≥ 2.0Sustained, confirmed intensification
6. Confidence Scoring and Uncertainty Bands — How Reliable Is the Current Read

Confidence is reported on a 0–100 scale and reflects data freshness, coverage quality, and cross-signal agreement. Uncertainty bands show likely ranges around the current read rather than pretending the system is more precise than it is.

7. Automation Intensity Matrix — How Function × Industry Intensity Is Computed

Each cell score blends overall conditions, weekly change, AI exposure, spread/breadth, role sensitivity, and industry sensitivity. Intensity tiers break at 45 / 60 / 75 and each cell carries a coverage label so users can distinguish stronger support from thinner support.

8. Lead-Lag Estimation — Directional Probabilities by Horizon

Lead-lag probabilities are evaluated across 30 / 60 / 90 / 180 day horizons using multiple signals, including top-line labor-demand intensification, divergence, exposure persistence, and corroborating evidence quality.

9. Hiring vs Employment Divergence — When Postings and Payrolls Disagree

Divergence compares hiring demand against employment levels. When postings weaken while payrolls stay firmer, the model can flag a latent margin signal before broader labor confirmation catches up. Labor confirmation then checks whether unemployment and underemployment momentum are beginning to agree with the weaker hiring picture.

UNRATE_3m = UNRATE_t - UNRATE_t-3
UNRATE_6m = UNRATE_t - UNRATE_t-6
U6_3m = U6_t - U6_t-3
U6_6m = U6_t - U6_t-6
10. Corporate Disclosure Intensity — SEC EDGAR Filing Signals

SEC disclosure intensity ingests 8-K, 10-Q, and 10-K filings and scores AI/labor language using frequency, recency, and context weighting. It is a corroboration layer that adds company-level evidence to the broader macro and cluster reads.

11. Occupation Structure Map — How the Treemap Is Built
Tile area

BLS employment size

Default color

Observed AI exposure

Alt modes

BLS outlook and median pay

Exposure matching uses exact SOC matches first, then broader SOC prefix matches, then title-based fallback when needed.

12. Portfolio Exposure Mapping — How Tickers Map to Clusters

Tickers map to clusters through a direct mapping hierarchy first, then industry fallback, then an explicit unmapped state. Portfolio v3 adds a company-attributes layer so business model and labor intensity can modify the blended signal instead of treating every same-cluster company as identical. Portfolio v4 adds curated workforce relevance weights, which rebalance the contributor mix and blended score when company-specific labor relevance appears stronger or weaker than the broad proxy mapping alone. Portfolio v5 adds capture profiles, separate mapping and capture confidence, software-enabler displacement risk, and efficiency confirmation for selected names. Capture profiles currently resolve names into labor buyers, labor sellers, software enablers, hardware enablers, or mixed / unclear cases.

13. Output Layer — What the Weekly Read Contains

The weekly read surfaces regime state, weekly deltas, capture-aware translations, early signals, action guidance, portfolio mapping, data quality context, and research-note export support. It is designed to support analyst workflow, not replace analyst judgment.

Coverage

--

Waiting for coverage data

Freshness

--

Waiting for freshness data

Evidence Strength

--

Waiting for evidence strength data

Quality Trend

Coverage, freshness, and evidence strength

8-point recent status history.

Runtime Snapshot

snap- --

waiting

Last update

--

Model version

--

Week ending

--

SEC disclosure freshness

--

Sources & Freshness

Freshness pending

Loading live source coverage and timestamps...

Waiting
Source What it does Cadence Latest loaded
Loading live source freshness...

Active Data-Quality Controls

ControlStatus
TimestampsActive
Versioned outputsActive
Snapshot metadataActive
Coverage labelsActive
Uncertainty intervalsActive

Active Module Versions

ModuleVersionEndpoint
Loading modules...----
Runtime Lineage and Governance

Implemented controls include source timestamps, versioned outputs, snapshot metadata, visible coverage labels, and immutable weekly vintages. Pending governance items include published source-diff reporting, formal benchmark protocols, and external-validity work.

Advanced Diagnostics
Core series observations

--

Last refresh

--

Active sources

--

Clusters detected

--

Suppressed signals

--

Regime confidence

--

Backtest Sharpe

Not published

False positive rate

Validation pending

Calibration

Parameter registry

Visual controls show current calibration values without changing the underlying data pipeline.

Composite Weighting

Weights auto-normalize based on configured domains.

Signal State

Composite regime signal (normalized)

1.24Watch

Persistence rules

Watch

Condition true in 2 of last 3 periods.

Warning

Condition true in 3 of last 4 + 2 domains confirm.

Alarm

Condition true in 6 of last 8 + 3 domains confirm.

Thresholds

Set cutoffs for watch, warning, and alarm regimes.

ParameterCurrent ValueDescriptionUsed In
Regime Smoothing Window28 daysSmoothing window for the labor-demand signal.ewi_from_fred.py
Regime Baseline Window365 daysTrailing baseline for z-score normalization.ewi_from_fred.py
Z-Score Alert Thresholds1.0 / 1.5 / 2.0Watch, Warning, Alarm thresholds.regime.v2
Automation Intensity Tier Breaks45 / 60 / 75Intensity tier cutoffs.risk_matrix.v2
Lead-Lag Horizons30 / 60 / 90 / 180Directional horizon set.lead_lag.v1
Divergence Latent-Margin Rulegap < -1.0 and 4w Δ < 0Latent margin signal trigger.divergence.v1
Labor Confirmation Thresholds3m +0.10 / 6m +0.20Momentum thresholds for unemployment confirmation.labor_confirmation.v1
False-Alarm Dampener26 weeksDowngrades unconfirmed weak-postings signals.labor_confirmation.v1
SEC Disclosure Lookback120 daysMaximum filing lookback window.sec_corporate_disclosure.py
SEC Max Filings per Ticker2Latest filings sampled per ticker.sec_corporate_disclosure.py
SEC Direction Thresholds+2.0 / -2.0Rising vs falling disclosure cutoffs.disclosure.py

Implemented and Test-Covered

  • regime
  • weekly insights
  • automation intensity matrix
  • lead-lag
  • divergence
  • watchlist alerts
  • implications
  • portfolio support / capture layer
  • SEC disclosure
  • weekly vintages
  • API smoke testing
  • versioned outputs

Remaining for Formal Sign-Off

  1. Pre-registered historical benchmark protocol
  2. Calibration and error-rate reporting by horizon
  3. Revision-impact studies with vintaged snapshots
  4. Ablation and sensitivity studies
  5. External-validity testing across regimes

The system is production-grade for directional weekly decision support, but users should treat it as a structured analytical input, not a validated predictive engine.