🪲 BugOut Index

Methodology — v1.1.1

The BugOut Index is a directional stress and stability reading. Six published metrics are placed between fixed endpoints and combined into one weighted 0–100 score. Higher means those inputs sit closer to the stable end of the ranges. The number shows how hard current published conditions are pressing. It is not a forecast, and it is not an instruction to bug out. This page describes how the current week's number was produced. Methodology version is v1.1.1.

1. Inputs and weights

Raw weights are relative coefficients that sum to 0.72. The “share of score” column is weight / 0.72 — the fraction of the finished index each metric actually carries after the publisher divides by the sum of weights. Tile labels that say “Raw weight 15%” are the raw weight × 100, not the post-division share.

MetricRaw valueUnitNormalization rangeNormalizedRaw weightShare of scoreSource
Inflation Rate 3.72 % −10 to 15 45.13 15.0% 20.8% FRED (CPIAUCSL)
Violent + Property Crime 2,443.27 per 100k 500 to 8,000 74.09 12.0% 16.7% Real-Time Crime Index
Unemployment Rate 4.10 % 0 to 25 83.6 12.0% 16.7% FRED (UNRATE)
Debt-to-GDP Ratio 121.19 % 0 to 200 39.41 12.0% 16.7% FRED (GFDEGDQ188S)
Homelessness Rate 0.22 % of pop. 0 to 0.5 56.0 9.0% 12.5% HUD AHAR
Trust in Government 39.00 % confidence 0 to 80 (inverted) 48.75 12.0% 16.7% Edelman Trust Barometer

Crime input, methodology 1.1.0

Publications through 2026-10-02 are methodology 1.0.0. Crime in those weeks is the locked input 2,723.0, an old unweighted print of the Real-Time Crime Index file. Those history rows are not rewritten.

Methodology 1.1.0 scores crime from RTCI’s cleaned file (AH-Datalytics/rtci, docs/app_data/final_sample.csv on main). The rate is violent plus property incidents per 100,000 people for the latest calendar month in that file. The weekly job uses RTCI’s Nationwide Full Sample row when that row appears once, its counts are usable, and its rate matches the population-weighted total of the other usable rows (within 0.02). That is the national figure RTCI publishes. On the current file the two figures match, including the agency crime and population totals. If the row is missing, duplicated, or outside that tolerance, the job scores the population-weighted total instead and records which one it used.

The crime observation date is the last day of that month, taken from the file (for example 2026-04-30). It is not the download time, and it is not filled in for weeks that were published under 1.0.0. The normalization range stays 500 to 8,000, inverted, and the raw weight stays 0.12. If the RTCI download fails or that rate cannot be computed, the weekly job refuses to publish, the same way it refuses when another core input fails. It does not carry the previous crime value forward.

This week is methodology 1.1.0. Crime in the table is the RTCI population-weighted national rate for the latest month in the file. Weeks through 2026-10-02 remain methodology 1.0.0, with crime locked at 2,723.0.

2. Normalization

Each metric is normalized to 0–100 using predefined thresholds:

normalized = (1 − (raw − min) / (max − min)) × 100

Trust in Government is inverted (higher trust → higher stability) by applying 100 − normalized after the above transform — equivalently a linear map of the trust percent on 0–80. An Edelman reading of 41 normalizes to 51.25. Inflation at 4% on −10…15 normalizes to 44.

3. Aggregation

The index is the weight-normalized sum of the per-metric scores (divide by the sum of weights; with all six present that denominator is 0.72). A perfect week on every metric therefore scores 100:

BOI = Σ (normalized_i × weight_i) / Σ weight_i

4. Risk bands

These four bands and cutoffs are methodology v1.1.1. They locate where today’s score sits. They do not forecast a crisis, and they are not a siren.

RangeBandInterpretation
70 – 100High StabilityLow risk — focus on long-term planning.
55 – 69.99Moderate StabilityWarning signs — monitor trends; prepare contingencies.
40 – 54.99Low StabilityHeightened risk — take this reading seriously. Conditions are pressing harder than in Moderate.
Below 40Critical InstabilityCollapse Likely — severe pressure on the published inputs. Not an instruction to bug out.

5. Limitations and caveats

6. Reproducibility

Every weekly run commits the raw inputs, the computed normalized scores, and the final index. Those committed files are the record of that week. The code that produced this page is open source. Rerunning runtime/publish/weekly_run.py fetches the latest observations, so it does not rebuild a past week’s score. Methodology version is v1.1.1.