Live state of the BOTWAVEBOMBA pipeline. Page auto-refreshes every 60 seconds.
Reads from api/latest.json, pipeline_state.json, and
data/source_registry.json at runtime. No cached numbers.
Cannot-verify is a first-class output — failures fail loud.
api/latest.jsonThree populations, one canonical phrasing. Read at runtime; no hardcoded numbers.
| Population | Count | Source file |
|---|---|---|
| Ingested every six hours | — | book_arm/memory/sources_global.json |
| Carries full five-axis bias fingerprint | — | data/source_registry.json#total |
| Awaiting fingerprinting (volume-only) | — | derived: ingested − fingerprinted |
Bloc distribution of the fingerprinted set — Western: — · Neutral: — · Adversarial: —
Path B build: extract one analytical stage from generate_feed.py
per calendar week. Six modules, then a seventh week for the orchestrator.
Plan: PLAN_HYBRID.md.
— / — modules extracted.
Next extraction target: —
(scheduled —).
Systemd timer: botwave-bomba-pipeline.timer ·
Shell: zombie760.github.io/scripts/bomba_pipeline.sh ·
Schedule: every 6 hours at 00, 06, 12, 18 UTC (with up to 5 min jitter).
After Week 7 of the decomposition, this page will read per-stage health
from api/pipeline_run.json (schema already drafted at
schemas/pipeline_run.schema.json).
Until then, status is inferred from the freshness of api/latest.json
and from the manually-maintained pipeline_state.json.