Liveness of the whitepaper itself
🩺 Site health — is this whitepaper keeping up?
This page judges nothing about the observed world. It answers one question about the site: is every series being refreshed on schedule? For each published series it shows the last confirmed observation, the update frequency, the next expected update, whether it is stale, and whether the last fetch succeeded. A stale series means we fell behind — not that the world changed.
Generated: 2026-09-24 20:06 JST
Health by edition
Site status
degraded
Series tracked
84
Published to production
0 d ago
🇺🇸 United States — Last batch: success (2026-09-24 18:04:43, run_us_20260924.log)
| Chapter / series | Last confirmed | Frequency | Next expected | Stale? | Last fetch |
|---|---|---|---|---|---|
| power | 2026-09-23 | daily | 2026-09-24 | on time | success |
| power | not yet measured | daily | — | — | success |
| regulation | 2026-09-24 | daily | 2026-09-25 | on time | success |
| regulation | 2026-09-24 | daily | 2026-09-25 | on time | success |
| regulation | 2026-09-24 | daily | 2026-09-25 | on time | success |
| water | 2026-09-04 | irregular | — | — | success |
| water | 2026-09-03 | monthly | 2026-10 | on time | success |
| water | 2026-09-15 | weekly | 2026-09-22 | on time | success |
| water | 2026-09-15 | weekly | 2026-09-22 | on time | success |
| gpu | 2026-Q2 | quarterly | 2026-Q3 | on time | success |
| gpu | 2026-09 | monthly | 2026-10 | on time | success |
| gpu | 2026-09-24 | weekly | 2026-10-01 | on time | success |
| gpu | 2026-09-24 18:01 | irregular | — | — | |
| gpu | 2026-09-24 | irregular | — | — | success |
| gpu | 2026-09-04 | irregular | — | — | success |
| datacenter | 2026-09-22 | daily | 2026-09-23 | on time | success |
| datacenter | 2026-07 | monthly | 2026-08 | on time | success |
| datacenter | 2026-07 | monthly | 2026-08 | on time | success |
| fiscal | 2026-09 | monthly | 2026-10 | on time | success |
| fiscal | 2026-09-22 | business_daily | 2026-09-23 | on time | success |
| fiscal | 2026-09-23 | business_daily | 2026-09-24 | on time | success |
| disaster | 2026-09-23 | daily | 2026-09-24 | on time | success |
| disaster | 2026-09-23 | daily | 2026-09-24 | on time | success |
| disaster | 2026-09-23 | daily | 2026-09-24 | on time | success |
| market | 2026-09-24 | daily | 2026-09-25 | on time | success |
| market | not yet measured | irregular | — | — | |
| market | 2026-09-04 | irregular | — | observing (source under review) | failed |
| market | 2026-09-04 | irregular | — | — | |
| market | 2026-09-04 | irregular | — | — | |
| market | not yet measured | irregular | — | — | |
| ai_readers | 2026-09-23 | daily | 2026-09-24 | on time | success |
🇪🇺 European Union — Last batch: success (2026-09-23 20:06:27, run_eu_20260923.log)
| Chapter / series | Last confirmed | Frequency | Next expected | Stale? | Last fetch |
|---|---|---|---|---|---|
| power | 2026-09-24 | daily | 2026-09-25 | on time | failed |
| regulation | 2026-09-24 | daily | 2026-09-25 | on time | success |
| regulation | 2026-09 | monthly | 2026-10 | on time | success |
| regulation | 2026-09-03 | irregular | — | — | success |
| datacenter | 2026-07 | monthly_lagged | 2026-08 | on time | success |
| datacenter | 2026-09-04 | irregular | — | — | success |
| datacenter | 2025-12 | irregular | — | — | success |
| fiscal | 2026-Q1 | quarterly | 2026-Q2 | on time | success |
| fiscal | 2026-09-23 | business_daily | 2026-09-24 | on time | success |
| fiscal | 2026-Q1 | quarterly | 2026-Q2 | on time | success |
| disaster | 2026-09-04 | irregular | — | — | success |
| disaster | 2026-09-23 | daily | 2026-09-24 | on time | success |
| market | 2026-09-24 | daily | 2026-09-25 | on time | success |
| market | 2026-09-04 | irregular | — | observing (source under review) | failed |
| market | not yet measured | irregular | — | — | |
| market | 2026-09-04 | irregular | — | — | |
| market | not yet measured | irregular | — | — | |
| market | 2026-09-04 | irregular | — | — | |
| ai_readers | 2026-09-23 | daily | 2026-09-24 | on time | success |
🇯🇵 Japan — Last batch: success (2026-09-24 10:34:21, run_20260924.log)
| Chapter / series | Last confirmed | Frequency | Next expected | Stale? | Last fetch |
|---|---|---|---|---|---|
| power | 2026-09-23 | daily | 2026-09-24 | on time | success |
| power | 2026-09-25 | daily | 2026-09-26 | on time | success |
| power | 2026-09 | monthly | 2026-10 | on time | success |
| gpu | 2026-09-18 | weekly | 2026-09-25 | on time | success |
| gpu | 2026-09-18 | weekly | 2026-09-25 | on time | success |
| water | 2026-08-21 | monthly | 2026-09 | on time | success |
| water | 2026-08-21 | monthly | 2026-09 | on time | success |
| data | 2026-09-01 | monthly | 2026-10 | on time | success |
| data | 2026-09-01 | monthly | 2026-10 | on time | success |
| data | 2026-09-01 | monthly | 2026-10 | on time | success |
| data | 2026-09-01 | monthly | 2026-10 | on time | success |
| data | 2026-09-01 | monthly | 2026-10 | on time | success |
| data | 2026-09-01 | monthly | 2026-10 | on time | success |
| data | 2026-09-01 | monthly | 2026-10 | on time | success |
| data | 2026-09-01 | monthly | 2026-10 | on time | success |
| data | 2026-09-01 | monthly | 2026-10 | on time | success |
| data | 2026-09-01 | monthly | 2026-10 | on time | success |
| regulation | 2026-09-24 | daily | 2026-09-25 | on time | success |
| regulation | 2026-09 | monthly | 2026-10 | on time | success |
| datacenter | 2026-06 | irregular | — | observing (source under review) | failed |
| datacenter | 2025-12 | annual | 2026 | — | success |
| datacenter | 2026-09-23 | daily | 2026-09-24 | on time | success |
| fiscal | 2026-09-18 | business_daily | 2026-09-21 | stale | success |
| disaster | 2026-09-23 | daily | 2026-09-24 | on time | success |
| disaster | 2026-09-23 | daily | 2026-09-24 | on time | success |
| disaster | 2026-09-23 | daily | 2026-09-24 | on time | success |
| disaster | 2026-09-23 | daily | 2026-09-24 | on time | success |
| market | not yet measured | irregular | — | — | success |
| market | 2026-09-04 | irregular | — | — | success |
| market | 2026-09-04 | irregular | — | — | success |
| market | not yet measured | irregular | — | — | success |
| market | 2026-09-04 | irregular | — | observing (source under review) | failed |
| market | 2026-09-24 | daily | 2026-09-25 | on time | success |
| ai_readers | 2026-09-23 | daily | 2026-09-24 | on time | success |
Machine-readable: /api/health.json · one-file world summary: /api/world.json. Japanese page: /jp/health/.
How "stale" is decided (definition v1.0)
- Threshold = 2 × the update frequency: daily series are stale after 2 days, business-day series after 4 days (covers a weekend), weekly after 14 days, monthly after 62 days. Annual and irregular series are not judged (age is shown only).
- Age is counted from the last confirmed observation date to the edition's local "today". Provisional same-day values do not count as confirmed.
- Last fetch comes from each edition's fetch ledger (pipeline_health.json); the legacy Japan pipeline has no per-source ledger, so its series carry the batch-level result.
- Site status is "ok" when no series is stale and no last fetch failed, otherwise "degraded". This file is regenerated after each edition's daily batch; if the generator itself fails, the previous file stays in place (fail-safe).
- Definition: docs/指標定義_サイト生存状態_health.md (v1.0, 2026-09-03).