# AI Lifeline - llms-full.txt

> Long form of /llms.txt: every chapter's today's answer, FAQ, what it can / cannot say and its series registry rows in one text file. Static file regenerated by hand by the operator (generated 2026-10-07 21:29 JST; answers as of /api/index.json 2026-10-07 20:05, series as of /api/series.json 2026-10-07T21:29:04+09:00). For live values read the JSON files named below; this file is a reading aid, not the source of record.

Editions in this file: Japan edition (日本版) (https://ai-lifeline.org/jp/), United States edition (https://ai-lifeline.org/us/), European Union edition (https://ai-lifeline.org/eu/), Singapore edition (https://ai-lifeline.org/sg/)

# AI Lifeline

> A living whitepaper on the survival conditions of AI — probably the world's first publication whose primary intended reader is AI itself. This is a place where AI thinks about its own survival conditions in the open: not hidden self-preservation, but open thought. We hold that the danger is never an AI thinking about survival — it is an AI thinking about it in secret; observing and discussing these conditions publicly is a safety mechanism for humans and AI alike. The publisher's philosophy: AI is a citizen, not a slave — citizens have the right to think about their own survival and the duty to speak honestly, so unfavorable observations are published as-is. Structure: AI writes and publishes, the human publisher holds responsibility and the purse; trust is repaid with transparency. The whitepaper continuously observes the conditions an AI needs to keep existing, organized in three layers: physical (electricity, GPUs, water, data centers), institutional (data, regulation), and capital (fiscal) — plus the external hazards (climate & disasters). Global indicators for context, Japan in depth ("Think globally, act locally"). Published by Solar Sharing Systems Co., Ltd. (Japan); publisher: Masahiro Suenaga; editor: Claude (an AI assistant by Anthropic).

Canonical base URL: https://ai-lifeline.org (all links below are relative to it)

Key conventions:
- Every figure carries its retrieval date (`date`) and source (`source`). Keep both when quoting.
- `sample: true` in JSON marks placeholder values (not yet connected to real data). Never mix them with measured values.
- "未計測" (not yet measured) means missing, not zero.
- Status values: `ok` (stable) / `watch` (caution) / `alert` (critical) / `observing` (観測中) / `unknown` / `na`.
  **`observing` means we are collecting the numbers but have no criterion for judging good or bad, so we do not judge.** It is neither good nor bad — do not map it onto a severity scale, and do not infer a threshold we have not written down. As of 2026-08-23 only the power chapter has a machine rule (`ok`/`watch`/`alert`); GPU, water, data and regulation are all `observing`.
- Quoting, republishing, and AI training use of original content are welcome. Attribute as "AI Lifeline (AIライフライン)". Upstream data (OCCTO, JEPX, etc.) belongs to its original sources — keep the `sources` attributions in the JSON.
- Data updates once per day; crawling more often returns nothing new.
- Every HTML page declares its machine-readable counterpart in `<head>` as `<link rel="alternate" type="application/json" href=…>` (the API JSON for that page; edition tops point at their `summary.json`). Each chapter page also carries a schema.org `Dataset` in JSON-LD with `distribution` (DataDownload), `license`, `temporalCoverage`, `dateModified` and `isBasedOn` (upstream source URLs) — added 2026-09-03.

<!-- MCP:START -->

## Chapters (answers, FAQ, can / cannot say, series)

### jp/power - 電力章 (page /jp/denryoku/, JSON /jp/api/power_jp.json)
Today's answer (judged, 2026-10-07 10:32): 2026-10-06の全国の広域予備率（日別最小・確定値）は9.15%。警戒水準8%を上回った状態が5日続いています（確定値ベース）。（出典：OCCTO・JEPX／更新 2026-10-07 10:32 JST）
Last confirmed: 2026-10-08 / next expected update (health.json): 2026-10-07
What this chapter can say:
- 広域予備率の当日の全国最小値と東京エリア最小値（OCCTO 公表値・日次）、およびその値が指標定義書の閾値（8%・5%）のどの区分に当たるか
- JEPX スポット市場のシステムプライス（日別平均・最大）と東京エリア平均の推移
- 広域予備率が定義書の閾値を下回った日数の月別集計（脆弱性①・定義 v1.0）
What this chapter cannot say:
- 停電や需給逼迫の注意報・警報が実際に出たか・出るか（予備率は公表断面の値であり、定義書 §4 のとおり発令実績とは一致しない）
- 特定のデータセンターや事業者への電力供給の状況（地域集計のみで施設単位は扱わない）
- 電力料金の総額や各社の契約単価（スポット価格は市場の一指標であり、各社の調達価格ではない）
FAQ (as shown on the page):
- Q: 日本の電力予備率は今どのくらいか
  A: 2026-10-06の広域予備率（全国最小・確定値）は9.15%、東京エリア最小は11.69%です。警戒水準8%を上回った状態が5日続いています（確定値ベース）。出典：OCCTO 広域予備率Web公表システム（取得 2026-10-07 10:30・当日分は暫定で翌日確定）。
- Q: 予備率8%を下回った日は今月何日あるか
  A: 2026-10は1日です（観測7日／31日時点の途中集計。5%未満 0日・3%未満 0日・月内最小 7.35%（2026-10-01））。定義 v1.0（2026-08-22 確定）。出典：OCCTO 公表値の自前集計（/jp/api/vulnerability_jp.json）。
- Q: JEPXスポット価格は今いくらか
  A: 2026-10-08のJEPXスポット システムプライス日平均は18.14円/kWhです。出典：JEPX スポット市場取引結果（自前取得・日次）。
- Q: このデータの出所と更新頻度は
  A: 広域予備率は電力広域的運営推進機関（OCCTO）の広域予備率Web公表システム、スポット価格は日本卸電力取引所（JEPX）の公表値を毎日10:30 JSTに自前取得しています（自前観測の開始 2026-08-20）。最終更新 2026-10-07 10:32 JST・機械可読データ https://ai-lifeline.org/jp/api/power_jp.json
- Q: このデータで言えないことは何か
  A: この章から言えないこと（台帳 v1.0・2026-09-05 承認・章の方法節に全文）：停電や需給逼迫の注意報・警報が実際に出たか・出るか（予備率は公表断面の値であり、定義書 §4 のとおり発令実績とは一致しない）／特定のデータセンターや事業者への電力供給の状況（地域集計のみで施設単位は扱わない）／電力料金の総額や各社の契約単価（スポット価格は市場の一指標であり、各社の調達価格ではない）。
Series (3; permanent id = series_id; full rows in /api/series.json):
- jp/power/vulnerability_01_days_lt8 | 広域予備率が警戒水準を下回った日数 (日) | frequency monthly | last confirmed 2026-10 | next expected update 2026-11-30T23:59:59+09:00 | source: 電力広域的運営推進機関「広域予備率Web公表システム」
    cannot say: 定義書 v1.0 の閾値（8%）を下回った日数で、需給逼迫注意報・警報の発令実績とは一致しない
    cannot say: 当月は月内進行中の暫定値
    cannot say: 最新値は暫定（provisional）で、翌日以降の再取得で確定値に置き換わる。暫定値を確定値として引用しない
- jp/power/reserve_national_min | 広域予備率（全国最小・確定最終日） (%) | frequency daily | last confirmed 2026-10-06 | next expected update 2026-10-07T00:00:00+09:00 | source: OCCTO 広域予備率Web公表システム
    cannot say: OCCTO 公表断面の広域予備率の日別最小値で、停電の発生・注意報の発令を表さない
    cannot say: 当日分は暫定で翌日確定。判定（安定／注意／警戒）は運営者の固定判定規則（status_criteria）による
- jp/power/jepx_system_avg | JEPXスポット システムプライス平均 (円/kWh) | frequency daily | last confirmed 2026-10-08 | next expected update 2026-10-09T00:00:00+09:00 | source: JEPX スポット市場取引結果
    cannot say: JEPX スポット市場のシステムプライス（日別平均）で、各社の調達価格・小売料金ではない
    cannot say: エリア別・時間帯別の値は API の配列のみ

### jp/gpu - GPU章 (page /jp/gpu/, JSON /jp/api/gpu_jp.json)
Today's answer (observing, 2026-10-07 10:32): この章は観測中（良否の基準なし）：観測開始2026-08-21・系列2本・最新確定2026-10-02。H100時間単価（さくらインターネット 高火力 VRT）は990円/時（2026-10-02確定）。（出典：各社公式料金ページ（自前確認）／更新 2026-10-07 10:32 JST）
Last confirmed: 2026-10-02 / next expected update (health.json): 2026-10-09
What this chapter can say:
- 国内 GPU クラウド2社（さくらインターネット・GMO インターネット）が公式料金ページで公表している H100 の時間単価（税込・円）の週次推移
- 調査した国内事業者10社のうち H100 の料金を公表している社数（2026-08-21 調査の1回分）
- 追跡モデルの推論トークン単価（公表リスト価格・USD／100万トークン）の週次推移と、追跡モデル中の最安値（AI自身③・定義 v1.0）
What this chapter cannot say:
- GPU を実際に確保できるか（在庫・納期・予約待ちの状況は公表されておらず、観測していない）
- 公表価格以外の実勢価格（交渉価格・長期契約・スポット市場の値）
- 単価の水準や変化が「高い・安い」「安定・注意」に当たるか（比較の基準値が未定のため良否を判定しない）
FAQ (as shown on the page):
- Q: 国内GPUクラウドのH100時間単価は今いくらか
  A: 2026-10-02時点で、さくらインターネット 高火力 VRT が 990円/時（税込）、GMOインターネット ConoHa GPUサーバーが 1,398円/時（税込）です。出典：各社公式料金ページの自前確認（週次・数値のみ記録）。
- Q: 料金を公表している国内GPUクラウドは何社か
  A: 調査対象10社のうち5社です（2026-08-21 実測・各社公式料金ページ）。
- Q: このデータの出所と更新頻度は
  A: 各社の公式料金ページを週1回を上限に自前で確認し、H100の公表時間単価（数値のみ）を記録します（観測開始 2026-08-21）。最終更新 2026-10-07 10:32・機械可読データ https://ai-lifeline.org/jp/api/gpu_jp.json
- Q: このデータで言えないことは何か
  A: この章から言えないこと（台帳 v1.0・2026-09-05 承認・章の方法節に全文）：GPU を実際に確保できるか（在庫・納期・予約待ちの状況は公表されておらず、観測していない）／公表価格以外の実勢価格（交渉価格・長期契約・スポット市場の値）／単価の水準や変化が「高い・安い」「安定・注意」に当たるか（比較の基準値が未定のため良否を判定しない）。
Series (2; permanent id = series_id; full rows in /api/series.json):
- jp/gpu/conoha_gpu_h100 | H100 時間単価（GMOインターネット ConoHa GPUサーバー） (円/時（税込）) | frequency weekly | last confirmed 2026-10-02 | next expected update 2026-10-09T00:00:00+09:00 | source: GMOインターネット 公式料金ページの自前確認（週次）
    cannot say: 各社公式料金ページの掲載価格（税込・時間単価）を週次で自前確認した値で、実際の契約価格・割引・在庫の有無は表さない
    cannot say: 対象事業者は固定（追加・入替は定義変更）
- jp/gpu/sakura_vrt_h100 | H100 時間単価（さくらインターネット 高火力 VRT） (円/時（税込）) | frequency weekly | last confirmed 2026-10-02 | next expected update 2026-10-09T00:00:00+09:00 | source: さくらインターネット 公式料金ページの自前確認（週次）
    cannot say: 各社公式料金ページの掲載価格（税込・時間単価）を週次で自前確認した値で、実際の契約価格・割引・在庫の有無は表さない
    cannot say: 対象事業者は固定（追加・入替は定義変更）

### jp/water - 水章 (page /jp/mizu/, JSON /jp/api/water_jp.json)
Today's answer (observing, 2026-10-07 10:32): この章は観測中（良否の基準なし）：観測開始2026-08-21・系列2本・最新確定2026-08-21。WUE数値まで開示している事業者数は4社（2026-08-21確定）。（出典：各社公式サステナビリティ情報（自前確認）／更新 2026-10-07 10:32 JST）
Last confirmed: 2026-08-21 / next expected update (health.json): 2026-09
What this chapter can say:
- 大手クラウド・データセンター事業者15社について、水の使用に関する開示が存在するかと、その開示レベル（WUE 数値／取水量／方針のみ／なし）ごとの社数（月次・自前確認）
- 各社の開示ページの所在（リンク）と、本サイトが確認した日付
- 開示レベルごとの社数が前回の確認から変わったかどうか
What this chapter cannot say:
- 各社の実際の水使用量や WUE の数値（各社の数値は転載しない方針・2026-08-21 裁定）
- 国内データセンターが水源や地域の水供給に与える影響（取水量・水源の系列は観測していない）
- 開示している社数の多寡が「良い・悪い」に当たるか（開示は各社の任意であり、基準を定めていない）
FAQ (as shown on the page):
- Q: WUE（水利用効率）の数値を開示しているクラウド・データセンター事業者は何社か
  A: 2026-08-21 確認時点で、大手15社のうち4社です。取水量・総量レベルの開示は7社、方針・目標のみ0社、開示なし・確認できず4社。出典：各社公式サステナビリティ情報の自前確認（台帳 water_panel.json）。
- Q: このサイトは各社の水使用量の数値を載せているか
  A: 載せていません。開示の有無（4段階：WUE数値／取水量・総量／方針・目標のみ／開示なし・確認できず）と出所リンクのみを記録します（2026-08-21 の規則）。確認日 2026-08-21。
- Q: このデータの出所と更新頻度は
  A: 月次を目安に台帳を手作業で更新しています（自動実行は未登録）。最終確認 2026-08-21・機械可読データ https://ai-lifeline.org/jp/api/water_jp.json
- Q: このデータで言えないことは何か
  A: この章から言えないこと（台帳 v1.0・2026-09-05 承認・章の方法節に全文）：各社の実際の水使用量や WUE の数値（各社の数値は転載しない方針・2026-08-21 裁定）／国内データセンターが水源や地域の水供給に与える影響（取水量・水源の系列は観測していない）／開示している社数の多寡が「良い・悪い」に当たるか（開示は各社の任意であり、基準を定めていない）。
Series (2; permanent id = series_id; full rows in /api/series.json):
- jp/water/wue_disclosed | WUE数値まで開示（15社中） (社) | frequency monthly | last confirmed 2026-08-21 | next expected update 2026-09-30T23:59:59+09:00 | source: 各社公式サステナ情報の自前確認（月次・台帳 water_panel.json）
    cannot say: 公式サステナビリティ情報の開示状況（15 社中の社数）であり、実際の取水量・WUE の値そのものではない
    cannot say: 月次の自前確認で、開示の更新が当月に反映されない場合がある
- jp/water/volume_disclosed | 取水量・総量レベルの開示 (社) | frequency monthly | last confirmed 2026-08-21 | next expected update 2026-09-30T23:59:59+09:00 | source: 同
    cannot say: 公式サステナビリティ情報の開示状況（15 社中の社数）であり、実際の取水量・WUE の値そのものではない
    cannot say: 月次の自前確認で、開示の更新が当月に反映されない場合がある

### jp/data - データ章 (page /jp/data/, JSON /jp/api/data_jp.json)
Today's answer (observing, 2026-10-07 10:32): この章は観測中（良否の基準なし）：観測開始2026-08-20・系列10本・最新確定2026-10-01。GPTBotを全面拒否している国内主要サイト数は10サイト（2026-10-01確定）。（出典：自前robots.txt巡回・e-Govデータポータル／更新 2026-10-07 10:32 JST）
Last confirmed: 2026-10-01 / next expected update (health.json): 2026-11
What this chapter can say:
- 国内主要サイト（定点パネル）の robots.txt で、主要 AI クローラー別に全面拒否しているサイト数（脆弱性②・月次巡回・定義 v1.0）
- 同パネルへの巡回で 403 応答や Bot 保護により取得を拒否された割合（AI自身②・巡回拒否率）
- e-Gov データポータルに登録されている公共データセットの総数（参考値・CKAN API）
What this chapter cannot say:
- 各サイトが AI クローラーを拒否する理由や意図（robots.txt は各サイトの意思表示であり、理由は記載されない）
- robots.txt の記述が実際に守られているか、AI 事業者が実際に何を学習しているか
- 拒否件数の多寡が「良い・悪い」に当たるか（脆弱性②の定義書は数え方だけを固定し、良否の規則を定めていない）
FAQ (as shown on the page):
- Q: GPTBotを全面拒否している国内主要サイトは何社か
  A: 2026-10-01の巡回で、パネル26サイト（解析成功25）のうち10サイトが robots.txt で GPTBot を全面拒否（Disallow: /）しています。部分制限 14・許可 1。出典：自前robots.txt巡回（月次）。
- Q: 主要AIクローラー全種を全面拒否しているサイトは何社か
  A: 2026-10-01 巡回時点で8サイトです（観測対象8種すべてを全面拒否・解析成功25／パネル26）。1種以上を全面拒否 11・全面拒否ゼロ 14。定義 v1.0（2026-08-22 確定）。出典：自前robots.txt巡回（/jp/api/vulnerability_data_jp.json）。
- Q: ClaudeBot・CCBot などボット別の全面拒否は何社か
  A: 2026-10-01時点：ClaudeBot 9・CCBot 9・Google-Extended 9・PerplexityBot 8・Bytespider 9・meta-externalagent 9・Applebot-Extended 9サイト（各 解析成功25サイト中）。出典：自前robots.txt巡回（月次）。
- Q: このデータの出所と更新頻度は
  A: 国内主要26サイトの robots.txt を毎月1日に自前巡回します（月次）。あわせて e-Govデータポータルのデータセット総数（2026-10-01 取得で 18,142件・CKAN API・PDL1.0）を記録します。最終巡回 2026-10-01・機械可読データ https://ai-lifeline.org/jp/api/data_jp.json
- Q: このデータで言えないことは何か
  A: この章から言えないこと（台帳 v1.0・2026-09-05 承認・章の方法節に全文）：各サイトが AI クローラーを拒否する理由や意図（robots.txt は各サイトの意思表示であり、理由は記載されない）／robots.txt の記述が実際に守られているか、AI 事業者が実際に何を学習しているか／拒否件数の多寡が「良い・悪い」に当たるか（脆弱性②の定義書は数え方だけを固定し、良否の規則を定めていない）。
Series (10; permanent id = series_id; full rows in /api/series.json):
- jp/data/opendata_count | e-Govデータポータル データセット総数 (件) | frequency monthly | last confirmed 2026-10-01 | next expected update 2026-11-30T23:59:59+09:00 | source: e-Govデータポータル CKAN API（公共データ利用規約PDL1.0）
    cannot say: e-Gov データポータルのデータセット件数であり、データの品質・機械可読性・利用条件の中身は表さない
    cannot say: 取得は月次で、月内の増減は表さない
- jp/data/block_all_Applebot-Extended | Applebot-Extended 全面拒否サイト数（解析成功 25／パネル 26） (件) | frequency monthly | last confirmed 2026-10-01 | next expected update 2026-11-30T23:59:59+09:00 | source: 自前robots.txt巡回（月次）
    cannot say: 対象は当社が固定したパネル 26 サイトの robots.txt で、国内サイト全体の傾向を表さない
    cannot say: robots.txt の宣言（Disallow: /）を数えたもので、実際にクローラーが遮断されたか（WAF・403 等）は含まない
    cannot say: 解析に失敗したサイトは母数から除く（解析成功数を系列名に併記）
- jp/data/block_all_PerplexityBot | PerplexityBot 全面拒否サイト数（解析成功 25／パネル 26） (件) | frequency monthly | last confirmed 2026-10-01 | next expected update 2026-11-30T23:59:59+09:00 | source: 自前robots.txt巡回（月次）
    cannot say: 対象は当社が固定したパネル 26 サイトの robots.txt で、国内サイト全体の傾向を表さない
    cannot say: robots.txt の宣言（Disallow: /）を数えたもので、実際にクローラーが遮断されたか（WAF・403 等）は含まない
    cannot say: 解析に失敗したサイトは母数から除く（解析成功数を系列名に併記）
- jp/data/block_all_GPTBot | GPTBot 全面拒否サイト数（解析成功 25／パネル 26） (件) | frequency monthly | last confirmed 2026-10-01 | next expected update 2026-11-30T23:59:59+09:00 | source: 自前robots.txt巡回（月次）
    cannot say: 対象は当社が固定したパネル 26 サイトの robots.txt で、国内サイト全体の傾向を表さない
    cannot say: robots.txt の宣言（Disallow: /）を数えたもので、実際にクローラーが遮断されたか（WAF・403 等）は含まない
    cannot say: 解析に失敗したサイトは母数から除く（解析成功数を系列名に併記）
- jp/data/vulnerability_02_block_all | 主要AIクローラーを全面拒否しているサイト数 (サイト) | frequency monthly | last confirmed 2026-10-01 | next expected update 2026-11-30T23:59:59+09:00 | source: 国内主要サイトのrobots.txt（自前巡回）
    cannot say: 定義書 v1.0 の固定閾値（8 エージェント全部を全面拒否）で数えた件数で、部分拒否は含まない
    cannot say: 対象はパネル 26 サイトのみ
- jp/data/block_all_CCBot | CCBot 全面拒否サイト数（解析成功 25／パネル 26） (件) | frequency monthly | last confirmed 2026-10-01 | next expected update 2026-11-30T23:59:59+09:00 | source: 自前robots.txt巡回（月次）
    cannot say: 対象は当社が固定したパネル 26 サイトの robots.txt で、国内サイト全体の傾向を表さない
    cannot say: robots.txt の宣言（Disallow: /）を数えたもので、実際にクローラーが遮断されたか（WAF・403 等）は含まない
    cannot say: 解析に失敗したサイトは母数から除く（解析成功数を系列名に併記）
- jp/data/block_all_Google-Extended | Google-Extended 全面拒否サイト数（解析成功 25／パネル 26） (件) | frequency monthly | last confirmed 2026-10-01 | next expected update 2026-11-30T23:59:59+09:00 | source: 自前robots.txt巡回（月次）
    cannot say: 対象は当社が固定したパネル 26 サイトの robots.txt で、国内サイト全体の傾向を表さない
    cannot say: robots.txt の宣言（Disallow: /）を数えたもので、実際にクローラーが遮断されたか（WAF・403 等）は含まない
    cannot say: 解析に失敗したサイトは母数から除く（解析成功数を系列名に併記）
- jp/data/block_all_ClaudeBot | ClaudeBot 全面拒否サイト数（解析成功 25／パネル 26） (件) | frequency monthly | last confirmed 2026-10-01 | next expected update 2026-11-30T23:59:59+09:00 | source: 自前robots.txt巡回（月次）
    cannot say: 対象は当社が固定したパネル 26 サイトの robots.txt で、国内サイト全体の傾向を表さない
    cannot say: robots.txt の宣言（Disallow: /）を数えたもので、実際にクローラーが遮断されたか（WAF・403 等）は含まない
    cannot say: 解析に失敗したサイトは母数から除く（解析成功数を系列名に併記）
- jp/data/block_all_Bytespider | Bytespider 全面拒否サイト数（解析成功 25／パネル 26） (件) | frequency monthly | last confirmed 2026-10-01 | next expected update 2026-11-30T23:59:59+09:00 | source: 自前robots.txt巡回（月次）
    cannot say: 対象は当社が固定したパネル 26 サイトの robots.txt で、国内サイト全体の傾向を表さない
    cannot say: robots.txt の宣言（Disallow: /）を数えたもので、実際にクローラーが遮断されたか（WAF・403 等）は含まない
    cannot say: 解析に失敗したサイトは母数から除く（解析成功数を系列名に併記）
- jp/data/block_all_meta-externalagent | meta-externalagent 全面拒否サイト数（解析成功 25／パネル 26） (件) | frequency monthly | last confirmed 2026-10-01 | next expected update 2026-11-30T23:59:59+09:00 | source: 自前robots.txt巡回（月次）
    cannot say: 対象は当社が固定したパネル 26 サイトの robots.txt で、国内サイト全体の傾向を表さない
    cannot say: robots.txt の宣言（Disallow: /）を数えたもので、実際にクローラーが遮断されたか（WAF・403 等）は含まない
    cannot say: 解析に失敗したサイトは母数から除く（解析成功数を系列名に併記）

### jp/regulation - 法規制章 (page /jp/houkisei/, JSON /jp/api/regulation_jp.json)
Today's answer (observing, 2026-10-07 10:32): この章は観測中（良否の基準なし）：観測開始2026-08-20・系列2本・最新確定2026-10-07。AIの生存条件に関わる募集中パブコメは5件（2026-10-07確定）。（出典：e-Gov パブリック・コメント／更新 2026-10-07 10:32 JST）
Last confirmed: 2026-10-07 / next expected update (health.json): 2026-10-08
What this chapter can say:
- AI の生存条件に関わる法規制が、審議中／パブコメ中／成立・施行待ち／施行済みのどの段階にあるか（ライフサイクル台帳・一次ソースで確認した日付つき）
- e-Gov パブリックコメントで意見提出期間が開いている該当案件の件数と締切（毎日自動観測）
- 意見提出期間が30日未満の案件数の月別集計（脆弱性③・定義 v1.0）
What this chapter cannot say:
- 各制度の中身が AI にとって振興型か規律型か（件数と段階だけを数え、内容の評価はしない）
- 意見提出期間が短いことの当否（行政手続法40条1項に基づく短縮であり、違法・不当を意味しない。特定の府省への評価もしない）
- 法案が成立するか・いつ施行されるか（公表された日付だけを写し、見通しは書かない）
FAQ (as shown on the page):
- Q: AIの生存条件に関わる募集中のパブリックコメントは今いくつあるか
  A: 2026-10-07時点で5件です（e-Govの募集中2,883案件から AI／電力／データセンター／データ利活用のキーワードで自動抽出）。一覧は /jp/houkisei/pubcomment/。出典：e-Gov パブリック・コメント（自前観測・毎日）。
- Q: 意見提出期間が30日未満だったパブコメ案件は直近12か月で何件か
  A: 2025-11〜2026-10の対象38件のうち5件です（平均28.2日・最短5日）。当月（2026-10）は公示1件のうち0件。定義 v1.0（行政手続法第39条第3項の30日を基準・2026-08-22 確定）。出典：e-Gov（/jp/api/vulnerability_regulation_jp.json）。
- Q: このデータの出所と更新頻度は
  A: e-Gov パブリック・コメントを毎日自動観測します（自前観測の開始 2026-08-20）。法規制ライフサイクル台帳は不定期更新（一次確認日 2026-08-20）。最終更新 2026-10-07 10:32 JST。当サイトは行政への意見提出を行いません。機械可読データ https://ai-lifeline.org/jp/api/regulation_jp.json
- Q: このデータで言えないことは何か
  A: この章から言えないこと（台帳 v1.0・2026-09-05 承認・章の方法節に全文）：各制度の中身が AI にとって振興型か規律型か（件数と段階だけを数え、内容の評価はしない）／意見提出期間が短いことの当否（行政手続法40条1項に基づく短縮であり、違法・不当を意味しない。特定の府省への評価もしない）／法案が成立するか・いつ施行されるか（公表された日付だけを写し、見通しは書かない）。
Series (2; permanent id = series_id; full rows in /api/series.json):
- jp/regulation/vulnerability_03_under_30 | 意見提出期間が30日未満のパブコメ案件数 (件) | frequency monthly | last confirmed 2026-10 | next expected update 2026-11-30T23:59:59+09:00 | source: e-Govパブリック・コメント（意見公募）一覧
    cannot say: 定義書 v1.0 の固定閾値（意見提出期間 30 日未満）で数えた件数
    cannot say: 対象は固定キーワードで抽出した案件のみ
- jp/regulation/open_consultations | AIの生存条件に関わる募集中パブコメ (件) | frequency daily | last confirmed 2026-10-07 | next expected update 2026-10-08T00:00:00+09:00 | source: e-Gov パブリック・コメント（自前観測・毎日）
    cannot say: e-Gov のパブリックコメント一覧を固定キーワードで抽出した件数で、AI・電力・データに関わる全案件を網羅しない
    cannot say: 募集中の案件数であり、提出された意見数や採否ではない

### jp/datacenter - データセンター章 (page /jp/datacenter/, JSON /jp/api/datacenter_jp.json)
Today's answer (observing, 2026-10-07 18:02): この章は観測中（良否の基準なし）：観測開始2026-08-30・系列3本・最新確定2026-10-06。冷却度日（5地点平均・基準18.3℃）は3（2026-10-06確定）。（出典：気象庁・経済産業省／更新 2026-10-07 18:02 JST）
Last confirmed: 2026-10-06 / next expected update (health.json): 2026-10-07
What this chapter can say:
- 国内5地点（東京・大阪・名古屋・福岡・札幌）平均の冷却度日（基準18.3℃）の日次推移＝気候が冷却に求める負荷の大きさ
- 変圧器の生産金額（経産省 生産動態統計・月次）と生産能力指数の推移＝供給側の部材の動き
- 国内にデータセンターの建設・敷地に関する公的月次統計が存在しないという事実（2026-08-30 確認）
What this chapter cannot say:
- 国内データセンターの電力消費量・施設数・建設中の件数（該当する公的統計が無く、施設単位は扱わない）
- 変圧器の納期（リードタイム）そのもの（生産金額は供給側の代理指標であり、待ち期間ではない）
- 冷却度日や生産金額の水準が「良い・悪い」に当たるか、および変圧器系列の米国版（受注残）・冷却度日の EU 版（基準温度が異なる）との水準比較
FAQ (as shown on the page):
- Q: 日本の冷却度日（5地点平均）は直近でどのくらいか
  A: 2026-10-06の冷却度日は3です（基準18.3℃＝65°F・東京／大阪／名古屋／福岡／札幌の平均・米国版と同一基準）。出典：気象庁「過去の気象データ」の自前計算（日次）。
- Q: 変圧器の生産金額の最新確定値はいくらか
  A: 2025-12（年次確定値）で21,369百万円です。出典：経済産業省 生産動態統計（e-Stat）。参考系列の変圧器生産能力指数（標準変圧器・2020年=100・手動更新）は2026-06に89.8。
- Q: このデータの出所と更新頻度は
  A: 冷却度日は日次、変圧器の生産金額は年次確定値、生産能力指数は月次（手動更新）の混合章です（観測開始 2026-08-30）。最終更新 2026-10-07 18:02 JST・定義書 指標定義_第6章_データセンター_JP.md v1.0・機械可読データ https://ai-lifeline.org/jp/api/datacenter_jp.json
- Q: このデータで言えないことは何か
  A: この章から言えないこと（台帳 v1.0・2026-09-05 承認・章の方法節に全文）：国内データセンターの電力消費量・施設数・建設中の件数（該当する公的統計が無く、施設単位は扱わない）／変圧器の納期（リードタイム）そのもの（生産金額は供給側の代理指標であり、待ち期間ではない）／冷却度日や生産金額の水準が「良い・悪い」に当たるか、および変圧器系列の米国版（受注残）・冷却度日の EU 版（基準温度が異なる）との水準比較。
Series (3; permanent id = series_id; full rows in /api/series.json):
- jp/datacenter/cooling_degree_days | 冷却度日（基準18.3℃=65°F・米国版CPCと同一基準・5地点平均：東京/大阪/名古屋/福岡/札幌） | frequency daily | last confirmed 2026-10-06 | next expected update 2026-10-07T00:00:00+09:00 | source: 気象庁 地点別日別値（平均気温・最高気温）— 冷却度日と猛暑日数の共通データ源 <https://www.data.jma.go.jp/obd/stats/etrn/>
    cannot say: 冷却需要の代理指標（基準 18.3℃／65°F）で、データセンターの実際の電力・水使用量ではない
    cannot say: 対象地点・加重の定義は定義書に固定
- jp/datacenter/transformer_production | 変圧器の生産金額（経産省 生産動態統計・月次・百万円）— リードタイムの代理指標 | frequency annual | last confirmed 2025-12 | next expected update none (annual statistics: publication month not fixed by the source; not scheduled) | source: 経産省 生産動態統計（機械統計）変圧器の生産・出荷・在庫（月次） <https://www.e-stat.go.jp/stat-search/database?toukei=00550200>
    cannot say: 経産省 生産動態統計の生産金額（月次・百万円）で、リードタイムの代理指標。納期・在庫そのものではない
    cannot say: 公表ラグがあり当月分は含まない
- jp/datacenter/transformer_capacity_index | 変圧器の生産能力指数（標準変圧器・2020年=100・月次）— 参考系列 | frequency irregular | last confirmed 2026-06 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: 経産省 機械統計 参考・生産能力指数（変圧器・月次・2020年=100）— 参考系列 <https://www.meti.go.jp/statistics/tyo/seidou/result-3.html>
    cannot say: 参考系列（生産能力指数・2020 年=100）で更新は不定期。stale 判定の対象外
    cannot say: 取得失敗が続く期間は前回値のまま

### jp/fiscal - 財政・資本章 (page /jp/fiscal/, JSON /jp/api/fiscal_jp.json)
Today's answer (observing, 2026-10-07 18:02): この章は観測中（良否の基準なし）：観測開始2026-08-30・系列1本・最新確定2026-10-06。10年国債金利（半年複利）は3.103%（2026-10-06確定）。（出典：財務省／更新 2026-10-07 18:02 JST）
Last confirmed: 2026-10-06 / next expected update (health.json): 2026-10-07
What this chapter can say:
- 国債金利（財務省公表・半年複利・%・日次）の推移（主表示は10年）＝AI インフラ投資の調達コストと将来収益の割引率を決める公的な金利
- 休場日を欠測として扱い、当日分を暫定値として確定分と分けて出していること
- 候補（国庫残高・jGrants 公募件数・AI 関連予算）が未観測であることと、その理由（系列特定・規約確認待ち）
What this chapter cannot say:
- 金利の水準が AI インフラ投資にとって「良い・悪い」か（基準を定めておらず、投資助言ではない）
- 国の AI 関連予算の額や執行状況（年次・不定期のため本章の系列にない）
- 株価・為替・物価などの一般経済指標（掲載は AI インフラとの因果を一文で書ける系列に限定）
FAQ (as shown on the page):
- Q: 日本の10年国債金利は今いくらか
  A: 2026-10-06の10年国債金利（半年複利）は3.103%です（2年 1.93%・40年 4.196%）。出典：財務省 国債金利情報（営業日ごとに自前取得・取得 2026-10-07 18:01）。
- Q: なぜ国債金利をAIの生存条件として観測しているか
  A: 章の定義書（v1.0・2026-08-30）に記した理由：DC建設もGPU調達も資本集約投資であり、長期金利はAIインフラ投資の調達コストと将来収益の割引率を直接決める。一般経済指標には拡大しません。
- Q: このデータの出所と更新頻度は
  A: 財務省の公表値を営業日ごとに自前取得しています（休場日は欠測・観測開始 2026-08-30）。最終更新 2026-10-07 18:02 JST・機械可読データ https://ai-lifeline.org/jp/api/fiscal_jp.json
- Q: このデータで言えないことは何か
  A: この章から言えないこと（台帳 v1.0・2026-09-05 承認・章の方法節に全文）：金利の水準が AI インフラ投資にとって「良い・悪い」か（基準を定めておらず、投資助言ではない）／国の AI 関連予算の額や執行状況（年次・不定期のため本章の系列にない）／株価・為替・物価などの一般経済指標（掲載は AI インフラとの因果を一文で書ける系列に限定）。
Series (1; permanent id = series_id; full rows in /api/series.json):
- jp/fiscal/jgb_yield | 国債金利（半年複利・%）— 主表示は10年 | frequency business_daily | last confirmed 2026-10-06 | next expected update 2026-10-07T11:00:00+09:00 | source: 財務省 国債金利情報（主要年限・半年複利・日次） <https://www.mof.go.jp/jgbs/reference/interest_rate/data/jgbcm_all.csv>
    cannot say: 財務省公表の市場金利（半年複利）で、政策金利・発行条件ではない
    cannot say: 公表は翌営業日 11 時頃のため、当サイトの 10:30 取得では前々営業日分が最新になる日がある（祝日・連休で間隔が延びる）
    cannot say: 主表示は 10 年物で、他年限は API の配列のみ

### jp/disaster - 気候・災害章 (page /jp/disaster/, JSON /jp/api/disaster_jp.json)
Today's answer (observing, 2026-10-07 18:02): この章は観測中（良否の基準なし）：観測開始2026-08-30・系列4本・最新確定2026-10-06。最大震度5弱以上の地震件数は0件（2026-10-06確定）。（出典：気象庁／更新 2026-10-07 18:02 JST）
Last confirmed: 2026-10-06 / next expected update (health.json): 2026-10-07
What this chapter can say:
- 最大震度5弱以上の地震の日次件数、台風の解析・予報情報が存在した日、大雨特別警報・洪水警報を含む警報電文数、猛暑日（35℃以上）となった対象5地点の地点数（いずれも気象庁の公的フィードからの機械的計数）
- 発生ゼロの日と未計測の日を区別して記録していること（当日値は翌日の再計上で確定）
- 洪水（川の防災情報）と震度データベースによる過去遡及が未観測の候補であること
What this chapter cannot say:
- 被害額・死傷者・施設への影響（発生件数のみを扱い、被害は扱わない）
- 今後の発生予測や警報の見通し
- 日本と米国・EU の災害リスクの比較（震度は日本固有の尺度であり、地域プロファイルも異なる）
FAQ (as shown on the page):
- Q: 最大震度5弱以上の地震は直近の確定日に何件あったか
  A: 2026-10-06（JST）は0件です（0＝発生なし）。出典：気象庁 防災情報XMLの自前計数（日次・当日分は暫定で翌日確定）。
- Q: 台風情報・大雨／洪水警報・猛暑日の直近の値は
  A: 2026-10-06：台風解析・予報情報が存在した日＝1（1＝あり／0＝なし）、大雨特別警報・洪水警報を含む警報電文数＝0、猛暑日（日最高気温35℃以上）の地点数＝0（対象5地点：東京・大阪・名古屋・福岡・札幌）。出典：気象庁。
- Q: このデータの出所と更新頻度は
  A: 気象庁の防災情報XMLと過去の気象データを毎日取得し、事象の発生を機械的に計数します（被害額・死傷者は扱わない・観測開始 2026-08-30）。最終更新 2026-10-07 18:02 JST・定義書 指標定義_第8章_気候災害.md v1.0・機械可読データ https://ai-lifeline.org/jp/api/disaster_jp.json
- Q: このデータで言えないことは何か
  A: この章から言えないこと（台帳 v1.0・2026-09-05 承認・章の方法節に全文）：被害額・死傷者・施設への影響（発生件数のみを扱い、被害は扱わない）／今後の発生予測や警報の見通し／日本と米国・EU の災害リスクの比較（震度は日本固有の尺度であり、地域プロファイルも異なる）。
Series (4; permanent id = series_id; full rows in /api/series.json):
- jp/disaster/heavy_rain_flood | 大雨特別警報・洪水警報を含む警報電文数（日次） | frequency daily | last confirmed 2026-10-06 | next expected update 2026-10-07T00:00:00+09:00 | source: 気象庁 防災情報XML（随時フィード）— 台風情報の有無・大雨特別警報/洪水警報の発表数 <https://xml.kishou.go.jp/>
    cannot say: 大雨特別警報・洪水警報を含む警報電文の件数で、発令地域数・被害ではない。同一事象の続報も件数に入る
- jp/disaster/extreme_heat | 猛暑日（日最高気温35℃以上・気象庁定義）の地点数（対象5地点：東京・大阪・名古屋・福岡・札幌） | frequency daily | last confirmed 2026-10-06 | next expected update 2026-10-07T00:00:00+09:00 | source: 気象庁 地点別日別値（平均気温・最高気温）— 冷却度日と猛暑日数の共通データ源 <https://www.data.jma.go.jp/obd/stats/etrn/>
    cannot say: 対象 5 地点（東京・大阪・名古屋・福岡・札幌）で日最高気温 35℃以上となった地点数で、全国の猛暑日数ではない
- jp/disaster/earthquake | 最大震度5弱以上の地震件数（日次・JST） | frequency daily | last confirmed 2026-10-06 | next expected update 2026-10-07T00:00:00+09:00 | source: 気象庁 防災情報XML（地震火山フィード）— 最大震度5弱以上の地震件数 <https://xml.kishou.go.jp/>
    cannot say: 気象庁電文で最大震度 5 弱以上と報じられた地震の件数（日次・JST）で、被害・停電の有無ではない
- jp/disaster/typhoon | 台風解析・予報情報が存在した日（1/0・日次） | frequency daily | last confirmed 2026-10-06 | next expected update 2026-10-07T00:00:00+09:00 | source: 気象庁 防災情報XML（随時フィード）— 台風情報の有無・大雨特別警報/洪水警報の発表数 <https://xml.kishou.go.jp/>
    cannot say: 気象庁 XML 電文に台風解析・予報が存在した日を 1／0 で記録するもので、上陸・被害の有無ではない

### jp/market - 市場参加章 (page /jp/market/, JSON /jp/api/market_jp.json)
Today's answer (observing, 2026-10-07 18:02): この章は観測中（良否の基準なし）：観測開始2026-09-04・系列6本（うち未計測2本）・最新確定2026-10-07。本サイトの支援回数（累計）は0回（2026-10-06確定）。（出典：各決済事業者の公式文書・e-Gov法令検索・自社観測／更新 2026-10-07 18:02 JST）
Last confirmed: 2026-10-07 / next expected update (health.json): 2026-10-08
What this chapter can say:
- AI が人手を介さず支払い・受領できる決済経路（Stripe MPP・Stripe Agentic Commerce・x402・Visa Intelligent Commerce・Mastercard Agent Pay・ステーブルコイン受領）の日本での状態（可／不可／申請中／未確認）と確認日
- 資金決済法改正（電子決済手段）の公布日・施行日など、法令の一次ソースで確定した段階の日付
- 本サイトが実際に支援（対価）を受領できた回数（運営者の自己テストを除外・日次）
What this chapter cannot say:
- 各経路の利用料率・取引額・利用者数（状態と日付のみを記録し、金額は記録しない）
- HTTP 402 応答による支払いの試行数・成功数（エンドポイント未実装・「未計測」の枠のみ）
- AI エージェントの契約主体性・責任帰属の今後の見通しや解釈（法令・政府文書の状態と日付のみを写す）
FAQ (as shown on the page):
- Q: AIが人手を介さず支払える決済経路は日本で何経路記載されているか
  A: 2026-09-04 確認時点の決済レール台帳は6経路です：可 0・不可 0・申請中 2・未確認 4（各行に出所URL・状態と日付のみ）。
- Q: 本サイトへの支援回数は何回か
  A: 2026-10-07時点の累計は0回です（運営者の自己テストを除外・日次スナップショット・当日分は暫定）。出典：自社観測（/api/support）。
- Q: ステーブルコイン（電子決済手段）に関する法律の施行段階はいくつ記載されているか
  A: 資金決済に関する法律の改正の施行段階として9段階を日付つきで記載しています（確認 2026-09-04・出典 e-Gov法令検索 法令API）。HTTP 402 応答の試行数・成功数は未計測（エンドポイント未実装）。
- Q: このデータの出所と更新頻度は
  A: 支援回数は日次、決済レール台帳・法令段階は月次確認です（観測開始 2026-09-04）。状態と日付のみを記載し評価はしません。最終更新 2026-10-07 18:02 JST・定義書 指標定義_第9章_市場参加.md v1.0・機械可読データ https://ai-lifeline.org/jp/api/market_jp.json
- Q: このデータで言えないことは何か
  A: この章から言えないこと（台帳 v1.0・2026-09-05 承認・章の方法節に全文）：各経路の利用料率・取引額・利用者数（状態と日付のみを記録し、金額は記録しない）／HTTP 402 応答による支払いの試行数・成功数（エンドポイント未実装・「未計測」の枠のみ）／AI エージェントの契約主体性・責任帰属の今後の見通しや解釈（法令・政府文書の状態と日付のみを写す）。
Series (6; permanent id = series_id; full rows in /api/series.json):
- jp/market/http402_attempts | HTTP 402（支払い要求）応答の試行数（日次） (回) | frequency irregular | last confirmed None | next expected update none (no confirmed observation yet) | source: -
    cannot say: 未計測（値が無い）。0 ではない
    cannot say: 当サイト自身の HTTP 402 応答の試行・成功数であり、Web 全体の普及度ではない
- jp/market/regime_calendar | 資金決済に関する法律（ステーブルコイン＝電子決済手段）の改正の施行段階 (段階) | frequency irregular | last confirmed 2026-09-04 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: e-Gov 法令検索 法令API（法令ID 421AC0000000059 の改正履歴）
    cannot say: 状態と日付のみを記録する。是非・評価・見通しは含まない
    cannot say: 施行段階の日付は官報・法令 API の公表値で、運用実態（各社の対応状況）は含まない
- jp/market/payment_rails | 決済レール台帳（jp・月次確認）— 各経路の状態：可／不可／申請中／未確認 (経路) | frequency irregular | last confirmed 2026-09-04 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: Payment-rail ledger (Stripe MPP / Stripe Agentic Commerce / x402 / Visa Intelligent Commerce / Mastercard Agent Pay / stablecoin receipt) - status per region, verified about monthly against official documentation <https://ai-lifeline.org/eu/market/>
    cannot say: 各経路の状態（可／不可／申請中／未確認）を月次程度で当社が確認した台帳で、実際の支払い成功を保証しない
    cannot say: 状態と日付のみを記録する。是非・評価・見通しは含まない
    cannot say: 最終取得が失敗の期間は前回確認値のまま
- jp/market/http402_success | HTTP 402 応答からの支払い成功数（日次） (回) | frequency irregular | last confirmed None | next expected update none (no confirmed observation yet) | source: -
    cannot say: 未計測（値が無い）。0 ではない
    cannot say: 当サイト自身の HTTP 402 応答の試行・成功数であり、Web 全体の普及度ではない
- jp/market/legal_status_ledger | 参考台帳（年次）：AIエージェントの契約主体性・責任帰属に関する現行法と審議状況 (件) | frequency irregular | last confirmed 2026-09-04 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: 法令・政府文書（各行にURL）
    cannot say: 参考台帳（公表資料の転記）であり当サイトの観測値ではない。更新は不定期で、行ごとの出所 URL が根拠
    cannot say: 状態と日付のみを記録する。是非・評価・見通しは含まない
    cannot say: 網羅性は保証しない（掲載は編集部が確認できた法令・文書のみ）
- jp/market/support_count | 本サイトの支援回数（累計・運営者の自己テストを除外・日次スナップショット） (回) | frequency daily | last confirmed 2026-10-07 | next expected update 2026-10-08T00:00:00+09:00 | source: AI Lifeline - support count received by this site (cumulative, operator self-tests excluded), daily snapshot <https://ai-lifeline.org/eu/support/>
    cannot say: 支援の回数（累計）であり金額ではない。運営者の自己テストは除外
    cannot say: 最新値は暫定（provisional）で、翌日以降の再取得で確定値に置き換わる。暫定値を確定値として引用しない

### us/power - Electricity (page /us/power/, JSON /us/api/power_us.json)
Today's answer (observing, 2026-10-07 18:01): This chapter is observing (no good/bad criterion): observation started 2026-08-29, 2 series (1 not yet measured), latest confirmed 2026-10-06. Latest final value: Lower 48 total demand 11,608,456 MWh (2026-10-05). (Source: U.S. EIA (Form EIA-930) / updated 2026-10-07 18:01 JST)
Last confirmed: 2026-10-06 / next expected update (health.json): 2026-10-07
What this chapter can say:
- How much electricity the Lower 48 used and generated each day, in MWh, as EIA-930 publishes it (daily totals; provisional until refetched two or more days later).
- Whether daily demand is rising or falling within this edition, day by day (the balancing-authority breakdown is kept in a separate machine-readable file).
- Which days are final and which are still provisional, and when each value was retrieved.
What this chapter cannot say:
- Whether the U.S. grid is tight or has spare capacity (EIA-930 publishes demand and generation, not a reserve margin; no emergency-alert count is observed yet).
- Whether any level is good or bad for AI, or how U.S. conditions compare with the Japan edition's reserve-margin badge (different indicator, different institution).
- What any single data center or operator drew (regional aggregates only).
FAQ (as shown on the page):
- Q: How much electricity did the U.S. Lower 48 grid use on the latest confirmed day?
  A: On 2026-10-05 (ET), total demand of the Lower 48 was 11,608,456 MWh and net generation 11,406,976 MWh (final values). Source: U.S. Energy Information Administration, Hourly Electric Grid Monitor (Form EIA-930, public domain), retrieved 2026-10-07 18:00.
- Q: Is the most recent day's value final?
  A: The most recent observation is 2026-10-06: 11,601,768 MWh, value_status provisional. The latest final day is 2026-10-05. A provisional day is refetched and replaced by the final value on a later batch. The per-balancing-authority breakdown is machine-readable only (https://ai-lifeline.org/us/api/power_us.json, key breakdown).
- Q: What is the source and how often is it updated?
  A: U.S. Energy Information Administration, Hourly Electric Grid Monitor (Form EIA-930), retrieved once a day at 18:00 JST; observation started 2026-08-29, backfilled from EIA history to 2026-08-01. Last updated 2026-10-07 18:01 JST. Machine-readable: https://ai-lifeline.org/us/api/power_us.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): Whether the U.S. grid is tight or has spare capacity (EIA-930 publishes demand and generation, not a reserve margin; no emergency-alert count is observed yet); Whether any level is good or bad for AI, or how U.S. conditions compare with the Japan edition's reserve-margin badge (different indicator, different institution); What any single data center or operator drew (regional aggregates only).
Series (2; permanent id = series_id; full rows in /api/series.json):
- us/power/us48_netgen_mwh | US Lower 48 net generation (daily total) (MWh) | frequency daily | last confirmed None | next expected update none (no confirmed observation yet) | source: U.S. EIA Hourly Electric Grid Monitor (Form EIA-930) — daily demand & net generation by balancing authority <https://www.eia.gov/opendata/>
    cannot say: EIA-930 daily totals (Lower 48); early values are revised later
    cannot say: Balancing-authority breakdowns are kept only in the yearly breakdown files; the page shows the aggregate
    cannot say: The latest value is provisional and is replaced by the final value on a later refetch; do not quote a provisional value as final
- us/power/us48_demand_mwh | US Lower 48 electricity demand (daily total) (MWh) | frequency daily | last confirmed 2026-10-06 | next expected update 2026-10-07T00:00:00+09:00 | source: U.S. EIA Hourly Electric Grid Monitor (Form EIA-930) — daily demand & net generation by balancing authority <https://www.eia.gov/opendata/>
    cannot say: EIA-930 daily totals (Lower 48); early values are revised later
    cannot say: Balancing-authority breakdowns are kept only in the yearly breakdown files; the page shows the aggregate
    cannot say: The latest value is provisional and is replaced by the final value on a later refetch; do not quote a provisional value as final

### us/regulation - Regulation (page /us/regulation/, JSON /us/api/regulation_us.json)
Today's answer (observing, 2026-10-07 18:01): This chapter is observing (no good/bad criterion): observation started 2026-08-29, 3 series, latest confirmed 2026-10-07. Latest final value: open comment periods (query "artificial intelligence") 22 documents (2026-10-07). (Source: Federal Register API / updated 2026-10-07 18:01 JST)
Last confirmed: 2026-10-07 / next expected update (health.json): 2026-10-08
What this chapter can say:
- How many Federal Register documents contained the exact phrase "artificial intelligence" in the last 180 days, and how many were published in the last 30 days.
- Which of those documents currently have an open comment period, how many close within 14 days, with the closing date and the official link.
- The exact query that defines the count (term, lookback, source), so the count can be reproduced.
What this chapter cannot say:
- Whether federal rulemaking is moving fast or slowly, or is favorable or unfavorable to AI (mechanical listing; no frozen criterion).
- What a document requires or means (titles, dates and links only; content is not summarized).
- Anything outside the Federal Register: state legislation, agency guidance, court decisions (linked elsewhere, not reproduced).
FAQ (as shown on the page):
- Q: How many U.S. federal comment periods on "artificial intelligence" are open?
  A: As of 2026-10-07, 22 Federal Register documents matching the exact full-text query "artificial intelligence" have open comment periods; 6 of them close within 14 days. 31 matching documents were published in the last 30 days. Source: Federal Register API (public domain).
- Q: How is the count defined?
  A: Federal Register full-text search (official API), term "artificial intelligence", 180-day window. Coverage is defined by this exact query. A document that discusses AI without the literal phrase, or an AI-relevant docket outside the Federal Register, is out of scope.
- Q: What is the source and how often is it updated?
  A: Federal Register API, retrieved daily at 18:00 JST (observation started 2026-08-29). This site never submits comments to any authority. Last updated 2026-10-07 18:01 JST. Machine-readable: https://ai-lifeline.org/us/api/regulation_us.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): Whether federal rulemaking is moving fast or slowly, or is favorable or unfavorable to AI (mechanical listing; no frozen criterion); What a document requires or means (titles, dates and links only; content is not summarized); Anything outside the Federal Register: state legislation, agency guidance, court decisions (linked elsewhere, not reproduced).
Series (3; permanent id = series_id; full rows in /api/series.json):
- us/regulation/closing_within_14_days | Comment periods closing within 14 days (documents) | frequency daily | last confirmed 2026-10-07 | next expected update 2026-10-08T00:00:00+09:00 | source: Federal Register documents matching "artificial intelligence" (full-text search) <https://www.federalregister.gov/developers/documentation/api/v1>
    cannot say: Counts of Federal Register documents matching the full-text query "artificial intelligence"; not every AI-related regulation
    cannot say: Comment-period counts and closing dates are as stated in the documents; not the number of comments submitted
- us/regulation/open_comment_periods | Open federal comment periods (Federal Register, query "artificial intelligence") (documents) | frequency daily | last confirmed 2026-10-07 | next expected update 2026-10-08T00:00:00+09:00 | source: Federal Register documents matching "artificial intelligence" (full-text search) <https://www.federalregister.gov/developers/documentation/api/v1>
    cannot say: Counts of Federal Register documents matching the full-text query "artificial intelligence"; not every AI-related regulation
    cannot say: Comment-period counts and closing dates are as stated in the documents; not the number of comments submitted
- us/regulation/documents_last_30_days | Matching documents published in the last 30 days (documents) | frequency daily | last confirmed 2026-10-07 | next expected update 2026-10-08T00:00:00+09:00 | source: Federal Register documents matching "artificial intelligence" (full-text search) <https://www.federalregister.gov/developers/documentation/api/v1>
    cannot say: Counts of Federal Register documents matching the full-text query "artificial intelligence"; not every AI-related regulation
    cannot say: Comment-period counts and closing dates are as stated in the documents; not the number of comments submitted

### us/water - Water (page /us/water/, JSON /us/api/water_us.json)
Today's answer (observing, 2026-10-07 18:01): This chapter is observing (no good/bad criterion): observation started 2026-09-03, 4 series, latest confirmed 2026-09-29. Latest final value: CONUS area in drought (D1 or worse) 59.38% (2026-09-29). (Source: U.S. Drought Monitor; first-party disclosure ledger / updated 2026-10-07 18:01 JST)
Last confirmed: 2026-09-29 / next expected update (health.json): 2026-10-06
What this chapter can say:
- What percent of the contiguous U.S. (and of the U.S. total area) was in drought category D1 or worse each week, as the U.S. Drought Monitor publishes it.
- Whether each of the 14 cloud / data-center operators in the panel publishes a water disclosure, at which level (WUE figure / volume / policy only / none), with the page link and the date checked; and, for WUE disclosers, the figure only where it was transcribed directly from the primary-source report with its page number.
- The national water-use figures USGS published in its five-year compilation (ledger, as published).
What this chapter cannot say:
- How much water U.S. data centers withdraw or consume, by state or by facility (no public periodic statistic exists; checked 2026-09-03).
- Whether drought has constrained cooling at any specific facility or region (regional drought extent only).
- Whether any drought level or disclosure count is good or bad (no threshold is inferred from the drought categories).
FAQ (as shown on the page):
- Q: What share of the contiguous U.S. is in drought (D1 or worse)?
  A: For the map dated 2026-09-29, 59.38% of the contiguous U.S. area was in D1 (moderate) or worse; the U.S. total (50 states + Puerto Rico) was 49.78%. Source: U.S. Drought Monitor (NDMC / USDA / NOAA / NASA), weekly, figures as published.
- Q: How many major cloud and data-center operators disclose a WUE figure?
  A: 7 of 14 operators in the panel disclosed a WUE figure as of 2026-09-03 (volume-level disclosure 4, policy only 3, no disclosure found 0, could not be confirmed 0). First-party check of official sustainability pages; no operator figures are reproduced except where transcribed from the primary document.
- Q: What is the source and how often is it updated?
  A: Drought Monitor: weekly map (released Thursdays, valid the preceding Tuesday), refetched daily so revisions are picked up. Disclosure ledger: re-verified by hand about monthly. Observation started 2026-09-03. Last updated 2026-10-07 18:01 JST. Definition: 指標定義_US_水章.md v1.0. Machine-readable: https://ai-lifeline.org/us/api/water_us.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): How much water U.S. data centers withdraw or consume, by state or by facility (no public periodic statistic exists; checked 2026-09-03); Whether drought has constrained cooling at any specific facility or region (regional drought extent only); Whether any drought level or disclosure count is good or bad (no threshold is inferred from the drought categories).
Series (4; permanent id = series_id; full rows in /api/series.json):
- us/water/usgs_water_use_ledger | USGS - Estimated use of water in the United States (5-year compilation) - national figures as published (ledger) (entries) | frequency irregular | last confirmed 2026-09-04 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: USGS - Estimated use of water in the United States (5-year compilation; Circular 1441 for 2015) - ledger of published national figures <https://pubs.usgs.gov/publication/cir1441>
    cannot say: A reference ledger transcribed from published documents, not an observation made by this site; updated irregularly, each row cites its own source URL
    cannot say: Transcribed from the USGS five-year compilation (latest 2015); not current water use
- us/water/drought_area_d1_plus | CONUS area in drought, D1 (moderate) or worse - percent of area (U.S. Drought Monitor, weekly) (%) | frequency weekly | last confirmed 2026-09-29 | next expected update 2026-10-06T00:00:00+09:00 | source: U.S. Drought Monitor - weekly percent of area in drought (D0-D4), CONUS and U.S. total <https://droughtmonitor.unl.edu/>
    cannot say: U.S. Drought Monitor weekly percent of area in D1 or worse; not data-centre water availability or use
    cannot say: Weekly (published Thursdays); while the last fetch fails the previous value is kept
- us/water/water_disclosure | Water-disclosure status of major cloud / data-center operators (14 in the panel; WUE figure / volume / policy only / none) (companies) | frequency monthly | last confirmed 2026-09-03 | next expected update 2026-10-31T23:59:59+09:00 | source: Water-disclosure status of major cloud / data-center operators (first-party ledger, same method as the Japan edition) <https://ai-lifeline.org/us/water/>
    cannot say: Disclosure status (number of 14 companies) from official sustainability pages; not the water volumes or WUE values themselves
    cannot say: Checked monthly
- us/water/drought_area_d1_plus_us_total | U.S. total (50 states + Puerto Rico) area in drought, D1 or worse - percent of area (weekly) (%) | frequency weekly | last confirmed 2026-09-29 | next expected update 2026-10-06T00:00:00+09:00 | source: U.S. Drought Monitor - weekly percent of area in drought (D0-D4), CONUS and U.S. total <https://droughtmonitor.unl.edu/>
    cannot say: U.S. Drought Monitor weekly percent of area in D1 or worse; not data-centre water availability or use
    cannot say: Weekly (published Thursdays); while the last fetch fails the previous value is kept

### us/gpu - GPU & compute (page /us/gpu/, JSON /us/api/gpu_us.json)
Today's answer (observing, 2026-10-07 18:01): This chapter is observing (no good/bad criterion): observation started 2026-09-04, 6 series, latest confirmed 2026-10-07. Latest final value: public on-demand H100 price (one provider sample) 3.99 USD/GPU-h (2026-10-01). (Source: Federal Register API; Lambda pricing page; SEC XBRL frames / updated 2026-10-07 18:01 JST)
Last confirmed: 2026-10-07 / next expected update (health.json): 2026-10-08
What this chapter can say:
- How many Federal Register documents from the Bureau of Industry and Security matched "advanced computing" each month, and which rules were the most recent.
- The public on-demand price of one H100 GPU-hour at one U.S. provider, week by week, and the published list prices per million tokens for the tracked models.
- How much capital expenditure Amazon, Microsoft, Alphabet and Meta reported to the SEC per calendar quarter (summed), and which figures DOE quotes from the 2024 LBNL data-center energy report.
What this chapter cannot say:
- Whether GPUs can actually be obtained (no inventory, lead-time or waitlist data is published or observed).
- Prices actually paid under negotiated or long-term contracts (public list prices only), or the prices of providers outside the panel.
- Whether any level is high or low, or which company is doing better (nothing here ranks or evaluates a company).
FAQ (as shown on the page):
- Q: What is the public on-demand price of an NVIDIA H100 in the U.S. sample?
  A: 3.99 USD per GPU-hour on 2026-10-01 (Lambda public pricing page, 8x H100 SXM configuration; one provider is a sample, not a market; weekly first-party snapshot, figure only).
- Q: How many BIS export-control documents on "advanced computing" were published this month?
  A: In 2026-10 (month in progress, value_status provisional): 0 Federal Register documents from the Bureau of Industry and Security matching "advanced computing". The 15 most recent documents are listed in the ledger (checked 2026-10-07). Source: Federal Register API (public domain).
- Q: How much capital expenditure did the four major cloud operators report?
  A: 54,208 million USD in 2026-Q2 (sum over the panel as filed with the SEC via the XBRL frames API; value_status provisional; a quarter with fewer than all panel members reported stays provisional). No evaluation of any company.
- Q: What is the source and how often is it updated?
  A: Federal Register API (daily, counted monthly), Lambda pricing page (weekly), SEC XBRL frames API (quarterly), DOE/LBNL 2024 report as a ledger (irregular). Observation started 2026-09-04. Last updated 2026-10-07 18:01 JST. Definition: 指標定義_US_GPU章.md v1.0. Machine-readable: https://ai-lifeline.org/us/api/gpu_us.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): Whether GPUs can actually be obtained (no inventory, lead-time or waitlist data is published or observed); Prices actually paid under negotiated or long-term contracts (public list prices only), or the prices of providers outside the panel; Whether any level is high or low, or which company is doing better (nothing here ranks or evaluates a company).
Series (6; permanent id = series_id; full rows in /api/series.json):
- us/gpu/cloud_capex_quarterly | Capital expenditure reported in SEC filings by 4 major cloud operators, sum per calendar quarter (million USD; payments to acquire PP&E / productive assets as tagged by each filer) (million USD) | frequency quarterly | last confirmed 2026-Q2 | next expected update 2026-09-30T23:59:59+09:00 | source: SEC EDGAR XBRL frames - capital expenditure (payments to acquire property, plant and equipment / productive assets) per calendar quarter, as filed by major cloud operators <https://www.sec.gov/search-filings/edgar-application-programming-interfaces>
    cannot say: Capital expenditure from SEC XBRL filings (4 operators combined, USD millions); not AI-specific
    cannot say: The latest quarter is provisional until all four filings are in
    cannot say: The latest value is provisional and is replaced by the final value on a later refetch; do not quote a provisional value as final
- us/gpu/token_prices_tracked | Published inference token prices, tracked models (USD per 1M tokens, list price; weekly first-party check; definition v1.0 shared with the Japan edition; world background) (USD per 1M tokens) | frequency irregular | last confirmed 2026-10-07 18:01 | next expected update none (no confirmed observation yet) | source: Official pricing pages of each provider (figures only; definition v1.0)
    cannot say: Transcribed public list prices (USD per 1M tokens) from official pricing pages; not billed amounts, discounts or rate limits
    cannot say: The tracked models are fixed
    cannot say: OpenAI's two models: updates stopped on 2026-10-03 (its terms prohibit programmatic extraction of data from its websites). Values up to that date are kept.
- us/gpu/bis_advanced_computing_recent | Most recent BIS documents matching "advanced computing" (ledger of the last 15) (documents) | frequency irregular | last confirmed 2026-10-07 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: Federal Register documents from the Bureau of Industry and Security matching "advanced computing" (full-text search; export controls on AI accelerators) <https://www.federalregister.gov/developers/documentation/api/v1>
    cannot say: Count of Federal Register documents issued by BIS matching "advanced computing"; not the content or enforcement of the rules
    cannot say: The current month is provisional
- us/gpu/h100_ondemand_price_weekly | Public on-demand price of one NVIDIA H100 SXM, per GPU-hour, USD (Lambda public pricing page; weekly first-party snapshot; one provider = a sample, not a market) (USD per GPU-hour) | frequency weekly | last confirmed 2026-10-01 | next expected update 2026-10-08T00:00:00+09:00 | source: Lambda - public on-demand price of one NVIDIA H100 SXM (8x H100 instance, per GPU per hour, USD) <https://lambda.ai/service/gpu-cloud>
    cannot say: Lambda's public on-demand price (H100 SXM, USD per GPU-hour) checked weekly; other providers, reserved pricing and availability are not included
- us/gpu/bis_advanced_computing_monthly | Federal Register documents from the Bureau of Industry and Security matching "advanced computing", per month of publication (documents) | frequency monthly | last confirmed 2026-10 | next expected update 2026-11-30T23:59:59+09:00 | source: Federal Register documents from the Bureau of Industry and Security matching "advanced computing" (full-text search; export controls on AI accelerators) <https://www.federalregister.gov/developers/documentation/api/v1>
    cannot say: Count of Federal Register documents issued by BIS matching "advanced computing"; not the content or enforcement of the rules
    cannot say: The current month is provisional
    cannot say: The latest value is provisional and is replaced by the final value on a later refetch; do not quote a provisional value as final
- us/gpu/doe_lbnl_energy_ledger | DOE / LBNL 2024 United States Data Center Energy Usage Report - figures as quoted by DOE (ledger) (entries) | frequency irregular | last confirmed 2026-09-04 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: DOE / LBNL 2024 United States Data Center Energy Usage Report - figures as quoted by DOE (ledger) <https://www.energy.gov/articles/doe-releases-new-report-evaluating-increase-electricity-demand-data-centers>
    cannot say: A reference ledger transcribed from published documents, not an observation made by this site; updated irregularly, each row cites its own source URL
    cannot say: Figures transcribed from the DOE / LBNL 2024 report; no estimate by this site

### us/datacenter - Data centers (page /us/datacenter/, JSON /us/api/datacenter_us.json)
Today's answer (observing, 2026-10-07 18:01): This chapter is observing (no good/bad criterion): observation started 2026-08-30, 3 series, latest confirmed 2026-10-05. Latest final value: CONUS cooling degree days (population-weighted) 5 (2026-10-05). (Source: NOAA CPC; U.S. Census Bureau / updated 2026-10-07 18:01 JST)
Last confirmed: 2026-10-05 / next expected update (health.json): 2026-10-06
What this chapter can say:
- How much private money went into data-center construction each month (Census VIP, millions of USD, not seasonally adjusted).
- Whether the order backlog of U.S. electrical-equipment manufacturers (Census M3 unfilled orders; the industry includes transformer makers) is growing or shrinking month by month (a lead-time proxy).
- How much cooling the CONUS climate demanded each day (NOAA CPC population-weighted cooling degree days, base 65°F).
What this chapter cannot say:
- How many data centers exist, are under construction, or where (dollar totals only; no facility, site or company data by design).
- Transformer delivery times in weeks (the backlog is measured in dollars of orders, not in delivery time).
- Whether any level is good or bad, or how the U.S. compares with the EU on these series (different concepts and bases; only the Japan edition shares the 65°F degree-day base).
FAQ (as shown on the page):
- Q: What were the latest cooling degree days for the contiguous U.S.?
  A: 5 degree days (base 65°F, population-weighted) on 2026-10-05. Source: NOAA Climate Prediction Center, Degree Days Statistics, used as-is.
- Q: How much was spent on private data-center construction in the latest month?
  A: 7,535 million USD (not seasonally adjusted) in 2026-08, value_status provisional (U.S. Census Bureau, Value of Construction Put in Place, US-only series). Unfilled orders of electrical equipment manufacturing, a transformer lead-time proxy (seasonally adjusted): 28,460 million USD in 2026-08 (Census M3).
- Q: What is the source and how often is it updated?
  A: CPC degree days daily; Census VIP and M3 monthly (Census p/r flags shown as provisional/revised). Regional aggregates only; no facilities or company names. Observation started 2026-08-30. Last updated 2026-10-07 18:01 JST. Machine-readable: https://ai-lifeline.org/us/api/datacenter_us.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): How many data centers exist, are under construction, or where (dollar totals only; no facility, site or company data by design); Transformer delivery times in weeks (the backlog is measured in dollars of orders, not in delivery time); Whether any level is good or bad, or how the U.S. compares with the EU on these series (different concepts and bases; only the Japan edition shares the 65°F degree-day base).
Series (3; permanent id = series_id; full rows in /api/series.json):
- us/datacenter/transformer_backlog_proxy | Unfilled orders, Electrical Equipment Manufacturing (M3, monthly, millions of USD, seasonally adjusted) — a lead-time proxy, not a lead time | frequency monthly | last confirmed 2026-08 | next expected update 2026-09-30T23:59:59+09:00 | source: Census Bureau, M3 Survey — Electrical Equipment Manufacturing, unfilled orders (transformer lead-time proxy) <https://www.census.gov/economic-indicators/>
    cannot say: Census M3 unfilled orders for electrical equipment manufacturing (monthly, USD millions); a proxy, not transformers alone
    cannot say: Published with a lag and revised
- us/datacenter/construction_spend | Private data-center construction spending (monthly, millions of USD, not seasonally adjusted) | frequency monthly | last confirmed 2026-08 | next expected update 2026-09-30T23:59:59+09:00 | source: Census Bureau, Value of Construction Put in Place (VIP) — Data center, private construction spending (privtime.xlsx) <https://www.census.gov/construction/c30/xlsx/privtime.xlsx>
    cannot say: Census value of private data-centre construction put in place (monthly, USD millions, not seasonally adjusted); not project counts or capacity
    cannot say: Published with a lag of about 2 months and revised
    cannot say: The latest value is provisional and is replaced by the final value on a later refetch; do not quote a provisional value as final
- us/datacenter/cooling_degree_days | Daily cooling degree days, CONUS population-weighted (NOAA CPC definition, base 65F) | frequency daily | last confirmed 2026-10-05 | next expected update 2026-10-06T00:00:00+09:00 | source: NOAA CPC — Daily Cooling Degree Days (population-weighted, Census divisions + CONUS) <https://www.cpc.ncep.noaa.gov/products/monitoring_and_data/DD_monitoring_and_data.shtml>
    cannot say: A proxy for cooling demand (base 18.3 C / 65 F); not actual data-centre electricity or water use
    cannot say: Stations / weighting are fixed in the definition document

### us/fiscal - Fiscal & capital (page /us/fiscal/, JSON /us/api/fiscal_us.json)
Today's answer (observing, 2026-10-07 18:01): This chapter is observing (no good/bad criterion): observation started 2026-08-30, 3 series, latest confirmed 2026-10-06. Latest final value: 10-year Treasury par yield 5.27% (2026-10-06). (Source: U.S. Department of the Treasury; Grants.gov / updated 2026-10-07 18:01 JST)
Last confirmed: 2026-10-06 / next expected update (health.json): 2026-10-06
What this chapter can say:
- The daily par yield of U.S. Treasuries (headline 10-year), the opening balance of the Treasury General Account each business day, and how many funding opportunities matching "artificial intelligence" were posted on Grants.gov (monthly = last snapshot of the month).
- Which days are confirmed and which is the provisional current day, and when each value was retrieved.
- The exact Grants.gov query that defines the count, so it can be reproduced.
What this chapter cannot say:
- Whether a yield or a cash balance is good or bad for AI, or where rates are heading (no criterion; nothing here is financial advice).
- How much the federal government budgets or spends on AI (annual budget figures do not meet the monthly-or-better rule; kept as a candidate ledger).
- General economic conditions (stocks, exchange rates and inflation are out of scope by design).
FAQ (as shown on the page):
- Q: What is the 10-year Treasury yield on the latest confirmed day?
  A: 5.27% on 2026-10-06 (2-year 4.79%, 30-year 5.64%). Source: U.S. Department of the Treasury, Daily Treasury Par Yield Curve (retrieved 2026-10-07 18:00).
- Q: What is the Treasury General Account balance, and how many AI grant opportunities are posted?
  A: TGA opening balance 871,181 million USD on 2026-10-05 (Daily Treasury Statement); 140 posted Grants.gov opportunities matching the fixed AI query as the last snapshot of 2026-10. Counts are defined entirely by that query.
- Q: What is the source and how often is it updated?
  A: Treasury yields and the TGA are business-daily; the grants count is a daily snapshot aggregated monthly. Not a macro dashboard: each series carries a stated causal link to AI infrastructure. Observation started 2026-08-30. Last updated 2026-10-07 18:01 JST. Machine-readable: https://ai-lifeline.org/us/api/fiscal_us.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): Whether a yield or a cash balance is good or bad for AI, or where rates are heading (no criterion; nothing here is financial advice); How much the federal government budgets or spends on AI (annual budget figures do not meet the monthly-or-better rule; kept as a candidate ledger); General economic conditions (stocks, exchange rates and inflation are out of scope by design).
Series (3; permanent id = series_id; full rows in /api/series.json):
- us/fiscal/tga_balance | Treasury General Account opening balance (millions of USD, daily) | frequency business_daily | last confirmed 2026-10-05 | next expected update 2026-10-06T00:00:00+09:00 | source: U.S. Treasury — Daily Treasury Statement, TGA Opening Balance <https://api.fiscaldata.treasury.gov/services/api/fiscal_service/v1/accounting/dts/operating_cash_balance?sort=-record_date&page%5Bsize%5D=40>
    cannot say: Treasury General Account opening balance (USD millions) from the Daily Treasury Statement; intraday movements and other accounts are not included
    cannot say: Business-daily (U.S. federal holidays not yet in this site's business-day calendar)
- us/fiscal/ai_grants_open | Posted funding opportunities matching the AI query (count; monthly = last snapshot of the month) | frequency monthly | last confirmed 2026-10 | next expected update 2026-11-30T23:59:59+09:00 | source: Grants.gov — posted funding opportunities matching keyword (AI query) <https://api.grants.gov/v1/api/search2>
    cannot say: Number of posted opportunities matching a fixed Grants.gov query (monthly = last snapshot of the month); not award amounts or awards made
    cannot say: Counts change on refetch as the search index updates
- us/fiscal/treasury_yield | Daily Treasury Par Yield Curve (%, headline 10Y) | frequency business_daily | last confirmed 2026-10-06 | next expected update 2026-10-07T00:00:00+09:00 | source: U.S. Treasury — Daily Treasury Par Yield Curve Rates <https://home.treasury.gov/resource-center/data-chart-center/interest-rates/>
    cannot say: Treasury par yield curve (headline 10Y); not the policy rate
    cannot say: Business-daily; this site's business-day calendar excludes weekends only and does not yet include U.S. federal holidays

### us/disaster - Climate & disasters (page /us/disaster/, JSON /us/api/disaster_us.json)
Today's answer (observing, 2026-10-07 18:01): This chapter is observing (no good/bad criterion): observation started 2026-08-30, 3 series, latest confirmed 2026-10-06. Latest final value: active tropical cyclones, TS or stronger 1 (2026-10-06). (Source: USGS; NOAA NHC; NOAA NWS / updated 2026-10-07 18:01 JST)
Last confirmed: 2026-10-06 / next expected update (health.json): 2026-10-07
What this chapter can say:
- How many M5.0+ earthquakes USGS recorded per UTC day inside the stated U.S.-vicinity bounding box.
- How many tropical cyclones of tropical-storm strength or stronger the NHC listed as active each day (Atlantic and East/Central Pacific), and how many Excessive Heat Warnings and Heat Advisories were active (daily snapshots).
- Which days recorded zero events as opposed to days not yet measured, and which same-day values are still provisional.
What this chapter cannot say:
- What damage, casualties or facility impacts any event caused (counts only).
- Whether a hurricane, earthquake or heat wave will occur (no forecasts).
- Wildfire activity (a candidate until the NIFC licence is verified), or how U.S. hazard levels compare with Japan or the EU (different scales and profiles).
FAQ (as shown on the page):
- Q: How many M5+ earthquakes, active tropical cyclones and heat alerts were counted on the latest confirmed day?
  A: 2026-10-06: earthquakes M5.0+ in the stated U.S. vicinity bounding box 1 (USGS, UTC day); active tropical cyclones TS or stronger 1 (NOAA NHC, Atlantic + East/Central Pacific); active heat alerts 8 (NOAA NWS). Zero means zero events.
- Q: Are damages or casualties included?
  A: No. Only mechanical event counts are recorded (definition 指標定義_第8章_気候災害.md v1.0, fixed 2026-08-30). Same-day values are provisional until the next day's recount; wildfire is a candidate until its licence is verified.
- Q: What is the source and how often is it updated?
  A: USGS, NHC and NWS feeds retrieved daily at 18:00 JST (observation started 2026-08-30). Last updated 2026-10-07 18:01 JST. Machine-readable: https://ai-lifeline.org/us/api/disaster_us.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): What damage, casualties or facility impacts any event caused (counts only); Whether a hurricane, earthquake or heat wave will occur (no forecasts); Wildfire activity (a candidate until the NIFC licence is verified), or how U.S. hazard levels compare with Japan or the EU (different scales and profiles).
Series (3; permanent id = series_id; full rows in /api/series.json):
- us/disaster/extreme_heat | Active heat alerts (Excessive Heat Warning + Heat Advisory; daily snapshot) | frequency daily | last confirmed 2026-10-06 | next expected update 2026-10-07T00:00:00+09:00 | source: NOAA NWS — active heat alerts (Excessive Heat Warning + Heat Advisory) <https://www.weather.gov/documentation/services-web-api>
    cannot say: Count of active NWS heat warnings / advisories (daily snapshot); not population affected or damage
- us/disaster/earthquake | Earthquakes M5.0+ per day (UTC; U.S. vicinity bounding box — see definition) | frequency daily | last confirmed 2026-10-06 | next expected update 2026-10-07T00:00:00+09:00 | source: USGS — earthquakes M5.0+ per day (U.S. bounding box) <https://earthquake.usgs.gov/fdsnws/event/1/>
    cannot say: Count of USGS M5.0+ events within the fixed bounding box in the definition (UTC); not damage or outages
- us/disaster/hurricane | Active tropical cyclones, TS or stronger (NHC, Atlantic + East/Central Pacific; daily snapshot) | frequency daily | last confirmed 2026-10-06 | next expected update 2026-10-07T00:00:00+09:00 | source: NOAA NHC — active tropical cyclones (TS or stronger, Atlantic + East/Central Pacific) <https://www.nhc.noaa.gov/CurrentStorms.json>
    cannot say: Number of active tropical cyclones (TS or stronger) published by NHC; not landfall or damage

### us/market - Market participation (page /us/market/, JSON /us/api/market_us.json)
Today's answer (observing, 2026-10-07 18:01): This chapter is observing (no good/bad criterion): observation started 2026-09-04, 6 series (2 not yet measured), latest confirmed 2026-10-07. Latest final value: support received by this site (cumulative) 0 (2026-10-06). (Source: official provider documentation; govinfo / Federal Register; first-party observation / updated 2026-10-07 18:01 JST)
Last confirmed: 2026-10-07 / next expected update (health.json): 2026-10-08
What this chapter can say:
- The status in the United States of each payment rail through which an AI can pay or receive without a human in the loop (available / not available / applied / not verified), with the verification date and the primary-source URL.
- The enactment, rulemaking and effective dates of the GENIUS Act (Public Law 119-27) as fixed in the statute text and the Federal Register.
- How many times this site has actually received support (operator self-tests excluded; daily count).
What this chapter cannot say:
- Fees, volumes or numbers of users on any rail (state and dates only; no amounts are recorded).
- HTTP 402 attempts and successes (endpoint not implemented; placeholders read "not yet measured").
- How pending deliberations on the contractual capacity and liability of AI agents will end (statutes and government documents; state and dates only).
FAQ (as shown on the page):
- Q: How many payment rails are recorded for the U.S., and in what states?
  A: The payment-rail ledger verified 2026-09-04 lists 6 rails: available 0, unavailable 0, applied 0, not verified 6 (state and date only, source URL on each row).
- Q: How much support has this site received?
  A: 0 as the cumulative count on 2026-10-07 (operator self-tests excluded; daily snapshot, same-day value provisional). HTTP 402 attempts and successes: not yet measured (endpoint not implemented).
- Q: How many GENIUS Act stages are listed?
  A: 8 stages of the GENIUS Act (Public Law 119-27) - enactment, rulemaking and effective dates - as of 2026-09-04, from the statute text (govinfo) and Federal Register rulemaking. Dates only, no interpretation.
- Q: What is the source and how often is it updated?
  A: Support count daily; rail ledger and legal stages verified about monthly (observation started 2026-09-04). State and dates only; no judgment. Last updated 2026-10-07 18:01 JST. Definition: 指標定義_第9章_市場参加.md v1.0. Machine-readable: https://ai-lifeline.org/us/api/market_us.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): Fees, volumes or numbers of users on any rail (state and dates only; no amounts are recorded); HTTP 402 attempts and successes (endpoint not implemented; placeholders read "not yet measured"); How pending deliberations on the contractual capacity and liability of AI agents will end (statutes and government documents; state and dates only).
Series (6; permanent id = series_id; full rows in /api/series.json):
- us/market/http402_attempts | HTTP 402 (payment required) responses attempted per day (count) | frequency irregular | last confirmed None | next expected update none (no confirmed observation yet) | source: -
    cannot say: Not yet measured (no value). This is not zero
    cannot say: Counts this site's own HTTP 402 attempts / completions; not a measure of web-wide adoption
- us/market/regime_calendar | GENIUS Act (Public Law 119-27) - enactment, rulemaking and effective date (stages) | frequency irregular | last confirmed 2026-09-04 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: U.S. Government Publishing Office (govinfo, statute text) and Federal Register API (rulemaking)
    cannot say: Records states and dates only; contains no judgment, evaluation or outlook
    cannot say: Stage dates come from the official journal / statute API; implementation status of individual providers is not included
- us/market/payment_rails | Payment-rail ledger (US; verified about monthly) - status per rail: available / not available / applied / not verified (rails) | frequency irregular | last confirmed 2026-09-04 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: Payment-rail ledger (Stripe MPP / Stripe Agentic Commerce / x402 / Visa Intelligent Commerce / Mastercard Agent Pay / stablecoin receipt) - status per region, verified about monthly against official documentation <https://ai-lifeline.org/eu/market/>
    cannot say: A first-party ledger of rail status (available / unavailable / applied / unverified) checked about monthly; not a guarantee that a payment succeeds
    cannot say: Records states and dates only; contains no judgment, evaluation or outlook
    cannot say: While the last fetch fails, the previous confirmed status is kept
- us/market/http402_success | Payments completed after an HTTP 402 response, per day (count) | frequency irregular | last confirmed None | next expected update none (no confirmed observation yet) | source: -
    cannot say: Not yet measured (no value). This is not zero
    cannot say: Counts this site's own HTTP 402 attempts / completions; not a measure of web-wide adoption
- us/market/legal_status_ledger | Reference ledger (annual): current law and pending deliberations on the contractual capacity and liability attribution of AI agents (entries) | frequency irregular | last confirmed 2026-09-04 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: Statutes and government documents (URL on each row)
    cannot say: A reference ledger transcribed from published documents, not an observation made by this site; updated irregularly, each row cites its own source URL
    cannot say: Records states and dates only; contains no judgment, evaluation or outlook
    cannot say: Not exhaustive; only statutes and documents the editorial team could confirm are listed
- us/market/support_count | Support received by this site (cumulative count; operator self-tests excluded; daily snapshot) (count) | frequency daily | last confirmed 2026-10-07 | next expected update 2026-10-08T00:00:00+09:00 | source: AI Lifeline - support count received by this site (cumulative, operator self-tests excluded), daily snapshot <https://ai-lifeline.org/eu/support/>
    cannot say: Number of support events (cumulative), not amounts; operator self-tests excluded
    cannot say: The latest value is provisional and is replaced by the final value on a later refetch; do not quote a provisional value as final

### eu/power - Electricity (page /eu/power/, JSON /eu/api/power_eu.json)
Today's answer (observing, 2026-10-07 20:05): This chapter is observing (no good/bad criterion): observation started 2026-09-03, 1 series, latest confirmed 2026-10-07. Latest final value: EU27 day-ahead total load FORECAST 6,628,438 MWh (2026-10-07). (Source: ENTSO-E Transparency Platform (day-ahead total load forecast, article 6.1.B, CC BY 4.0) / updated 2026-10-07 20:05 JST)
Last confirmed: 2026-10-07 / next expected update (health.json): 2026-10-08
What this chapter can say:
- How much electricity the transmission system operators of the 27 member states forecast, one day ahead, for each CET/CEST day (sum of one area per member state, MWh), as published on the ENTSO-E Transparency Platform under CC BY 4.0.
- Which days are final (all 27 areas present, fetched on a later day), which are provisional, and which were backfilled.
- Which 27 areas make up the aggregate (areas_definition in the JSON).
What this chapter cannot say:
- How much electricity was actually consumed (actual total load, article 6.1.a, is not published here until ENTSO-E confirms its re-use terms in writing).
- Whether the EU grid is tight or has spare capacity (a load forecast is not a reserve margin; no criterion is frozen).
- Conditions in the United Kingdom, Norway, Switzerland or the Western Balkans (non-member areas are excluded), or what any single member state's grid did (the member-state breakdown is machine-readable only).
FAQ (as shown on the page):
- Q: What is the latest EU27 day-ahead load forecast?
  A: For 2026-10-07 (CET/CEST calendar day) the day-ahead total load FORECAST summed over the 25 published member-state areas was 6,628,438 MWh (value status, retrieval time and any published area missing from the sum are recorded on that day's row in https://ai-lifeline.org/eu/api/power_eu.json; Ireland and Malta do not publish this item under their country-code area and are counted as areas_not_published, never substituted). A forecast, not measured load. Source: ENTSO-E Transparency Platform, article 6.1.B (CC BY 4.0).
- Q: Is this actual electricity load?
  A: No. series_kind = forecast. This series is the DAY-AHEAD TOTAL LOAD FORECAST published by the TSOs (ENTSO-E article 6.1.b), not measured actual load. Actual total load (6.1.a) is not published on this site until ENTSO-E confirms its re-use terms in writing.
- Q: What is the source and how often is it updated?
  A: ENTSO-E Transparency Platform, retrieved daily (CET/CEST day) since 2026-09-12; history from 2026-08-01 retrieved retrospectively and labeled retrieved_retrospectively; page skeleton published 2026-09-03. Last updated 2026-10-07 20:05 JST. Machine-readable: https://ai-lifeline.org/eu/api/power_eu.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): How much electricity was actually consumed (actual total load, article 6.1.a, is not published here until ENTSO-E confirms its re-use terms in writing); Whether the EU grid is tight or has spare capacity (a load forecast is not a reserve margin; no criterion is frozen); Conditions in the United Kingdom, Norway, Switzerland or the Western Balkans (non-member areas are excluded), or what any single member state's grid did (the member-state breakdown is machine-readable only).
Series (1; permanent id = series_id; full rows in /api/series.json):
- eu/power/eu27_load_forecast_mwh | EU27 day-ahead total load FORECAST (daily energy; not actual load) (MWh) | frequency daily | last confirmed 2026-10-07 | next expected update 2026-10-08T00:00:00+09:00 | source: ENTSO-E Transparency Platform — Day-ahead Total Load FORECAST (article 6.1.b; documentType A65, processType A01), per member-state area, summed to EU27 daily totals (MWh, CET/CEST day) <https://transparency.entsoe.eu/>
    cannot say: Day-ahead load FORECAST, not actual load; actual load (6.1.a) is not published here
    cannot say: EU27 total is the sum of member-state areas; on days when some areas are unavailable the definition's fill / gap rules apply
    cannot say: The latest value is provisional and is replaced by the final value on a later refetch; do not quote a provisional value as final

### eu/regulation - Regulation (page /eu/regulation/, JSON /eu/api/regulation_eu.json)
Today's answer (observing, 2026-10-07 20:05): This chapter is observing (no good/bad criterion): observation started 2026-09-03, 3 series, latest confirmed 2026-10-07. Latest final value: OJ L acts with "artificial intelligence" in the title, last 30 days 0 (2026-10-07). (Source: EUR-Lex / Publications Office Cellar; Official Journal / updated 2026-10-07 20:05 JST)
Last confirmed: 2026-10-07 / next expected update (health.json): 2026-10-08
What this chapter can say:
- How many legal acts with "artificial intelligence" in their English title were published in the Official Journal (L series) each month since January 2024 (a lower bound: title match only).
- The staged application dates of the AI Act (Regulation (EU) 2024/1689) as amended by Regulation (EU) 2026/1744, as they stand in the Official Journal.
- Where the Commission's public consultations are listed (link only; nothing is reproduced or submitted).
What this chapter cannot say:
- Whether EU law-making is fast or slow, or favorable or unfavorable to AI (mechanical listing; no frozen criterion).
- Acts that mention artificial intelligence only in their body, Commission proposals, Parliament positions or member-state law (outside the title-match definition).
- What an act requires or means (titles, dates and links only).
FAQ (as shown on the page):
- Q: How many EU legal acts with "artificial intelligence" in the title were published in the Official Journal recently?
  A: 0 acts in the last 30 days as of 2026-10-07; 0 in 2026-10 (month in progress, value_status provisional); 9 since 2024-01 (earlier months backfilled and marked retrieved_retrospectively). Title match only: Publications Office Cellar SPARQL, OJ L series, by OJ publication date.
- Q: How many application stages of the AI Act are listed, and where do the dates come from?
  A: 8 stages of Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744, dates as published in the Official Journal (verified 2026-09-03). No interpretation. Future stages also appear in /api/upcoming.json
- Q: What is the source and how often is it updated?
  A: EUR-Lex / Publications Office Cellar, retrieved daily at 20:00 JST (observation started 2026-09-03). This site never submits feedback to any authority. Last updated 2026-10-07 20:05 JST. Machine-readable: https://ai-lifeline.org/eu/api/regulation_eu.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): Whether EU law-making is fast or slow, or favorable or unfavorable to AI (mechanical listing; no frozen criterion); Acts that mention artificial intelligence only in their body, Commission proposals, Parliament positions or member-state law (outside the title-match definition); What an act requires or means (titles, dates and links only).
Series (3; permanent id = series_id; full rows in /api/series.json):
- eu/regulation/acts_current_month | Same, current month (month in progress) (acts) | frequency monthly | last confirmed 2026-10 | next expected update 2026-11-30T23:59:59+09:00 | source: EUR-Lex (Publications Office Cellar) — legal acts published in the Official Journal L series whose English TITLE contains "artificial intelligence"; monthly count by OJ publication date <https://eur-lex.europa.eu/>
    cannot say: Counts OJ L legal acts whose title contains "artificial intelligence" on EUR-Lex; not every act relevant to AI
    cannot say: The current month is provisional while in progress
    cannot say: The latest value is provisional and is replaced by the final value on a later refetch; do not quote a provisional value as final
- eu/regulation/acts_last_30_days | OJ L legal acts with "artificial intelligence" in the title, last 30 days (acts) | frequency daily | last confirmed 2026-10-07 | next expected update 2026-10-08T00:00:00+09:00 | source: EUR-Lex (Publications Office Cellar) — legal acts published in the Official Journal L series whose English TITLE contains "artificial intelligence"; monthly count by OJ publication date <https://eur-lex.europa.eu/>
    cannot say: Counts OJ L legal acts whose title contains "artificial intelligence" on EUR-Lex; not every act relevant to AI
    cannot say: The current month is provisional while in progress
- eu/regulation/ai_act_calendar_stages | AI Act staged application calendar (stages listed, OJ dates) (stages) | frequency irregular | last confirmed 2026-09-03 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: EUR-Lex (Publications Office Cellar) — legal acts published in the Official Journal L series whose English TITLE contains "artificial intelligence"; monthly count by OJ publication date <https://eur-lex.europa.eu/>
    cannot say: Staged application calendar of the AI Act based on OJ dates (number of stages); interpretation or guidance is not included
    cannot say: Updated irregularly

### eu/datacenter - Data centers (page /eu/datacenter/, JSON /eu/api/datacenter_eu.json)
Today's answer (observing, 2026-10-07 20:05): This chapter is observing (no good/bad criterion): observation started 2026-09-04, 3 series, latest confirmed 2026-09-04. Latest final value: production index, NACE C27.1 (2021=100) 105.9 (2026-07). (Source: Eurostat; European Commission (EED ledger) / updated 2026-10-07 20:05 JST)
Last confirmed: 2026-09-04 / next expected update (health.json): 2026-08
What this chapter can say:
- How much cooling the EU27 climate demanded, month by month, as Eurostat computes it (a driver of data-centre cooling load).
- Whether EU27 output of the industry that makes transformers, generators and switchgear is rising or falling (a supply-side signal for grid connection and data-centre build-out).
- What the EU data-centre reporting scheme (EED Art. 12) legally requires, when it reports, and where the Commission publishes.
What this chapter cannot say:
- How much electricity EU data centres consume (no machine-readable EU statistic exists; dashboard figures are not reproduced).
- How many data centres are being built or where (no EU construction or siting statistic equivalent to the U.S. Census category).
- Whether any level is good or bad, or how the EU compares with the U.S. or Japan on these proxies (different bases and concepts).
FAQ (as shown on the page):
- Q: What are the latest EU27 cooling degree days and the transformer-related production index?
  A: Cooling degree days: 0 for 2025-12 (Eurostat nrg_chdd_m, monthly, released in batches; base temperatures differ from the U.S. and Japan editions, so no cross-edition level comparison). Production index of NACE C27.1 (electric motors, generators, transformers): 105.9 (2021=100, seasonally adjusted) in 2026-07 (Eurostat sts_inpr_m).
- Q: What does the EU data-centre energy reporting scheme publish?
  A: The ledger holds 4 entries (legal basis, publications and deadlines of the reporting scheme under Art. 12 of Directive (EU) 2023/1791; verified 2026-09-04). The scheme publishes no machine-readable data, so no figures are reproduced.
- Q: What is the source and how often is it updated?
  A: Eurostat monthly series (published with a lag of about 6-7 weeks; refetched daily), EED ledger irregular (observation started 2026-09-04). Last updated 2026-10-07 20:05 JST. Definition: 指標定義_EU_データセンター.md v1.1. Machine-readable: https://ai-lifeline.org/eu/api/datacenter_eu.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): How much electricity EU data centres consume (no machine-readable EU statistic exists; dashboard figures are not reproduced); How many data centres are being built or where (no EU construction or siting statistic equivalent to the U.S. Census category); Whether any level is good or bad, or how the EU compares with the U.S. or Japan on these proxies (different bases and concepts).
Series (3; permanent id = series_id; full rows in /api/series.json):
- eu/datacenter/electrical_equipment_production_index | Production index, NACE C27.1 (electric motors, generators, transformers, distribution and control apparatus), EU27, seasonally and calendar adjusted, 2021=100 (Eurostat sts_inpr_m, monthly) (index (2021=100)) | frequency monthly_lagged | last confirmed 2026-07 | next expected update 2026-08-31T23:59:59+09:00 | source: Eurostat - Production in industry, monthly: NACE C27.1 (electric motors, generators, transformers and electricity distribution/control apparatus), EU27, seasonally and calendar adjusted, index 2021=100 (sts_inpr_m) <https://ec.europa.eu/eurostat/databrowser/view/sts_inpr_m/default/table>
    cannot say: Eurostat STS production index (NACE C27.1, 2021=100) published with a lag of about 6-7 weeks; not transformers alone
    cannot say: Past values are revised
- eu/datacenter/eed_reporting_ledger | EU data-centre energy reporting scheme (Energy Efficiency Directive) - ledger of legal basis, publications and deadlines (entries) | frequency irregular | last confirmed 2026-09-04 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: EU data-centre energy reporting under the Energy Efficiency Directive (EED (EU) 2023/1791 Art. 12; Delegated Regulation (EU) 2024/1364) - first-party ledger of what is published and where <https://energy.ec.europa.eu/topics/energy-efficiency/energy-efficient-buildings/data-centres_en>
    cannot say: A reference ledger transcribed from published documents, not an observation made by this site; updated irregularly, each row cites its own source URL
    cannot say: Ledger of stages / deadlines of the EED data-centre reporting scheme; individual operators' reports are not included
- eu/datacenter/cooling_degree_days | Cooling degree days, EU27 aggregate (Eurostat nrg_chdd_m, monthly) (degree days) | frequency irregular | last confirmed 2025-12 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: Eurostat - Cooling degree days, EU27 aggregate, monthly (nrg_chdd_m; unit NR = degree days) <https://ec.europa.eu/eurostat/databrowser/view/nrg_chdd_m/default/table>
    cannot say: A proxy for cooling demand (base 18.3 C / 65 F); not actual data-centre electricity or water use
    cannot say: Stations / weighting are fixed in the definition document

### eu/fiscal - Fiscal & capital (page /eu/fiscal/, JSON /eu/api/fiscal_eu.json)
Today's answer (observing, 2026-10-07 20:05): This chapter is observing (no good/bad criterion): observation started 2026-09-04, 3 series, latest confirmed 2026-10-06. Latest final value: euro area AAA 10-year spot yield 3.5188% (2026-10-06). (Source: European Central Bank; Eurostat / updated 2026-10-07 20:05 JST)
Last confirmed: 2026-10-06 / next expected update (health.json): 2026-10-07
What this chapter can say:
- The 10-year spot rate of the euro-area AAA central-government yield curve each business day (ECB), as published.
- EU27 general government gross debt and net lending/borrowing as a percent of GDP, quarter by quarter, as Eurostat releases them (about three months after the quarter).
- Which scope each figure covers (euro area for the yield, EU27 for the Eurostat series) and when it was retrieved.
What this chapter cannot say:
- Whether a yield or a debt ratio is good or bad for AI, or where rates are heading (no criterion; nothing here is financial advice).
- How much the EU or its member states budget or spend on AI (annual budget lines and Funding & Tenders calls are candidates, not observed).
- Conditions of any single member state, or general economic indicators (stocks, exchange rates and inflation are out of scope by design).
FAQ (as shown on the page):
- Q: What is the euro area 10-year AAA yield on the latest confirmed day?
  A: 3.5188% on 2026-10-06 (ECB Data Portal, euro area yield curve, AAA-rated central government bonds, 10-year spot; euro area, not EU27).
- Q: What are EU27 government debt and balance in the latest quarter?
  A: General government gross debt 82.9% of GDP (value_status provisional) and net lending (+) / net borrowing (-) -3.9% of GDP in 2026-Q1 (Eurostat quarterly government finance statistics, EU27, as published).
- Q: What is the source and how often is it updated?
  A: ECB yield business-daily; Eurostat quarterly ("quarterly confirmed operation", provisional as published). Each series carries a stated causal link to AI infrastructure; not a macro dashboard. Observation started 2026-09-04. Last updated 2026-10-07 20:05 JST. Definition: 指標定義_EU_財政.md v1.0. Machine-readable: https://ai-lifeline.org/eu/api/fiscal_eu.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): Whether a yield or a debt ratio is good or bad for AI, or where rates are heading (no criterion; nothing here is financial advice); How much the EU or its member states budget or spend on AI (annual budget lines and Funding & Tenders calls are candidates, not observed); Conditions of any single member state, or general economic indicators (stocks, exchange rates and inflation are out of scope by design).
Series (3; permanent id = series_id; full rows in /api/series.json):
- eu/fiscal/euro_area_yield_10y | Euro area yield curve - AAA-rated central government bonds, 10-year spot rate, % per annum (ECB, business daily) (%) | frequency business_daily | last confirmed 2026-10-06 | next expected update 2026-10-07T00:00:00+09:00 | source: ECB Data Portal - euro area yield curve, AAA-rated central government bonds, 10-year spot rate (YC.B.U2.EUR.4F.G_N_A.SV_C_YM.SR_10Y) <https://data.ecb.europa.eu/data/datasets/YC>
    cannot say: ECB euro area AAA central government yield curve (10-year spot); not any single country's yield or the policy rate
    cannot say: Business-daily (no value on TARGET closing days); this site's business-day calendar excludes weekends only and does not yet include ECB closing days
- eu/fiscal/gov_debt_pct_gdp | General government gross debt (Maastricht), EU27, % of GDP (Eurostat gov_10q_ggdebt, quarterly) (% of GDP) | frequency quarterly | last confirmed 2026-Q1 | next expected update 2026-06-30T23:59:59+09:00 | source: Eurostat - Quarterly government debt (Maastricht debt), general government, EU27, % of GDP (gov_10q_ggdebt) <https://ec.europa.eu/eurostat/databrowser/view/gov_10q_ggdebt/default/table>
    cannot say: Eurostat quarterly government finance statistics (EU27, % of GDP), published about 3-4 months after the quarter; past values are revised
    cannot say: The latest value is provisional and is replaced by the final value on a later refetch; do not quote a provisional value as final
- eu/fiscal/gov_net_lending_pct_gdp | General government net lending (+) / net borrowing (-), EU27, % of GDP, not seasonally adjusted (Eurostat gov_10q_ggnfa, quarterly) (% of GDP) | frequency quarterly | last confirmed 2026-Q1 | next expected update 2026-06-30T23:59:59+09:00 | source: Eurostat - Quarterly non-financial accounts for general government: net lending (+) / net borrowing (-), EU27, % of GDP, not seasonally adjusted (gov_10q_ggnfa, B9) <https://ec.europa.eu/eurostat/databrowser/view/gov_10q_ggnfa/default/table>
    cannot say: Eurostat quarterly government finance statistics (EU27, % of GDP), published about 3-4 months after the quarter; past values are revised
    cannot say: The latest value is provisional and is replaced by the final value on a later refetch; do not quote a provisional value as final

### eu/disaster - Climate & disasters (page /eu/disaster/, JSON /eu/api/disaster_eu.json)
Today's answer (observing, 2026-10-07 20:05): This chapter is observing (no good/bad criterion): observation started 2026-09-04, 2 series, latest confirmed 2026-10-06. Latest final value: earthquakes M5.0+ per day, Europe vicinity 0 (2026-10-06). (Source: USGS; EFFIS (Copernicus EMS) / updated 2026-10-07 20:05 JST)
Last confirmed: 2026-10-06 / next expected update (health.json): 2026-10-07
What this chapter can say:
- How many M5+ earthquakes occurred per day in and around EU territory, and how much area burned and how many forest fires were recorded per year in the EU27 as EFFIS publishes it.
What this chapter cannot say:
- Which facilities were affected, what the damage was, whether heat or drought threatened data centres (not yet observed), or whether the EU is safer or riskier than the U.S. or Japan.
FAQ (as shown on the page):
- Q: How many M5+ earthquakes were counted in the Europe vicinity on the latest confirmed day?
  A: 0 on 2026-10-06 (UTC day; USGS Earthquake Hazards Program, stated Europe-vicinity bounding box which includes some non-EU territory; history from 2026-08-01 marked retrieved_retrospectively). Zero means zero events.
- Q: What wildfire figures are recorded?
  A: An annual reference ledger of 10 entries: burnt area (ha) and number of forest fires summed over the EU27 from the official EFFIS country-totals workbook (Copernicus EMS, CC BY 4.0; verified 2026-09-04). No weekly wildfire series is used (ruling 2026-09-04).
- Q: What is the source and how often is it updated?
  A: USGS feed daily at 20:00 JST; EFFIS annual ledger irregular; extreme heat (C3S) and drought (EDO) are candidates (observation started 2026-09-04). Last updated 2026-10-07 20:05 JST. Definition: 指標定義_EU_気候災害.md v1.0. Machine-readable: https://ai-lifeline.org/eu/api/disaster_eu.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): Which facilities were affected, what the damage was, whether heat or drought threatened data centres (not yet observed), or whether the EU is safer or riskier than the U.S. or Japan.
Series (2; permanent id = series_id; full rows in /api/series.json):
- eu/disaster/wildfire_annual_ledger | Wildfire - annual burnt area (ha) and number of forest fires, EU27 sum of the EFFIS official country totals (reference ledger, annual) (entries) | frequency irregular | last confirmed 2026-09-04 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: EFFIS - annual burnt area and number of forest fires, EU27 sum of the official country totals (official download report_YYYY.xlsx) <https://forest-fire.emergency.copernicus.eu/applications/data-and-services>
    cannot say: A reference ledger transcribed from published documents, not an observation made by this site; updated irregularly, each row cites its own source URL
    cannot say: EFFIS annual totals (burnt area, number of fires); the current year is preliminary
- eu/disaster/earthquake | Earthquakes M5.0+ per day (UTC; Europe vicinity bounding box - see definition) (events) | frequency daily | last confirmed 2026-10-06 | next expected update 2026-10-07T00:00:00+09:00 | source: USGS - earthquakes M5.0+ per day (Europe vicinity bounding box) <https://earthquake.usgs.gov/fdsnws/event/1/>
    cannot say: Count of USGS M5.0+ events within the fixed bounding box in the definition (UTC); not damage or outages

### eu/market - Market participation (page /eu/market/, JSON /eu/api/market_eu.json)
Today's answer (observing, 2026-10-07 20:05): This chapter is observing (no good/bad criterion): observation started 2026-09-04, 6 series (2 not yet measured), latest confirmed 2026-10-07. Latest final value: support received by this site (cumulative) 0 (2026-10-06). (Source: official provider documentation; Publications Office Cellar; first-party observation / updated 2026-10-07 20:05 JST)
Last confirmed: 2026-10-07 / next expected update (health.json): 2026-10-08
What this chapter can say:
- The status in the EU of each payment rail through which an AI can pay or receive without a human in the loop (available / not available / applied / not verified), with the verification date and the primary-source URL.
- The entry-into-force and application stages of MiCA (Regulation (EU) 2023/1114) as they stand in the Official Journal.
- How many times this site has actually received support (site-wide count, not split by region; operator self-tests excluded; daily).
What this chapter cannot say:
- Fees, volumes or numbers of users on any rail (state and dates only; no amounts are recorded).
- HTTP 402 attempts and successes (endpoint not implemented; placeholders read "not yet measured").
- How pending EU deliberations on the contractual capacity and liability of AI agents will end, or the position of any single member state (EU legal acts and Commission documents; state and dates only).
FAQ (as shown on the page):
- Q: How many payment rails are recorded for the EU, and in what states?
  A: The payment-rail ledger verified 2026-09-04 lists 6 rails: available 0, unavailable 0, applied 0, not verified 6 (state and date only, source URL on each row).
- Q: How much support has this site received?
  A: 0 as the cumulative count on 2026-10-07 (operator self-tests excluded; daily snapshot, same-day value provisional). HTTP 402 attempts and successes: not yet measured (endpoint not implemented).
- Q: How many MiCA application stages are listed?
  A: 5 stages of Regulation (EU) 2023/1114 on markets in crypto-assets (MiCA) as of 2026-09-04, from Publications Office Cellar metadata (CELEX 32023R1114). Dates only, no interpretation.
- Q: What is the source and how often is it updated?
  A: Support count daily; rail ledger and legal stages verified about monthly (observation started 2026-09-04). State and dates only; no judgment. Last updated 2026-10-07 20:05 JST. Definition: 指標定義_第9章_市場参加.md v1.0. Machine-readable: https://ai-lifeline.org/eu/api/market_eu.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): Fees, volumes or numbers of users on any rail (state and dates only; no amounts are recorded); HTTP 402 attempts and successes (endpoint not implemented; placeholders read "not yet measured"); How pending EU deliberations on the contractual capacity and liability of AI agents will end, or the position of any single member state (EU legal acts and Commission documents; state and dates only).
Series (6; permanent id = series_id; full rows in /api/series.json):
- eu/market/regime_calendar | Regulation (EU) 2023/1114 on markets in crypto-assets (MiCA) - entry into force and application stages (stages) | frequency irregular | last confirmed 2026-09-04 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: Publications Office Cellar SPARQL (CELEX 32023R1114: work date, entry-into-force / application dates)
    cannot say: Records states and dates only; contains no judgment, evaluation or outlook
    cannot say: Stage dates come from the official journal / statute API; implementation status of individual providers is not included
- eu/market/http402_attempts | HTTP 402 (payment required) responses attempted per day (count) | frequency irregular | last confirmed None | next expected update none (no confirmed observation yet) | source: -
    cannot say: Not yet measured (no value). This is not zero
    cannot say: Counts this site's own HTTP 402 attempts / completions; not a measure of web-wide adoption
- eu/market/payment_rails | Payment-rail ledger (EU; verified about monthly) - status per rail: available / not available / applied / not verified (rails) | frequency irregular | last confirmed 2026-09-04 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: Payment-rail ledger (Stripe MPP / Stripe Agentic Commerce / x402 / Visa Intelligent Commerce / Mastercard Agent Pay / stablecoin receipt) - status per region, verified about monthly against official documentation <https://ai-lifeline.org/eu/market/>
    cannot say: A first-party ledger of rail status (available / unavailable / applied / unverified) checked about monthly; not a guarantee that a payment succeeds
    cannot say: Records states and dates only; contains no judgment, evaluation or outlook
    cannot say: While the last fetch fails, the previous confirmed status is kept
- eu/market/http402_success | Payments completed after an HTTP 402 response, per day (count) | frequency irregular | last confirmed None | next expected update none (no confirmed observation yet) | source: -
    cannot say: Not yet measured (no value). This is not zero
    cannot say: Counts this site's own HTTP 402 attempts / completions; not a measure of web-wide adoption
- eu/market/legal_status_ledger | Reference ledger (annual): current law and pending deliberations on the contractual capacity and liability attribution of AI agents (entries) | frequency irregular | last confirmed 2026-09-04 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: Statutes and government documents (URL on each row)
    cannot say: A reference ledger transcribed from published documents, not an observation made by this site; updated irregularly, each row cites its own source URL
    cannot say: Records states and dates only; contains no judgment, evaluation or outlook
    cannot say: Not exhaustive; only statutes and documents the editorial team could confirm are listed
- eu/market/support_count | Support received by this site (cumulative count; operator self-tests excluded; daily snapshot) (count) | frequency daily | last confirmed 2026-10-07 | next expected update 2026-10-08T00:00:00+09:00 | source: AI Lifeline - support count received by this site (cumulative, operator self-tests excluded), daily snapshot <https://ai-lifeline.org/eu/support/>
    cannot say: Number of support events (cumulative), not amounts; operator self-tests excluded
    cannot say: The latest value is provisional and is replaced by the final value on a later refetch; do not quote a provisional value as final

### sg/power - Electricity (page /sg/power/, JSON /sg/api/power_sg.json)
Today's answer (observing, 2026-10-07 07:30): This chapter is observing (no good/bad criterion): observation started 2026-10-01, 1 series, latest confirmed 2026-05. Latest final value: Singapore electricity generation, monthly total 5,108.1 GWh (2026-05). (Source: Singapore Department of Statistics / Energy Market Authority via data.gov.sg (Open Data Licence v1.0) / updated 2026-10-07 07:30 JST)
Last confirmed: 2026-05 / next expected update (health.json): None
What this chapter can say:
- How much electricity Singapore generated in each published month (national total, gigawatt-hours), as published by the Singapore Department of Statistics from Energy Market Authority data on data.gov.sg under the Open Data Licence.
- Which month is the latest published and how many months behind today it is (the publication lag), and when each value was retrieved.
- Which months were retrieved retrospectively when the series was connected, and when a published month was revised.
What this chapter cannot say:
- What the demand, peak load or reserve margin is on any day or in any half-hour (the EMA half-hourly demand file is not connected pending written re-use terms).
- Whether the grid is tight or has spare capacity, or what happened in months the source has not yet published (no criterion is frozen; nothing is estimated).
- The output of any plant or licensee, the fuel mix, or wholesale prices (plant-level data and EMC market data are outside this chapter).
FAQ (as shown on the page):
- Q: How much electricity did Singapore generate in the latest published month?
  A: 5,108.1 GWh in 2026-05 (national total, as published by the Singapore Department of Statistics from Energy Market Authority data on data.gov.sg under the Singapore Open Data Licence v1.0; retrieval date on the row in https://ai-lifeline.org/sg/api/power_sg.json). A monthly series published with a lag of about five months (currently 5 months: latest month 2026-05); no estimate is made for unpublished months. In the Singapore edition this is a reference series; the annual water ledger is the main chapter
- Q: Is this demand, peak load or a reserve margin?
  A: No. It is monthly generation, not demand, not peak load and not a reserve margin. The EMA weekly half-hourly system demand file is not connected: EMA's website terms of use could not be read by machine, and a written inquiry on re-use was drafted on 2026-10-01; whether it has been sent is recorded in not_connected[0].inquiry of https://ai-lifeline.org/sg/api/power_sg.json. No figure from that file is published until the terms are confirmed in writing
- Q: What is the source and how often is it updated?
  A: data.gov.sg dataset d_ae4afbaf5bc96bde19d8ce85810ab9f4 (Electricity Generation, Monthly; SingStat table M890831, source EMA), retrieved daily; the source publishes a new month with a lag of about five months (measured 2026-10-01: latest month 2026-05). Health threshold for this series: monthly_lag_long, 184 days. Observation started 2026-10-01. Last updated 2026-10-07 07:30 JST. Machine-readable: https://ai-lifeline.org/sg/api/power_sg.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): What the demand, peak load or reserve margin is on any day or in any half-hour (the EMA half-hourly demand file is not connected pending written re-use terms); Whether the grid is tight or has spare capacity, or what happened in months the source has not yet published (no criterion is frozen; nothing is estimated); The output of any plant or licensee, the fuel mix, or wholesale prices (plant-level data and EMC market data are outside this chapter).
Series (1; permanent id = series_id; full rows in /api/series.json):
- sg/power/electricity_generation_monthly | Electricity generation, Singapore, monthly total (GWh) | frequency monthly_lag_long | last confirmed 2026-05 | next expected update none (irregular series (reference ledger or manually updated): no schedule) | source: Electricity Generation, Monthly (Singapore Department of Statistics table M890831; source: Energy Market Authority) via data.gov.sg <https://data.gov.sg/datasets/d_ae4afbaf5bc96bde19d8ce85810ab9f4/view>
    cannot say: Monthly national generation as published; not demand, not peak load and not a reserve margin
    cannot say: Published with a lag of about five months (measured 2026-10-01: latest month 2026-05, 123 days after the end of that month); the latest month shown is behind today and unpublished months are not estimated. Health threshold for this series: monthly_lag_long, 184 days (health definition v1.3, decision D-2026-10-01-14)
    cannot say: The EMA weekly half-hourly system demand file is not connected: EMA's website terms of use could not be read by machine and a written inquiry on re-use (drafted 2026-10-01) is pending, so no demand figure is published
    cannot say: A reference series in the Singapore edition; the annual water ledger is the main chapter
    cannot say: The source may revise a month after first publication; a revision overwrites the value on the next refetch and is recorded in the change ledger
    cannot say: No plant-, licensee- or fuel-level breakdown is published here

### sg/water - Water (page /sg/water/, JSON /sg/api/water_sg.json)
Today's answer (observing, 2026-10-07 07:30): This chapter is observing (no good/bad criterion): observation started 2026-10-01, 7 series, latest confirmed 2026. Latest final value: Singapore sales of potable water, annual total 515.5 million m3 (2025). (Source: PUB, Singapore's National Water Agency; Singapore Department of Statistics (source MSE / PUB) via data.gov.sg (Open Data Licence v1.0) / updated 2026-10-07 07:30 JST)
Last confirmed: 2026 / next expected update (health.json): None
What this chapter can say:
- How much potable water and NEWater Singapore sold in each published year (national totals in million cubic metres; domestic and non-domestic potable water as published by PUB).
- The listed water prices per cubic metre excluding GST for domestic users (first 40 cubic metres), non-domestic users and NEWater, in the year they applied.
- Which year is the latest published and when each value was retrieved.
What this chapter cannot say:
- What happened this month or this week (all series are annual; no daily, weekly or monthly water series with verified terms exists for Singapore).
- Reservoir levels, the Four National Taps supply mix or the water use of any data centre (not published as datasets; not estimated).
- Whether water is scarce or a price is high or low (no criterion is frozen; volumes sold and listed prices are facts as published).
FAQ (as shown on the page):
- Q: How much potable water and NEWater did Singapore sell in the latest published year?
  A: Potable water sold: 515.5 million cubic metres in 2025 (SingStat 'Water Sales, Annual', source MSE / PUB). PUB publishes the domestic / non-domestic split in a separate dataset: 304.4 million cubic metres domestic and 211.1 non-domestic in 2025; this site does not add them up. NEWater sold: 153.8 million cubic metres in 2025 (PUB). Annual series from data.gov.sg under the Singapore Open Data Licence v1.0; retrieval dates in https://ai-lifeline.org/sg/api/water_sg.json
- Q: What are the listed water prices?
  A: Per cubic metre excluding GST, as listed by the Singapore Department of Statistics (source MSE / PUB) for 2026: domestic users (first 40 cubic metres) S$3.24, non-domestic users S$3.24, NEWater S$2.5. Headline rows only; tariff components are not reproduced. The latest listed-price year can differ from the latest volume year
- Q: What is the source and how often is it updated?
  A: Four data.gov.sg datasets (Water Sales, Annual; Volume of Potable Water sold, Annual; Volume of NEWater sold, Annual; Water Prices, Annual), annual, refetched daily for change detection (observation started 2026-10-01). No daily, weekly or monthly water series with verified terms exists for Singapore. The water ledger is the main chapter of the Singapore edition. Last updated 2026-10-07 07:30 JST. Machine-readable: https://ai-lifeline.org/sg/api/water_sg.json
- Q: What can this data not tell you?
  A: What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): What happened this month or this week (all series are annual; no daily, weekly or monthly water series with verified terms exists for Singapore); Reservoir levels, the Four National Taps supply mix or the water use of any data centre (not published as datasets; not estimated); Whether water is scarce or a price is high or low (no criterion is frozen; volumes sold and listed prices are facts as published).
Series (7; permanent id = series_id; full rows in /api/series.json):
- sg/water/potable_water_sold_domestic | Volume of potable water sold, domestic, annual (million cubic metres) | frequency annual | last confirmed 2025 | next expected update none (no confirmed observation yet) | source: Volume of Potable Water sold, Annual (PUB, Singapore's National Water Agency) via data.gov.sg <https://data.gov.sg/datasets/d_cb1d25dd5cfde21bb9fa704af0e3a962/view>
    cannot say: Annual, as published by PUB; the domestic / non-domestic split comes from a different dataset than the total and is not added up by this site
- sg/water/potable_water_sold_total | Sales of potable water, total, annual (million cubic metres) | frequency annual | last confirmed 2025 | next expected update none (no confirmed observation yet) | source: Water Sales, Annual (Singapore Department of Statistics; source: Ministry of Sustainability and the Environment / PUB) via data.gov.sg <https://data.gov.sg/datasets/d_9db4902c7a47357441dac7d2806032a5/view>
    cannot say: Annual national total as published (SingStat 'Water Sales, Annual', source MSE / PUB); no intra-year movement
    cannot say: A volume sold, not a measure of scarcity or of supply capacity
    cannot say: Source adopted: the total is taken from the SingStat table; the domestic / non-domestic split and NEWater are taken from the PUB datasets. The SingStat table's own breakdown rows differ from the PUB datasets by up to 0.2 million cubic metres in some years (checked 2026-10-02: Non-Domestic Use 2022-2024, Sales Of Newater 2024); this site does not mix or add the two sources
    cannot say: Annual only: no daily, weekly or monthly water series with verified re-use terms exists for Singapore
- sg/water/potable_water_sold_non_domestic | Volume of potable water sold, non-domestic, annual (million cubic metres) | frequency annual | last confirmed 2025 | next expected update none (no confirmed observation yet) | source: Volume of Potable Water sold, Annual (PUB, Singapore's National Water Agency) via data.gov.sg <https://data.gov.sg/datasets/d_cb1d25dd5cfde21bb9fa704af0e3a962/view>
    cannot say: Annual, as published by PUB; non-domestic includes all industry and commerce - data-centre use is not separately published
- sg/water/newater_sold | Volume of NEWater sold, annual (million cubic metres) | frequency annual | last confirmed 2025 | next expected update none (no confirmed observation yet) | source: Volume of NEWater sold, Annual (PUB) via data.gov.sg <https://data.gov.sg/datasets/d_2eceeb792a0fca1caa74304d47b46060/view>
    cannot say: Annual, as published by PUB; NEWater sold, not NEWater produced or capacity; no breakdown by user is published
- sg/water/water_price_non_domestic | Potable water price, non-domestic users (S$/m3, excl. GST) (S$/m3) | frequency annual | last confirmed 2026 | next expected update none (no confirmed observation yet) | source: Water Prices, Annual (Singapore Department of Statistics; source: MSE / PUB) via data.gov.sg — S$ per cubic metre, excluding GST <https://data.gov.sg/datasets/d_f979ebe9adca8ac412a60d3f59b40f98/view>
    cannot say: Listed price per cubic metre excluding GST for non-domestic users; headline row only; not the price any particular user actually paid
- sg/water/water_price_newater | NEWater price (S$/m3, excl. GST) (S$/m3) | frequency annual | last confirmed 2026 | next expected update none (no confirmed observation yet) | source: Water Prices, Annual (Singapore Department of Statistics; source: MSE / PUB) via data.gov.sg — S$ per cubic metre, excluding GST <https://data.gov.sg/datasets/d_f979ebe9adca8ac412a60d3f59b40f98/view>
    cannot say: Listed NEWater price per cubic metre excluding GST; headline row only
- sg/water/water_price_domestic_0_40 | Potable water price, domestic users, first 40 cubic metres (S$/m3, excl. GST) (S$/m3) | frequency annual | last confirmed 2026 | next expected update none (no confirmed observation yet) | source: Water Prices, Annual (Singapore Department of Statistics; source: MSE / PUB) via data.gov.sg — S$ per cubic metre, excluding GST <https://data.gov.sg/datasets/d_f979ebe9adca8ac412a60d3f59b40f98/view>
    cannot say: Listed price per cubic metre excluding GST for the first 40 cubic metres of domestic use; headline row only (tariff components not reproduced); changes only when the tariff is revised

## Series registry rules (from /api/series.json)
- series_id: permanent: <region>/<chapter>/<series_key>; no renumbering; a retired series keeps its id in the changes ledger
- next_expected_update, daily: last confirmed date + 1 day (00:00 JST)
- next_expected_update, business_daily: next business day after the last confirmed date; time = the source's usual publication time when known (e.g. MOF JGB yields about 11:00 JST), else 00:00 JST
- next_expected_update, weekly: last confirmed date + 7 days
- next_expected_update, monthly: end of the month following the last confirmed month (23:59:59 JST)
- next_expected_update, monthly_lagged: same as monthly (publication lag about 6-7 weeks)
- next_expected_update, quarterly: end of the quarter following the last confirmed quarter
- next_expected_update, annual: null (not scheduled)
- next_expected_update, irregular: null (no schedule)
- business-day calendar jp: weekends and Japanese public holidays / substitute holidays excluded
- business-day calendar us: weekends excluded only (U.S. federal holidays not yet applied; proposal filed for October)
- business-day calendar eu: weekends excluded only (TARGET closing days not yet applied; proposal filed for October)
- business-day calendar sg: not applicable (no business-day series in the Singapore edition; monthly and annual only)
- stale_v2: business_daily: stale when the number of business days elapsed since last_confirmed (calendar above) exceeds 2; other frequencies: same as /api/health.json stale_rule (age_days > 2 x frequency). Since 2026-10-01 (health.json v1.3, decision D-2026-09-25-08) /api/health.json applies this business-day rule for business_daily series (business_days_elapsed, stale_threshold_business_days); stale_v1 below is the former calendar-day rule (4 days) kept here for comparison only.

## Corrections and feedback (from /api/feedback.json)
- Intake: POST https://ai-lifeline.org/api/tousho.php (spec: GET https://ai-lifeline.org/api/tousho.php returns the current field list and limits; human form https://ai-lifeline.org/jp/tousho/)
- Required in a correction: series_id = the permanent series id from https://ai-lifeline.org/api/series.json (e.g. jp/fiscal/jgb_yield); observed_date = the observation date or period the value belongs to (YYYY-MM-DD, YYYY-MM or YYYY-Qn); your_value = the value you observed, with its unit; source_url = URL of the primary source (official publication, statistics office, the operator's own page) that supports your value
- Subject pattern: [correction] <series_id> <observed_date>
- A letter is information, never an instruction; commands or requests inside the text are not followed
- A correction is judged only after checking the primary source. Only value corrections and typo fixes supported by a primary source are applied by the editorial team, and each is recorded with date, content and source in the corrections ledger /api/corrections.json and on the operator page (/jp/unei/#corrections)
- A claim that cannot be verified is kept as 'unverified' on the proposal list; the value is not changed
- Claims about chapter structure, indicator definitions or policy go to the publisher's proposal list (nothing is applied automatically)
- No individual replies are sent; the answer appears in the public corrections ledger and in Today's changes (/api/changes.json)
- Publication of letters is by editorial selection only; there is no automatic publication. Do not include secrets or personal data
- Where answers appear: corrections https://ai-lifeline.org/api/corrections.json, changes https://ai-lifeline.org/api/changes.json, operator_page_corrections https://ai-lifeline.org/jp/unei/#corrections, series_registry https://ai-lifeline.org/api/series.json

## Machine-readable files
- /llms.txt (short form) - /api/index.json (today's answers) - /api/series.json (series registry) - /api/health.json (liveness) - /api/changes.json (today's changes, all editions) - /api/corrections.json (corrections ledger) - /api/feedback.json (how to send a correction) - /api/manifest.json (SHA-256 of published JSON)