{
  "format": "agent-article-v0",
  "article_id": "EA-062",
  "canonical_url": "/tools/ea-062-data-residency-sovereign-ai",
  "page_type": "reference",
  "claim_ids": [],
  "evidence_ids": [
    "EVD-EA-062-URL-B85DC9207D05",
    "EVD-EA-062-URL-82C97913ADAF",
    "EVD-EA-062-URL-6EB682A9E7CB",
    "EVD-EA-062-URL-FAE2196874A7",
    "EVD-EA-062-URL-45084A6538D2",
    "EVD-EA-062-URL-44F96EE3C027",
    "EVD-EA-062-URL-C1B3487DF384",
    "EVD-EA-062-URL-0BF19B892A08",
    "EVD-EA-062-URL-33B08F5D4F48",
    "EA-062-R11-RESEARCH",
    "EA-062-R11-WEB-READBACK"
  ],
  "unknown_ids": [
    "EA-062-UNKNOWN-01",
    "EA-062-UNKNOWN-CURRENTNESS"
  ],
  "operational_object_ids": [],
  "provider": [
    "OpenAI"
  ],
  "models": [],
  "plans": [],
  "surfaces": [],
  "regions": [],
  "current_status": "UNKNOWN",
  "observation_status": "SPEC_ONLY",
  "freshness": "UNKNOWN",
  "last_verified": null,
  "supersedes": [],
  "superseded_by": [],
  "provenance": [
    "COMM-058-EA0062",
    "SRC-EA-062-URL-B85DC9207D05",
    "SRC-EA-062-URL-82C97913ADAF",
    "SRC-EA-062-URL-6EB682A9E7CB",
    "SRC-EA-062-URL-FAE2196874A7",
    "SRC-EA-062-URL-45084A6538D2",
    "SRC-EA-062-URL-44F96EE3C027",
    "SRC-EA-062-URL-C1B3487DF384",
    "SRC-EA-062-URL-0BF19B892A08",
    "SRC-EA-062-URL-33B08F5D4F48",
    "WEBBODY-EA0062-R8-08E96213"
  ],
  "article_sources": [
    {
      "id": "EVD-EA-062-URL-B85DC9207D05",
      "evidence_class": "RESEARCH",
      "title": "E1 | official product docs | \"Data residency and inference residency for ChatGPT\" | OpenAI |",
      "href": "https://help.openai.com/en/articles/9903489-data-residency-for-chatgpt",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-062-URL-B85DC9207D05"
      ],
      "supporting_locators": [
        "EVIDENCE TABLE",
        "E1 | official product docs | \"Data residency and inference residency for ChatGPT\" | OpenAI | https://help.openai.com/en/articles/9903489-data-residency-for-chatgpt"
      ],
      "scope": "EVIDENCE TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EVD-EA-062-URL-82C97913ADAF",
      "evidence_class": "RESEARCH",
      "title": "E2 | official product docs | \"Data, privacy, and security for Foundry Models sold by Azure in Microsoft Foundry\" | Microsoft |",
      "href": "https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/data-privacy",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-062-URL-82C97913ADAF"
      ],
      "supporting_locators": [
        "EVIDENCE TABLE",
        "E2 | official product docs | \"Data, privacy, and security for Foundry Models sold by Azure in Microsoft Foundry\" | Microsoft | https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/data-privacy"
      ],
      "scope": "EVIDENCE TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EVD-EA-062-URL-6EB682A9E7CB",
      "evidence_class": "RESEARCH",
      "title": "E3 | official product docs | \"Region availability for Foundry Models sold by Azure\" | Microsoft |",
      "href": "https://learn.microsoft.com/en-us/azure/foundry/foundry-models/concepts/models-sold-directly-by-azure-region-availability",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-062-URL-6EB682A9E7CB"
      ],
      "supporting_locators": [
        "EVIDENCE TABLE",
        "E3 | official product docs | \"Region availability for Foundry Models sold by Azure\" | Microsoft | https://learn.microsoft.com/en-us/azure/foundry/foundry-models/concepts/models-sold-directly-by-azure-region-availability"
      ],
      "scope": "EVIDENCE TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EVD-EA-062-URL-FAE2196874A7",
      "evidence_class": "RESEARCH",
      "title": "E4 | official product docs | \"Geographic cross-Region inference\" | Amazon Web Services |",
      "href": "https://docs.aws.amazon.com/bedrock/latest/userguide/geographic-cross-region-inference.html",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-062-URL-FAE2196874A7"
      ],
      "supporting_locators": [
        "EVIDENCE TABLE",
        "E4 | official product docs | \"Geographic cross-Region inference\" | Amazon Web Services | https://docs.aws.amazon.com/bedrock/latest/userguide/geographic-cross-region-inference.html"
      ],
      "scope": "EVIDENCE TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EVD-EA-062-URL-45084A6538D2",
      "evidence_class": "RESEARCH",
      "title": "E5 | official product docs | \"Data retention\" | Amazon Web Services |",
      "href": "https://docs.aws.amazon.com/bedrock/latest/userguide/data-retention.html",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-062-URL-45084A6538D2"
      ],
      "supporting_locators": [
        "EVIDENCE TABLE",
        "E5 | official product docs | \"Data retention\" | Amazon Web Services | https://docs.aws.amazon.com/bedrock/latest/userguide/data-retention.html"
      ],
      "scope": "EVIDENCE TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EVD-EA-062-URL-44F96EE3C027",
      "evidence_class": "RESEARCH",
      "title": "E6 | official product docs | \"Monitor model invocation using CloudWatch Logs and Amazon S3\" | Amazon Web Services |",
      "href": "https://docs.aws.amazon.com/bedrock/latest/userguide/model-invocation-logging.html",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-062-URL-44F96EE3C027"
      ],
      "supporting_locators": [
        "EVIDENCE TABLE",
        "E6 | official product docs | \"Monitor model invocation using CloudWatch Logs and Amazon S3\" | Amazon Web Services | https://docs.aws.amazon.com/bedrock/latest/userguide/model-invocation-logging.html"
      ],
      "scope": "EVIDENCE TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EVD-EA-062-URL-C1B3487DF384",
      "evidence_class": "RESEARCH",
      "title": "E7 | official contractual/product terms | \"Google Cloud Platform Services with Data Residency\" | Google Cloud |",
      "href": "https://cloud.google.com/terms/data-residency",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-062-URL-C1B3487DF384"
      ],
      "supporting_locators": [
        "EVIDENCE TABLE",
        "E7 | official contractual/product terms | \"Google Cloud Platform Services with Data Residency\" | Google Cloud | https://cloud.google.com/terms/data-residency"
      ],
      "scope": "EVIDENCE TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EVD-EA-062-URL-0BF19B892A08",
      "evidence_class": "RESEARCH",
      "title": "E8 | official contractual terms | \"Service Specific Terms\" | Google Cloud |",
      "href": "https://cloud.google.com/terms/service-terms",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-062-URL-0BF19B892A08"
      ],
      "supporting_locators": [
        "EVIDENCE TABLE",
        "E8 | official contractual terms | \"Service Specific Terms\" | Google Cloud | https://cloud.google.com/terms/service-terms"
      ],
      "scope": "EVIDENCE TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EVD-EA-062-URL-33B08F5D4F48",
      "evidence_class": "RESEARCH",
      "title": "E9 | official public-policy/procurement framework | \"Sovereign Cloud Framework explained\" | European Commission |",
      "href": "https://commission.europa.eu/news-and-media/news/sovereign-cloud-framework-explained-2026-06-01_en",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-062-URL-33B08F5D4F48"
      ],
      "supporting_locators": [
        "EVIDENCE TABLE",
        "E9 | official public-policy/procurement framework | \"Sovereign Cloud Framework explained\" | European Commission | https://commission.europa.eu/news-and-media/news/sovereign-cloud-framework-explained-2026-06-01_en"
      ],
      "scope": "EVIDENCE TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EA-062-R11-RESEARCH",
      "evidence_class": "RESEARCH",
      "title": "EA-062 監査済みresearch / canonical revision binding",
      "supports": [
        "1. VERIFIED_SPEC: Data ResidencyとInference/Processing Residencyは別面である。OpenAIが用語として明示的に分離し、Azure/AWSもdeployment/routingの実装として同じ差を示す。\n2. VERIFIED_SPEC: at-rest保証がsource geography/regionにあっても、Global/Data Zone/cross-region inferenceではprompt/response処理が別region/zoneへ移動し得る。\n3. VERIFIED_SPEC: logging、abuse monitoring、backup/DR、metadata/control plane、grounding/RAG、agent runtime/memory/session等は、base inference/storageとは別の適用範囲・例外を持ち得る。\n4. VERIFIED_SPEC + PRODUCT_VOLATILE: 利用可否はprovider名ではなく、plan/tenant、region、model ID/version、deployment type、feature/subsystem、retention mode等の組合せで決まる。\n5. VERIFIED_SPEC: Sovereign AI/cloudはdata residencyより広い。少なくともEU Commissionの現行sovereignty frameworkではlegal/jurisdictional、operational、supply-chain、technological autonomy等を別評価する。\n6. INFERENCE: provider横断のEnterprise AI Coreでは「どの国/regionか」だけでなく、「何のdata/artifactを、どのoperationで、誰/どのserviceが、どこで扱い、どの期間残すか」を最小比較単位にする必要がある。\n7. INFERENCE: regional endpointやregional storageの存在は、workload全体のregionality/sovereigntyを証明しない。最も境界の弱いsubsystem/feature/tool/log pathが実効境界を決める。"
      ],
      "limit": "canonical監査・revision bindingの存在を示す。外部ソースcurrentnessが本文またはcontrol-planeで確定していない場合は、currentnessをUNKNOWNのまま保持する。",
      "origin_class": "AUDITED_CANONICAL_RESEARCH_PACKET",
      "source_or_experiment_ids": [
        "COMM-058-EA0062"
      ],
      "supporting_locators": [
        "COMM-058-EA0062",
        "EA-062-R5-LEGACY-MIGRATION-20261008-R1",
        "content/staging/EA-062.md"
      ],
      "scope": "監査済みEA本文・canonical revision・既存Source Graph relationの範囲。欠損currentnessは推測で閉じない。",
      "provenance_status": "AUDIT_PASS_CANONICAL_BINDING"
    },
    {
      "id": "EA-062-R11-WEB-READBACK",
      "evidence_class": "IMPL",
      "title": "EA-062 Web body identity / canonical readback",
      "supports": [
        "canonical staging bodyのSHA-256一致とR9 canonical ledger readbackをProduction projectionの入力として検証する。"
      ],
      "limit": "body identity/readbackは本文claim自体の真偽や外部ソースの最新性を追加保証しない。",
      "checked_at": null,
      "origin_class": "IMPLEMENTATION_READBACK",
      "source_or_experiment_ids": [
        "WEBBODY-EA0062-R8-08E96213"
      ],
      "supporting_locators": [
        "WEBBODY-EA0062-R8-08E96213",
        "content/staging/EA-062.md",
        "EA-062-R5-LEGACY-MIGRATION-20261008-R1"
      ],
      "scope": "R9/R10 canonical readback後のProduction生成時body identity。",
      "provenance_status": "CANONICAL_READBACK_BODY_HASH_MATCH"
    }
  ],
  "research_sections": [
    {
      "heading": "WHY_THIS_MATTERS_TO_UPDATE",
      "text": "Enterprise AIでは「データが日本/欧州にある」「リージョンを選んだ」という一文だけでは、保存・推論・検索/grounding・agent runtime・ログ・abuse monitoring・backup/DR・support/debug・metadata/control planeの所在地を説明できない。さらにData ResidencyとSovereign AIは同義ではなく、法的管轄、運用主体、供給網、技術的自律性まで含む場合がある。将来版では、providerの地域機能を単一の○×ではなく、データ面/処理面/運用面に分解して記載しなければ過大保証になる。"
    },
    {
      "heading": "SCOPE_ROUTING",
      "text": "Enterprise AI Core / provider mapping / organization overlay / interoperability / governance / security & privacy / implementation / non-LLM component"
    },
    {
      "heading": "CLAIM_OR_RESEARCH_QUESTION",
      "text": "1. Data residencyの対象は何か。保存(at rest)と推論/処理(inference/processing)は同一境界か。\n2. ログ、abuse monitoring、backup、routing、metadata、support/debug、RAG/grounding/agent機能は同じ地域保証に含まれるか。\n3. providerのGlobal/Data Zone/Regional等のdeployment方式はどこまで処理場所を拘束するか。\n4. Sovereign AI/sovereign cloudはresidencyと何が異なるか。\n5. 後続Workがprovider横断で比較できる最小のresidency/sovereignty記述単位は何か。"
    },
    {
      "heading": "EVIDENCE TABLE",
      "text": "E1 | official product docs | \"Data residency and inference residency for ChatGPT\" | OpenAI | https://help.openai.com/en/articles/9903489-data-residency-for-chatgpt | access 2026-09-14; page current as-of access | current product docs; no API revision | locators: definitions of Data Residency / Inference Residency; supported regions; \"What is not included\" / limitations | VERIFIED_SPEC + PRODUCT_VOLATILE | support + limit\n- Data residencyは対象customer contentのat-rest保存地域、inference residencyは対象contentのGPU execution地域として別概念。現行ページはat-rest対象地域としてAustralia/Canada/Europe/India/Japan/Singapore/South Korea/UAE/UK/USを列挙し、inference residencyは現行対応地域が限定される。inference residency利用には同一地域のdata residencyが前提。\n- authentication、routing、contentを含まないlogging、indexing等は選択地域外で処理され得ると明記。すべてのfeature/modelが同じresidency対象ではない。\n\n\nE2 | official product docs | \"Data, privacy, and security for Foundry Models sold by Azure in Microsoft Foundry\" | Microsoft | https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/data-privacy | access 2026-09-14 | current Microsoft Foundry docs | locators: Global deployment / DataZone deployment / data at rest | VERIFIED_SPEC + PRODUCT_VOLATILE | support + limit\n- Global deploymentではprompt/response処理がmodel提供可能な複数geographyへ回り得る。Data Zoneでは指定data zone内の複数地域で処理され得る。一方、uploaded dataやabuse-monitoring store等のat-rest dataはcustomer-designated geographyに保持されるとする。処理場所と保存場所を分離する一次根拠。\n\n\nE3 | official product docs | \"Region availability for Foundry Models sold by Azure\" | Microsoft | https://learn.microsoft.com/en-us/azure/foundry/foundry-models/concepts/models-sold-directly-by-azure-region-availability | access 2026-09-14; current page published/updated 2026 | model/version/deployment-type specific | locators: deployment type descriptions; model-region tables | VERIFIED_SPEC + PRODUCT_VOLATILE | support + limit\n- Global/Data Zone/Regional(Standard)等で処理境界が異なる。利用可否はmodel ID/version、deployment type、resource regionの組合せで変動するため、「Azureで利用可能」だけではresidencyを確定できない。\n\n\nE4 | official product docs | \"Geographic cross-Region inference\" | Amazon Web Services | https://docs.aws.amazon.com/bedrock/latest/userguide/geographic-cross-region-inference.html | access 2026-09-14 | current Amazon Bedrock docs | locators: source Region / destination Region / prompt-output movement / abuse detection storage | VERIFIED_SPEC + PRODUCT_VOLATILE | support + limit\n- cross-Region inferenceでは、既定でdataはsource Regionに保存される一方、input prompt/output resultがsource Region外へ移動し得る。abuse detectionのため保存する場合はdestination Regionに保存され得る。at-restの既定位置だけではinference pathを説明できない。\n\n\nE5 | official product docs | \"Data retention\" | Amazon Web Services | https://docs.aws.amazon.com/bedrock/latest/userguide/data-retention.html | access 2026-09-14 | current Amazon Bedrock data-retention modes | locators: data_retention_mode; none/ZDR; model compatibility; cross-region retained data | VERIFIED_SPEC + PRODUCT_VOLATILE | support + limit\n- retention mode `none` はZero Data Retentionを構成するprovider controlだが、対応しないmodelは利用できない。`store=false`だけで常にZDRを保証するわけではない。cross-region inferenceでretentionが発生する場合、destination側保存も考慮が必要。modelごとのpolicy gateが存在する。\n\n\nE6 | official product docs | \"Monitor model invocation using CloudWatch Logs and Amazon S3\" | Amazon Web Services | https://docs.aws.amazon.com/bedrock/latest/userguide/model-invocation-logging.html | access 2026-09-14 | current Bedrock invocation logging | locators: logging disabled by default; CloudWatch/S3 destinations | VERIFIED_SPEC + PRODUCT_VOLATILE | context + limit\n- invocation loggingは別設定面であり、default disabled。enable時のCloudWatch/S3 destinationは独立して設計する必要がある。推論リージョンだけでログ所在地/保存を代表させてはならない。\n\n\nE7 | official contractual/product terms | \"Google Cloud Platform Services with Data Residency\" | Google Cloud | https://cloud.google.com/terms/data-residency | last modified 2026-09-08; access 2026-09-14 | current service list | locators: AI/ML Data Location; Generative AI / Gemini Enterprise Agent Platform exceptions | VERIFIED_SPEC + PRODUCT_VOLATILE | support + limit\n- current Data Residency対象service一覧はGenerative AIを含むが、Grounding with Google Search/Maps、RAG Engine等に例外がある。AI/ML Data Locationでも対象model/featureが限定され、Gemini Enterprise Agent PlatformのFeature Store、Agent Runtime、Memory Bank、Sessions、Sandboxes、RAG Engine、Agent Evaluations等に個別例外が示される。製品単位の地域保証をagent subsystem全体へ拡張してはならない。\n\n\nE8 | official contractual terms | \"Service Specific Terms\" | Google Cloud | https://cloud.google.com/terms/service-terms | access 2026-09-14 | current terms | locators: Data Location; storage at rest; same-country/multi-region replication; resource identifiers/attributes exclusions | VERIFIED_SPEC + PRODUCT_VOLATILE | support + limit\n- 対象serviceでは選択Region/Multi-RegionでCustomer Data at restを保管するとしつつ、backup/reliability/debugging/support/maintenance/securityのため同一国またはselected Multi-Region内でreplicationし得る。resource identifiers、attributes、other data labels等はCustomer Data定義から外れる場合がある。customer側のaccess/movementもprovider residency保証とは別。\n\n\nE9 | official public-policy/procurement framework | \"Sovereign Cloud Framework explained\" | European Commission | https://commission.europa.eu/news-and-media/news/sovereign-cloud-framework-explained-2026-06-01_en | published 2026-06-01; access 2026-09-14 | Sovereign Cloud Framework / SEAL | locators: eight sovereignty categories; SEAL levels | VERIFIED_SPEC | context + limit\n- EU Commissionのframeworkはsovereigntyをdata locationだけに限定せず、strategic、legal/jurisdictional、data and AI、operational、supply chain、technological、security/compliance、environmental sustainabilityの8領域で評価する。したがってsovereignty=residencyという同一視は不適切。このframeworkはEU調達文脈の評価枠であり、全クラウド/全法域に自動適用される普遍的技術標準ではない。"
    },
    {
      "heading": "FINDINGS",
      "text": "1. VERIFIED_SPEC: Data ResidencyとInference/Processing Residencyは別面である。OpenAIが用語として明示的に分離し、Azure/AWSもdeployment/routingの実装として同じ差を示す。\n2. VERIFIED_SPEC: at-rest保証がsource geography/regionにあっても、Global/Data Zone/cross-region inferenceではprompt/response処理が別region/zoneへ移動し得る。\n3. VERIFIED_SPEC: logging、abuse monitoring、backup/DR、metadata/control plane、grounding/RAG、agent runtime/memory/session等は、base inference/storageとは別の適用範囲・例外を持ち得る。\n4. VERIFIED_SPEC + PRODUCT_VOLATILE: 利用可否はprovider名ではなく、plan/tenant、region、model ID/version、deployment type、feature/subsystem、retention mode等の組合せで決まる。\n5. VERIFIED_SPEC: Sovereign AI/cloudはdata residencyより広い。少なくともEU Commissionの現行sovereignty frameworkではlegal/jurisdictional、operational、supply-chain、technological autonomy等を別評価する。\n6. INFERENCE: provider横断のEnterprise AI Coreでは「どの国/regionか」だけでなく、「何のdata/artifactを、どのoperationで、誰/どのserviceが、どこで扱い、どの期間残すか」を最小比較単位にする必要がある。\n7. INFERENCE: regional endpointやregional storageの存在は、workload全体のregionality/sovereigntyを証明しない。最も境界の弱いsubsystem/feature/tool/log pathが実効境界を決める。"
    },
    {
      "heading": "LIMITS / COUNTEREVIDENCE / FAILURE ENVELOPE",
      "text": "- \"Japan region available\"や\"EU data residency\"を、全processing/全feature/全metadata/全operator accessの国内・域内固定と読み替えない。\n- Global/Data Zone/cross-region inferenceは可用性/容量面の利点と引換えに処理場所が広がる場合がある。\n- RAG、web/search/maps grounding、agent runtime、memory、sandbox、session、evaluation、connector/toolはbase modelと異なるresidency scopeを持ち得る。\n- abuse/safety monitoringにretentionやdestination-side storageが存在し得る。ZDR/retention設定はmodel compatibilityを変える場合がある。\n- providerのログ機能は別途enable/routeされることがあり、推論地域からログ地域を推定できない。\n- backup/DR/support/debugのreplica境界は「exact region」と同じとは限らない。\n- control-plane metadata、billing、resource identifiers、routing/authentication等がcustomer-content residencyの対象外となる場合がある。\n- customer自身またはthird-party tool/connectorによるexport/egressはproviderのbase residency guarantee外になり得る。\n- residencyはjurisdiction、operator nationality/control、supply-chain independence、cryptographic/key sovereignty、technical autonomyを自動的に満たさない。\n- provider docs/region tablesは高頻度に変わるため、公開後アップデート時に再確認必須。"
    },
    {
      "heading": "AVAILABILITY_GATES",
      "text": "OpenAI: eligible workspace/plan、選択data-residency region、inference-residency supported region、model/feature limitation。inference residencyとdata residencyは同一regionでの対応が必要。\nMicrosoft Foundry: model ID/version × deployment type(Global/Data Zone/Regional等) × resource region/geography × feature。\nAmazon Bedrock: source region × inference profile/cross-region mode × destination region set × model × data-retention mode × logging configuration。\nGoogle Cloud: service × region/multi-region × AI/ML Data Location対象model × feature/subsystem exceptions。Agent/RAG/grounding系は個別確認が必要。\nSovereign offering/framework: residencyだけでなく法的/運用/供給網/技術統制の適用条件を個別確認。"
    },
    {
      "heading": "IMPLEMENTATION_STATE",
      "text": "- Provider-native residency/region controlsは複数社で実装済み。ただしsemantic scopeは統一されていない。\n- provider横断で同じ意味を持つ単一の\"AI residency\" switch/specは本RUNでは確認できない。\n- PROPOSAL: Enterprise AI Coreに `Residency & Sovereignty Matrix` を置く。最低列は `artifact/data class | operation(store/process/route/log/backup/support/review) | provider/service/feature | model/version | deployment type | region/country/zone | retention | access actor | third party/subprocessor | key/control plane | evidence date/version | status(VERIFIED/UNKNOWN)`。\n- PROPOSAL: workload release gateは、policy-required cellがUNKNOWNまたはallowed boundary外ならpromotion不可とする。これは既存provider仕様ではなく将来運用設計案。\n- PROPOSAL: runtime/asset inventoryからmodel/feature/deployment変更を検知し、MatrixのPRODUCT_VOLATILE cellを再検証対象にする。"
    },
    {
      "heading": "BENCHMARK_OR_EVAL",
      "text": "通常のmodel benchmarkはresidency/sovereigntyを評価しないため、benchmark scoreの外挿は禁止。\n適切なのはconformance evaluation: 各data planeについてdocumentation/contract/configuration/observable telemetryを突合し、`store/process/route/log/backup/support`ごとにPASS/FAIL/UNKNOWNを付ける。\nSAFE TEST_PROFILE（未実施）: synthetic/non-sensitive inputだけを用い、指定region deploymentで公開configuration、request routing metadata、provider-exposed log destination、retention settingを確認する。tenant secrets、実顧客データ、課金変更、危険なcross-border testは実施しない。"
    },
    {
      "heading": "SECURITY/PRIVACY",
      "text": "residency boundary外へのtool/grounding/log/monitoring pathをdata-flow threat modelへ含める。ZDRとdata residencyは別controlとして記録する。\nAUDIT: 実行時にはprovider/service、model/version、deployment type、requested region、resolved processing policy、retention/log settings、Matrix revisionをtrace/audit provenanceへ残す。ただしproviderが実destinationを公開しない場合はUNKNOWNを維持する。"
    },
    {
      "heading": "COST",
      "text": "Global/cross-region routing、dedicated/sovereign offering、regional capacity reservation等はcost/throughput/availability trade-offを持ち得るため、価格は公開後Workでcurrent claimとして再採集する。本RUNでは価格を確定しない。"
    },
    {
      "heading": "OPERABILITY",
      "text": "failover時に地域境界を拡大する設計は、通常時とincident時でpolicyが変わる。availability failoverとresidency policyの優先順位を事前に明示する必要がある。"
    },
    {
      "heading": "SAFE_WORDING_FOR_FUTURE_BOOK",
      "text": "「データレジデンシーは『リージョンを選べばすべてがその地域に留まる』という単一機能ではない。保存、推論、ルーティング、ログ、監視、バックアップ、検索/grounding、エージェント実行などで適用範囲が異なり、provider・model・deployment type・featureごとに確認が必要である。Sovereign AIはさらに法的管轄、運用統制、供給網、技術的自律性などを含み得るため、Data Residencyと同義に扱わない。」"
    },
    {
      "heading": "UPDATE_WORK_HANDOFF",
      "text": "1. 将来版でData Residencyのprovider mappingを作る場合、OpenAI/Azure/Bedrock/Googleを同じ「地域対応○」表にせず、Storage / Inference / Routing / Logs & Monitoring / Backup & Support / RAG & Grounding / Agent Runtime & Memory / Metadata-Control Planeで分割する。\n2. current product claimは公開時点で必ず再取得する。特にOpenAI supported inference regions、Azure model-version-region table、Bedrock retention/model restrictions、Google AI/ML Data Location exception listを再確認。\n3. `Residency & Sovereignty Matrix` はCore候補として、EA-061 Data Classificationのdata class/provenanceと接続する。classification labelだけでは処理地域を決めず、purpose/principal/provider/feature/retentionと組み合わせる。\n4. Sovereign AI章では「residency」「jurisdiction/control」「operational sovereignty」「supply chain」「technical autonomy」を別軸で採否する。EU Sovereign Cloud Frameworkは有力な比較枠だが、EU procurement contextを明記する。\n5. tenant実証が必要になった場合は上記SAFE TEST_PROFILEを使用し、未観測部分をpublic docsで埋めたことにしない。"
    },
    {
      "heading": "OPEN_UNKNOWN",
      "text": "- provider横断で共通利用できる正式なAI residency/sovereignty machine-readable schemaは未確認。\n- 各providerが内部routingした実処理regionをrequest単位でどこまで監査可能に露出するかはprovider/feature別に未確定。\n- agent tool/connector先third-partyまで含むend-to-end residency attestationの一般標準は未確認。\n- exact sovereign controls（key ownership/operator access/jurisdiction/supply-chain）をAI service単位で比較できる共通証明形式は未確認。"
    },
    {
      "heading": "STOP CONDITION",
      "text": "EA-062の初回Evidence Packetとして、主要4 providerの保存/処理/ログ・subsystem差、Sovereign AIとの概念差、availability gates、failure envelope、future Core用matrix案まで一次公式資料でboundedに確立した。次回は同一claim/source versionを再採集せず、上記OPEN_UNKNOWNに直接答える標準/attestationまたは新version差分がある場合のみ補完する。\n\n---"
    },
    {
      "heading": "AUDITED_BOUNDARY",
      "text": "Storage-at-rest, inference/processing residency, routing, logs, backup/support, grounding/RAG, agent runtime/memory/session and control-plane metadata are separate scopes. Sovereignty is broader than residency. Provider-native residency statements apply only to stated content/features/operations. ZDR, retention and residency are separate."
    }
  ],
  "human_url": "/tools/ea-062-data-residency-sovereign-ai",
  "markdown_url": "/agent/article.md?path=%2Ftools%2Fea-062-data-residency-sovereign-ai",
  "json_url": "/agent/article.json?path=%2Ftools%2Fea-062-data-residency-sovereign-ai"
}