{
  "schemaVersion": 1,
  "namespace": "appstore2031/storefront/v2",
  "editionId": "2031-2026-08-02",
  "candidateId": "category-001-candidate-08",
  "canonicalCandidateSha256": "d05fe536760876aad6b809047def0a2ab7448fd1ac3fa9b2fb1e797e2ec7a9b5",
  "fictionalDisclosure": true,
  "fiction": {
    "name": "RemedyWeave",
    "developerName": "Joint Remedy Works",
    "iconAsset": "/storefront/v2/icons/category-001-candidate-08.svg",
    "iconTheme": {
      "motif": "A distinct geometric mark derived from the fictional name.",
      "palette": "High-contrast spectral gradient.",
      "shapeLanguage": "Rounded app-store tile with a clear lettermark.",
      "accessibilityNote": "The name remains visible beside the icon; colour is not the only identifier."
    },
    "storeDescription": "RemedyWeave is for the failures nobody wants to own. When an identity service, automated decision system, payment network and delivery provider all played a part, it creates one shared incident record and assigns a qualified human repair lead. That person gathers the right evidence, coordinates temporary safety steps, pushes each supplier to correct its part and keeps you updated. Final legal decisions stay with courts, regulators and public bodies; RemedyWeave's job is to make practical repair happen now.",
    "rating": 4.7,
    "ratingLabel": "imagined 2031 rating",
    "reviews": [
      {
        "reviewerAlias": "PortCitySam",
        "title": "No more supplier ping-pong",
        "body": "One lead joined the transport wallet and identity teams on the same case. I stopped repeating my story and got my travel access restored that day.",
        "stars": 5,
        "stance": "benefit",
        "fictionalDisclosure": true
      },
      {
        "reviewerAlias": "AshaChecks",
        "title": "The record felt too broad",
        "body": "They fixed the failure, but I wanted clearer control over which supplier could see each part of the shared incident file.",
        "stars": 3,
        "stance": "critical",
        "fictionalDisclosure": true
      }
    ]
  },
  "category": {
    "id": "category-001",
    "name": "Qualified Human Help and Service Repair",
    "plainLanguageDefinition": "Gets a serious case to a qualified person who can act, then repairs staffing and caseloads so human help stays reachable over time. It records what the machine did, who can pause or correct it, and whether real service results improve.",
    "recurringBrowsePurpose": "An affected person or frontline worker needing a qualified human response, or a service leader, commissioner, worker body or public body responsible for restoring enough staff to finish cases safely.",
    "completion": {
      "trigger": "A consequential case lacks a qualified human owner, or evidence shows that an automated front door has reduced staffing, human contact, response, continuity or completed outcomes.",
      "boundedWork": "Package machine limits, evidence and overrides; transfer the case to a named qualified person and track the outcome; measure staffing, retention, caseloads, offline contact, complaints, failed handoffs, crises, subgroup results and exits; then restore funded trained staff or pause the automated route when human service falls.",
      "observableDone": "A record names the responsible person, machine limits, evidence and overrides. Callers reach a qualified person without proving harm or repeating their story; that person can pause, correct and finish the response within the local urgent time. Funded retained staff and workable caseloads sustain contact, groups, care, handoffs and appeal. Synthetic contact explains its limits, data use and alternatives. Results by group show response, cases, crises, exits and dependence improving over time; staff or supply limits are recorded."
    }
  },
  "rank": {
    "mainChartPosition": 2,
    "rangeAcrossWeights": [
      1,
      3
    ],
    "dominantWorldIds": [
      "W06"
    ],
    "whyAboveNext": "RemedyWeave tackles the harder structural problem of several suppliers disputing ownership, while CaseCairn at number 3 mainly protects continuity during a handoff between services that still accept their separate duties.",
    "whyThisPosition": "It ranks second because supplier chains can span sectors and borders, the need is serious, and the user can understand what completion means. It sits below RemedySwitch because it depends on contracts or public rules that force rival suppliers to share records and recognise one temporary repair lead.",
    "couldMoveUpIf": "It could take first place if multi-supplier machine services become the normal route for essential decisions and joint repair records gain legal recognition.",
    "couldMoveDownIf": "It would fall if prime providers are made fully liable for their entire supply chain and can already deliver one complete repair route themselves.",
    "strongestCounterCase": "A private coordinator could weaken direct supplier liability and become another holder of sensitive data; joint liability rules may be safer if they force the prime provider to own every repair.",
    "publishedChartAppearances": [
      {
        "chart": "main",
        "rank": 2,
        "worldId": null,
        "geographicLensId": null,
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W01",
        "geographicLensId": "united-states",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W03",
        "geographicLensId": "united-states",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W04",
        "geographicLensId": "united-states",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 1,
        "worldId": "W06",
        "geographicLensId": "united-states",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W01",
        "geographicLensId": "mainland-china",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W03",
        "geographicLensId": "mainland-china",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W04",
        "geographicLensId": "mainland-china",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 1,
        "worldId": "W06",
        "geographicLensId": "mainland-china",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W01",
        "geographicLensId": "european-union",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W03",
        "geographicLensId": "european-union",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W04",
        "geographicLensId": "european-union",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 1,
        "worldId": "W06",
        "geographicLensId": "european-union",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W01",
        "geographicLensId": "india",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W03",
        "geographicLensId": "india",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W04",
        "geographicLensId": "india",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 1,
        "worldId": "W06",
        "geographicLensId": "india",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W01",
        "geographicLensId": "japan-and-republic-of-korea",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W03",
        "geographicLensId": "japan-and-republic-of-korea",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W04",
        "geographicLensId": "japan-and-republic-of-korea",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 1,
        "worldId": "W06",
        "geographicLensId": "japan-and-republic-of-korea",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W01",
        "geographicLensId": "gulf-technology-economies",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W03",
        "geographicLensId": "gulf-technology-economies",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W04",
        "geographicLensId": "gulf-technology-economies",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 1,
        "worldId": "W06",
        "geographicLensId": "gulf-technology-economies",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W01",
        "geographicLensId": "latin-america",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W03",
        "geographicLensId": "latin-america",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W04",
        "geographicLensId": "latin-america",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 1,
        "worldId": "W06",
        "geographicLensId": "latin-america",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W01",
        "geographicLensId": "africa",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W03",
        "geographicLensId": "africa",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W04",
        "geographicLensId": "africa",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 1,
        "worldId": "W06",
        "geographicLensId": "africa",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W01",
        "geographicLensId": "other-material-paths",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W03",
        "geographicLensId": "other-material-paths",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 3,
        "worldId": "W04",
        "geographicLensId": "other-material-paths",
        "weightSetId": null
      },
      {
        "chart": "conditional",
        "rank": 1,
        "worldId": "W06",
        "geographicLensId": "other-material-paths",
        "weightSetId": null
      }
    ]
  },
  "salesPromise": "One human takes charge when a broken result crosses suppliers—and stays until the real-world harm is repaired.",
  "whatItDoes": {
    "headline": "A cross-supplier repair lead",
    "summary": "It identifies the organisations involved in a machine-mediated failure, assigns one qualified human coordinator, tracks each correction and keeps the case alive while formal liability is still being decided.",
    "steps": [
      "Gather the person's consented timeline and request relevant records from each supplier.",
      "Name a qualified human repair lead under a pre-agreed lead-liability rule.",
      "Pause delegated actions where authorised, reconcile records, and coordinate practical correction across suppliers.",
      "Confirm the remedy, export unresolved issues to independent appeal, and charge repeat failure to responsible parties."
    ],
    "outcome": "One named human coordinates the correction, the person receives a practical result and record, and supplier responsibility is not left unresolved."
  },
  "whyOnTheList": {
    "headline": "Multi-supplier systems need one repair owner",
    "summary": "By 2031, one everyday service may rely on many separate systems for identity, data, payment, prediction and physical delivery. A person harmed by the combined result cannot safely manage five support queues. RemedyWeave makes cross-supplier repair a callable service with a named owner and an observable finish.",
    "why2031Not2026": "Incident managers and ombuds services exist now, but routine consumer and public-service outcomes are not yet consistently assembled from many semi-autonomous suppliers with shared records and recognised temporary repair authority. That fragmented responsibility could become a normal 2031 failure pattern.",
    "worldShifts": [
      {
        "shift": "By 2031, consequential services can be assembled from many machine, data, identity, payment, and delivery suppliers while responsibility remains fragmented.",
        "causalChain": [
          "A service outcome is produced by several suppliers and automated handoffs.",
          "Each supplier can show its own component worked or point to another party.",
          "A pre-authorised repair lead assembles the shared record and coordinates correction.",
          "Independent appeal and liability bodies decide contested rights while repeat failures reshape contracts."
        ],
        "basis": "measured-trend",
        "evidenceIds": [
          "AC-06",
          "AC-09"
        ],
        "worldIds": [
          "W06"
        ],
        "evidenceLimit": "The sources support present conditions and directional pressures. This 2031 world, product, name and rank are reasoned forecast artefacts."
      }
    ],
    "whyRepeatedUse": "Every serious cross-supplier failure opens a case, and recurring patterns require contract and staffing repair."
  },
  "futureDistance": {
    "cutoffBaseline": "In 2026, incident managers and ombuds routes exist, but affected people still face separate supplier records and ownership disputes.",
    "structuralDifference2031": "A recognised human lead can coordinate repair across routine machine-mediated supplier chains before final liability is settled.",
    "essential2031Conditions": [
      "Consequential outcomes routinely depend on several autonomous or machine-mediated suppliers.",
      "Contracts or public rules recognise common records, timed responses, and temporary lead repair authority."
    ],
    "notJustBetterAI": "The work is coordinating responsibility, evidence, correction, and remedy across organisations with conflicting interests.",
    "failureCondition": "If one service operator already controls the full chain and can repair every outcome, a separate cross-supplier lead is unnecessary."
  },
  "howItCouldBeBuilt": {
    "overview": "Create lead-liability agreements, a minimum shared incident record, verified supplier contacts, qualified repair staff, response clocks, and portable independent-appeal exports.",
    "components": [
      {
        "name": "Shared failure record",
        "plainLanguageRole": "Shows each supplier action, evidence, limit, handoff, correction, and unresolved disagreement in one readable timeline."
      }
    ],
    "dependencies": [
      {
        "kind": "institutional",
        "name": "Recognised lead-repair rule",
        "plainLanguageRole": "Requires one party to coordinate correction even while final liability remains disputed.",
        "causalRequirement": "Sector contracts, insurance, or regulation can assign temporary repair leadership and later contribution between suppliers.",
        "necessity": "essential",
        "basis": "design-inference",
        "evidenceIds": [],
        "worldIds": [
          "W06"
        ],
        "ifMissing": "The service may organise records but cannot promise coordinated repair."
      }
    ],
    "hardestPart": "Compelling timely cooperation from suppliers that benefit from fragmented responsibility while keeping rights and final remedies with proper authorities.",
    "whatCouldBeSimpler": "A commissioner manually appoints a lead for each serious incident."
  },
  "harmsAndFailure": {
    "whoBenefits": [
      "Affected people get one human owner instead of navigating supplier blame.",
      "Repeated weak links become visible to commissioners and regulators."
    ],
    "warnings": [
      "People with urgent, complex, multilingual, offline, or multi-system cases.",
      "Small suppliers or frontline staff wrongly assigned lead blame without control."
    ],
    "waysItCouldFail": [
      "A central incident record can expose sensitive linked data.",
      "Lead appointment can oversimplify shared causation or delay emergency action."
    ],
    "abuseRisks": [
      "Large suppliers could force smaller parties to carry repair costs.",
      "Suppliers could omit logs, rewrite timelines, or overwhelm leads with low-value data."
    ],
    "safeguards": [
      "Use minimum necessary records, signed provenance, independent sampling, contribution review, and protected urgent action.",
      "Require lead power to match access and control; return unsupported blame to the controlling organisation.",
      "Audit missing records, rejected cases, remedies, and subgroup outcomes."
    ],
    "whenItMustStop": "Stop certifying participating suppliers when they repeatedly miss record or response duties; pause delegated actions where authorised."
  },
  "rankExplanation": {
    "whyThisRank": "It ranks second because supplier chains can span sectors and borders, the need is serious, and the user can understand what completion means. It sits below RemedySwitch because it depends on contracts or public rules that force rival suppliers to share records and recognise one temporary repair lead.",
    "sourceWhyAboveNext": "RemedyWeave tackles the harder structural problem of several suppliers disputing ownership, while CaseCairn at number 3 mainly protects continuity during a handoff between services that still accept their separate duties.",
    "plainEnglishWhyAboveNext": "RemedyWeave tackles the harder structural problem of several suppliers disputing ownership, while CaseCairn at number 3 mainly protects continuity during a handoff between services that still accept their separate duties.",
    "couldMoveUpIf": "It could take first place if multi-supplier machine services become the normal route for essential decisions and joint repair records gain legal recognition.",
    "couldMoveDownIf": "It would fall if prime providers are made fully liable for their entire supply chain and can already deliver one complete repair route themselves.",
    "basis": "design-inference",
    "evidenceIds": [
      "AC-06",
      "AC-09",
      "AC-25",
      "PC-S03",
      "AC-27",
      "PC-S05",
      "AC-30",
      "src-eu-gpai-act-qa",
      "AC-33",
      "PC-S08",
      "RSM-02",
      "PC-S10",
      "AC-39",
      "SC-R15",
      "AC-38",
      "SC-R23",
      "AC-36",
      "EWF-18",
      "E18",
      "horizon.geopolitics-governance-security.s52"
    ],
    "worldIds": [
      "W06"
    ],
    "evidenceLimit": "The score and rank are authored judgements over sealed concepts, not measurements of future adoption."
  },
  "grounding": {
    "scores": {
      "futureDistance": 5,
      "needScale": 5,
      "globalBreadth": 5,
      "marketplaceClarity": 5,
      "deliveryReadiness2031": 3,
      "trustAndSafety": 4,
      "total": 92
    },
    "evidenceAnchors": [
      {
        "statement": "Bound evidence describes uneven real-world transfer and the need for human control in consequential machine-assisted work.",
        "basis": "measured-trend",
        "evidenceIds": [
          "AC-06",
          "AC-09"
        ],
        "worldIds": [
          "W06"
        ]
      }
    ],
    "regionalVariation": [
      {
        "geographyId": "united-states",
        "fit": "conditional",
        "explanation": "Supplier fragmentation creates demand, but sector and state powers to compel cooperation vary.",
        "evidenceIds": [
          "AC-25",
          "PC-S03"
        ]
      },
      {
        "geographyId": "mainland-china",
        "fit": "conditional",
        "explanation": "Coordinated policy may enable lead rules, while local and migrant remedy gaps remain.",
        "evidenceIds": [
          "AC-27",
          "PC-S05"
        ]
      },
      {
        "geographyId": "european-union",
        "fit": "present",
        "explanation": "Switching, court, and AI-governance routes can support cross-supplier records and remedy.",
        "evidenceIds": [
          "AC-30",
          "src-eu-gpai-act-qa"
        ]
      },
      {
        "geographyId": "india",
        "fit": "conditional",
        "explanation": "Assisted identity and informal access are necessary for practical multi-supplier remedy.",
        "evidenceIds": [
          "AC-33",
          "PC-S08"
        ]
      },
      {
        "geographyId": "japan-and-republic-of-korea",
        "fit": "present",
        "explanation": "Highly connected automated services make coordinated repair useful, subject to public funding.",
        "evidenceIds": [
          "RSM-02",
          "PC-S10"
        ]
      },
      {
        "geographyId": "gulf-technology-economies",
        "fit": "conditional",
        "explanation": "Strong digital coordination helps, while non-citizen appeal and supplier transparency need safeguards.",
        "evidenceIds": [
          "AC-39",
          "SC-R15"
        ]
      },
      {
        "geographyId": "latin-america",
        "fit": "conditional",
        "explanation": "Regional supplier chains create need, but enforcement and country variation are material.",
        "evidenceIds": [
          "AC-38",
          "SC-R23"
        ]
      },
      {
        "geographyId": "africa",
        "fit": "conditional",
        "explanation": "Regional bargaining could establish lead rules, while national ownership and records remain uneven.",
        "evidenceIds": [
          "AC-36",
          "EWF-18"
        ]
      },
      {
        "geographyId": "other-material-paths",
        "fit": "unknown",
        "explanation": "Cross-border and small-state paths may lack an authority able to compel every supplier.",
        "evidenceIds": [
          "E18",
          "horizon.geopolitics-governance-security.s52"
        ]
      }
    ],
    "scenarioFit": [
      {
        "worldId": "W06",
        "fit": "strong",
        "reason": "Dense machine-mediated supplier chains make fragmented responsibility and cross-system repair a repeated 2031 service need."
      }
    ],
    "resolutionCriteria": [
      "Every accepted case has one named qualified repair lead and complete known supplier timeline.",
      "Urgent safe action occurs within the local time even when final liability is disputed.",
      "The person receives correction, explanation, record export, and independent appeal.",
      "Repeat supplier non-cooperation and subgroup harm decline under audited contracts."
    ]
  },
  "evidenceLimitations": "Observed and published evidence grounds the world pressures and present constraints. The category, product, developer, reviews, rating and exact rank are fictional forecasts and may be wrong.",
  "datedCollisionAudit": {
    "cutoff": "2026-08-02",
    "auditedAt": "2026-08-03T23:59:59.000Z",
    "verdict": "future-dependent-no-collision-found",
    "publicReason": "no-material-collision-found. This is a search-level collision screen, not a complete registry search, trademark opinion or legal clearance. Search engines can miss products, private services, regional uses, recent launches and non-Latin-script equivalents. A no-material-collision-found verdict means only that this bounded search did not expose a material exact-name use.",
    "closestMatches": []
  },
  "evidenceReferences": [
    {
      "kind": "source",
      "id": "AC-06",
      "title": "METR Task-Completion Time Horizons",
      "publisher": "unknown",
      "url": "https://metr.org/time-horizons/",
      "publishedAt": "2026-05-08",
      "accessedAt": "2026-08-01",
      "limitations": "The metric is human task-equivalent difficulty, not elapsed autonomous runtime; suite coverage is limited",
      "evidenceClass": "measured-trend",
      "geographies": [
        "Other/unspecified",
        "unknown"
      ]
    },
    {
      "kind": "source",
      "id": "AC-09",
      "title": "T2J-Bench",
      "publisher": "unknown",
      "url": "https://arxiv.org/abs/2605.29054",
      "publishedAt": "2026-05-27",
      "accessedAt": "2026-08-01",
      "limitations": "Preprint, one task family",
      "evidenceClass": "measured-trend",
      "geographies": [
        "Other/unspecified",
        "unknown"
      ]
    },
    {
      "kind": "source",
      "id": "AC-25",
      "title": "America's AI Action Plan",
      "publisher": "unknown",
      "url": "https://www.whitehouse.gov/releases/2025/07/white-house-unveils-americas-ai-action-plan/",
      "publishedAt": "2025-07-23",
      "accessedAt": "2026-08-01",
      "limitations": "Political plan, not evidence of implementation or outcomes",
      "evidenceClass": "policy-intent",
      "geographies": [
        "United States",
        "United States/North America"
      ]
    },
    {
      "kind": "source",
      "id": "PC-S03",
      "title": "United States Data Center Energy Usage Report: 2025 Update",
      "publisher": "Lawrence Berkeley National Laboratory",
      "url": "https://eta-publications.lbl.gov/publications/united-states-data-center-energy-2025",
      "publishedAt": "undated-at-access",
      "accessedAt": "2026-08-02",
      "limitations": "This is a US-only bottom-up model, not a global forecast. Shipment, lifetime, utilisation and cooling assumptions drive the range. It does not predict local tariffs, queue rules or who receives service.",
      "evidenceClass": "modelled-projection",
      "geographies": [
        "United States"
      ]
    },
    {
      "kind": "source",
      "id": "AC-27",
      "title": "State Council “AI Plus” opinion",
      "publisher": "unknown",
      "url": "https://big5.www.gov.cn/gate/big5/www.gov.cn/zhengce/content/202508/content_7037861.htm",
      "publishedAt": "2025-08-26",
      "accessedAt": "2026-08-01",
      "limitations": "The percentage is a government target whose definition and measurement are not yet independently established",
      "evidenceClass": "policy-intent",
      "geographies": [
        "China"
      ]
    },
    {
      "kind": "source",
      "id": "PC-S05",
      "title": "China releases plan to advance Digital China development",
      "publisher": "State Council of the People's Republic of China",
      "url": "https://english.www.gov.cn/news/202505/17/content_WS6827c405c6d0868f4e8f29cc.html",
      "publishedAt": "2025-05-17",
      "accessedAt": "2026-08-02",
      "limitations": "A target is not verified delivered or generally available capacity. EFLOPS measures are not automatically comparable across all hardware and workloads. The plan does not show that an individual can buy or move capacity freely.",
      "evidenceClass": "policy-intent",
      "geographies": [
        "China"
      ]
    },
    {
      "kind": "source",
      "id": "AC-30",
      "title": "Navigating the AI Act",
      "publisher": "unknown",
      "url": "https://digital-strategy.ec.europa.eu/en/faqs/navigating-ai-act",
      "publishedAt": "2026-07-27",
      "accessedAt": "2026-08-01",
      "limitations": "Implementation and enforcement outcomes remain unobserved at cutoff",
      "evidenceClass": "policy-intent",
      "geographies": [
        "European Union",
        "Europe/EU"
      ]
    },
    {
      "kind": "source",
      "id": "src-eu-gpai-act-qa",
      "title": "General-Purpose AI Models in the AI Act - Questions & Answers",
      "publisher": "European Commission",
      "url": "https://digital-strategy.ec.europa.eu/en/faqs/general-purpose-ai-models-ai-act-questions-answers",
      "publishedAt": "undated-at-access",
      "accessedAt": "2026-08-02",
      "limitations": "The official page did not expose a clear publication date; it was accessed on 2026-08-02. Legal systemic-risk thresholds and duties do not predict capability or enforcement capacity.",
      "evidenceClass": "policy-intent",
      "geographies": [
        "eu"
      ]
    },
    {
      "kind": "source",
      "id": "AC-33",
      "title": "Digital India and IndiaAI shared compute",
      "publisher": "unknown",
      "url": "https://www.pib.gov.in/PressReleasePage.aspx?PRID=2278453&lang=1&reg=48",
      "publishedAt": "2026-06-27",
      "accessedAt": "2026-08-01",
      "limitations": "Government-reported counts do not equal frontier-equivalent or fully utilised compute",
      "evidenceClass": "measured-trend",
      "geographies": [
        "India"
      ]
    },
    {
      "kind": "source",
      "id": "PC-S08",
      "title": "India's Common Compute Capacity Crosses 34,000 GPUs",
      "publisher": "Press Information Bureau, Government of India",
      "url": "https://www.pib.gov.in/PressReleasePage.aspx?PRID=2132817&lang=1&reg=3",
      "publishedAt": "2025-05-30",
      "accessedAt": "2026-08-02",
      "limitations": "Empanelled capacity is not the same as continuously available capacity. GPU counts do not capture performance differences, networking, storage or software readiness. Government reporting is not evidence that every person can access every listed resource.",
      "evidenceClass": "measured-trend",
      "geographies": [
        "India"
      ]
    },
    {
      "kind": "source",
      "id": "RSM-02",
      "title": "Global Robot Density in Factories Doubled in Seven Years",
      "publisher": "IFR",
      "url": "https://ifr.org/ifr-press-releases/news/robot-density-surges-in-europe-asia-and-americas",
      "publishedAt": "undated-at-access",
      "accessedAt": "2026-08-01",
      "limitations": "Density is a stock-to-employment ratio, not a measure of autonomous task coverage or productivity",
      "evidenceClass": "measured-trend",
      "geographies": [
        "Global",
        "Global/international"
      ]
    },
    {
      "kind": "source",
      "id": "PC-S10",
      "title": "MSIT to Establish the National AI Computing Center as a Catalyst for Genuine Growth in AI",
      "publisher": "Ministry of Science and ICT, Republic of Korea",
      "url": "https://www.msit.go.kr/eng/bbs/view.do?bbsSeqNo=42&mId=4&mPid=2&nttSeqNo=1166&pageIndex=1&sCode=eng&searchOpt=ALL",
      "publishedAt": "2025-09-08",
      "accessedAt": "2026-08-02",
      "limitations": "Most capacity numbers are planned procurement or construction, not delivered service. A public-private centre does not imply unrestricted person-level access. The source is one national plan and should not be generalised to all of Asia.",
      "evidenceClass": "policy-intent",
      "geographies": [
        "Republic of Korea"
      ]
    },
    {
      "kind": "source",
      "id": "AC-39",
      "title": "Stargate UAE in planned 5 GW campus",
      "publisher": "unknown",
      "url": "https://www.mediaoffice.abudhabi/en/technology/global-tech-alliance-launches-stargate-uae/",
      "publishedAt": "2026-04-27",
      "accessedAt": "2026-08-01",
      "limitations": "Promotional sources; announced partners and capacity are not assured delivery",
      "evidenceClass": "measured-trend",
      "geographies": [
        "United Arab Emirates",
        "Saudi Arabia",
        "Middle East/Gulf",
        "United Arab Emirates / Saudi Arabia"
      ]
    },
    {
      "kind": "source",
      "id": "SC-R15",
      "title": "Saudi Family Statistics 2024",
      "publisher": "General Authority for Statistics, Saudi Arabia",
      "url": "https://www.stats.gov.sa/documents/20117/2435273/Saudi%2BFamily%2BStatistics%2BEN.pdf/14706a41-9ba0-1ae8-e1b4-f6ee2ec3d7f3",
      "publishedAt": "undated-at-access",
      "accessedAt": "2026-08-02",
      "limitations": "Household size and type do not reveal loneliness, autonomy, relationship quality or within-household exclusion.",
      "evidenceClass": "measured-trend",
      "geographies": [
        "Saudi Arabia"
      ]
    }
  ],
  "rankingIndexPath": "rankings/category-001/index.json",
  "sourceReceipts": []
}
