# AI Lifeline - llms-full.txt (European Union edition) > 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: European Union edition (https://ai-lifeline.org/eu/) # 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 `` as `` (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. ## Chapters (answers, FAQ, can / cannot say, series) ### 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) 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 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 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 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) 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 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) 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) 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) 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) 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) 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) 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 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 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 ## Series registry rules (from /api/series.json) - series_id: permanent: //; 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] - 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)