Warconomy
Operator

Morning report

A read-only daily operator snapshot: production health, route/crawler health, source-watch status, staleness, the best next data pull, the best next autonomous task, and any blockers. It promotes nothing and asserts no new value.

One glance at the whole operation. Production is healthy and auto-rollout is confirmed; 8/8 indexing checks pass; 5 of 8 source-gated values have a checkable official page, 2 are blocked by source access. 5 values are overdue and 15 are stale for re-check. This report promotes nothing — it tells you what to look at, what Claude can do now, and the single best next task.

  • Best next data pull: CREA May 2026 Russian fossil-fuel export revenue.
  • Best next autonomous task: —.
  • Blockers: none.
  • Run npm run operator:morning for this report from the CLI.

At a glance

KnownProduction healthy

Auto-rollout confirmed; bot 404s expected.

Known8/8 indexing checks

Sitemap/robots/canonical/linking.

Stale5 overdue · 15 stale

Values due for re-check.

Known0 blockers

Nothing blocking.

Best next data pull (≈5 minutes)

CREA May 2026 Russian fossil-fuel export revenue — Lowest-effort / highest-value source-gated value; check availability, then fill a source packet.

  • Cadence: Monthly (~6 weeks in arrears) · Last known: April 2026 (published 2026-06-01)
  • Official source: open ↗ · source packet
  • Claude can check availability: yes · Needs your exact value: yes

Best next autonomous task (no value needed)

Nothing queued.

What Claude can do now / what needs you

Claude can do now

  • Run npm run operator:check (offline integrity).
  • Run npm run operator:check:sources (detect-only reachability).
  • Validate a pasted source packet and produce a promotion dry-run.
  • Keep audits, backlog, source-watch, and staleness current.
  • Draft a new evergreen briefing from sources already in the registry (no new numeric values).

Still needs you

  • Supply an exact source value via a validated source packet.
  • One-time Google Search Console / Bing setup (DNS TXT, submit sitemap).

Briefings

Source-reviewed economic explainers — not live news, not real-time, not investment advice. New evergreen briefings can be drafted autonomously from sources already in the registry.

  • Published: 27 · Latest reviewed: 2026-06-23 · /briefings
  • Needs a manual source packet for live tracking: Ukrainian strikes on Russian refineries: fuel supply, exports and prices; Conflict in Africa and critical-mineral supply; Sudan's war: Red Sea security, food insecurity and regional trade; Eastern DRC conflict: cobalt, copper and electronics supply chains; The Sahel: conflict, coups, uranium and gold; Taiwan and semiconductors: a global manufacturing risk; Military losses and the long shadow on labour and growth; Sudan's war: displacement, food and the road to recovery; Gaza: human capital, displacement and reconstruction
  • Next briefing ideas: Critical minerals data layer: ingest USGS Mineral Commodity Summaries (annual, build-and-forget) to back the DRC/Sahel/minerals briefings with figures. · Panama Canal: how drought-driven draft limits can affect shipping (links existing chokepoint page). · Semiconductor trade series: a reviewed SIA/WTO snapshot to back the Taiwan briefing. · Refresh /conflict-economies on demand (npm run worldbank:macro) when new World Bank years land.
  • Human-capital layer: published — dignity-first explainer + World Bank demographic context · /human-capital (refresh: npm run worldbank:humancapital).
  • ⚠ Casualty-number policy: Do NOT publish Warconomy casualty, wounded or displacement figures. Those are uncertain, contested estimates — cite UNHCR/IOM/UCDP/UN as ranges with caveats, never as Warconomy numbers or certainties.
  • Population structure: published — age bands, working-age share & dependency ratios for 14 conflict economies (refresh: npm run population:ingest; projections included: false).
  • Critical minerals: source-backed (citation-only) — /minerals. USGS Mineral Commodity Summaries pages block automated access (403) and ship PDF/ZIP-CSV; used citation-only. No mineral figures are published without a reviewed source packet.
  • Dataset-version decision: Keep new public layers editorial (no version bump); fold only a curated batch of stable structured records into the versioned export in a dedicated version-cut train. (decision report, current 1.191.0).
  • Optional-key APIs: EIA/FRED are optional-key future integrations: never commit a key; the default build needs no key and makes no network call. See /methodology/data-sources.

Manual work by kind

  • PDF/XLSX extraction: Longer SIPRI / NATO defense-spending series; World Bank Pink Sheet — wheat / fertilizer / gas
  • Blocked by source access: Suez / Red Sea official transit metric; Black Sea grain export volumes
  • Automatable later: sipri-nato-series, suez-transit, pink-sheet, grain-volumes

Checklists

  • After every deploy: npm run verify:prod
  • Before every promotion: npm run operator:check → validate the source packet → promotionPlan() dry-run → npm run validate:release

Related

Operator workbench · Source watch · Staleness · Production health · Backlog · /operator/report/data.json