{ "format": "agent-article-v0", "article_id": "EA-091", "canonical_url": "/tools/ea-091-multi-cloud-ai", "page_type": "reference", "claim_ids": [], "evidence_ids": [ "EVD-EA-091-URL-5054E58070D9", "EVD-EA-091-URL-DDD1ABD2CC4F", "EVD-EA-091-URL-2595F3D251B5", "EA-091-R11-RESEARCH", "EA-091-R11-WEB-READBACK" ], "unknown_ids": [ "EA-091-UNKNOWN-01", "EA-091-UNKNOWN-CURRENTNESS" ], "operational_object_ids": [], "provider": [], "models": [], "plans": [], "surfaces": [], "regions": [], "current_status": "UNKNOWN", "observation_status": "SPEC_ONLY", "freshness": "UNKNOWN", "last_verified": null, "supersedes": [], "superseded_by": [], "provenance": [ "COMM-082-EA0091", "SRC-EA-091-URL-5054E58070D9", "SRC-EA-091-URL-DDD1ABD2CC4F", "SRC-EA-091-URL-2595F3D251B5", "WEBBODY-EA0091-R8-82C0526B" ], "article_sources": [ { "id": "EVD-EA-091-URL-5054E58070D9", "evidence_class": "RESEARCH", "title": "1. [official spec / PRODUCT_VOLATILE] Amazon Bedrock, “Route model inference requests across AWS Regions with cross-Region inference”, AWS, accessed 2026-09-16.", "href": "https://docs.aws.amazon.com/bedrock/latest/userguide/cross-region-inference.html", "supports": [], "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。", "origin_class": "SOURCE_PACKET_REFERENCE", "source_or_experiment_ids": [ "SRC-EA-091-URL-5054E58070D9" ], "supporting_locators": [ "EVIDENCE TABLE", "1. [official spec / PRODUCT_VOLATILE] Amazon Bedrock, “Route model inference requests across AWS Regions with cross-Region inference”, AWS, accessed 2026-09-16. https://docs.aws.amazon.com/bedrock/latest/userguide/cross-region-inference.html" ], "scope": "EVIDENCE TABLE", "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED" }, { "id": "EVD-EA-091-URL-DDD1ABD2CC4F", "evidence_class": "RESEARCH", "title": "2. [official spec / PRODUCT_VOLATILE] Amazon Bedrock, “Supported Regions and models for inference profiles”, AWS, accessed 2026-09-16.", "href": "https://docs.aws.amazon.com/us_en/bedrock/latest/userguide/inference-profiles-support.html", "supports": [], "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。", "origin_class": "SOURCE_PACKET_REFERENCE", "source_or_experiment_ids": [ "SRC-EA-091-URL-DDD1ABD2CC4F" ], "supporting_locators": [ "EVIDENCE TABLE", "2. [official spec / PRODUCT_VOLATILE] Amazon Bedrock, “Supported Regions and models for inference profiles”, AWS, accessed 2026-09-16. https://docs.aws.amazon.com/us_en/bedrock/latest/userguide/inference-profiles-support.html" ], "scope": "EVIDENCE TABLE", "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED" }, { "id": "EVD-EA-091-URL-2595F3D251B5", "evidence_class": "RESEARCH", "title": "3. [official product docs / PRODUCT_VOLATILE] “Use open models using Model as a Service (MaaS)”, Google Cloud, last updated 2026-01-02, accessed 2026-09-16.", "href": "https://docs.cloud.google.com/vertex-ai/generative-ai/docs/open-models/use-maas", "supports": [], "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。", "origin_class": "SOURCE_PACKET_REFERENCE", "source_or_experiment_ids": [ "SRC-EA-091-URL-2595F3D251B5" ], "supporting_locators": [ "EVIDENCE TABLE", "3. [official product docs / PRODUCT_VOLATILE] “Use open models using Model as a Service (MaaS)”, Google Cloud, last updated 2026-01-02, accessed 2026-09-16. https://docs.cloud.google.com/vertex-ai/generative-ai/docs/open-models/use-maas" ], "scope": "EVIDENCE TABLE", "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED" }, { "id": "EA-091-R11-RESEARCH", "evidence_class": "RESEARCH", "title": "EA-091 監査済みresearch / canonical revision binding", "supports": [ "- provider abstractionは「同じpromptを別APIへ送れる」だけでは不十分。model ID、context/tool/schema、streaming、structured output、safety、retention、region、quota、cost、latency、eval profileをrouting metadataにする。\n- AWS自身のcross-Regionでもdestination Region・SCP/IAM・data residencyがrouting correctnessを左右す。multi-cloudではこの差がさらに大きい。\n- portabilityの単位はproviderではなくcapability contract。tool use、JSON schema、vision、batch、cache等をfeature flagとして扱う。" ], "limit": "canonical監査・revision bindingの存在を示す。外部ソースcurrentnessが本文またはcontrol-planeで確定していない場合は、currentnessをUNKNOWNのまま保持する。", "origin_class": "AUDITED_CANONICAL_RESEARCH_PACKET", "source_or_experiment_ids": [ "COMM-082-EA0091" ], "supporting_locators": [ "COMM-082-EA0091", "EA-091-R5-LEGACY-MIGRATION-20261008-R1", "content/staging/EA-091.md" ], "scope": "監査済みEA本文・canonical revision・既存Source Graph relationの範囲。欠損currentnessは推測で閉じない。", "provenance_status": "AUDIT_PASS_CANONICAL_BINDING" }, { "id": "EA-091-R11-WEB-READBACK", "evidence_class": "IMPL", "title": "EA-091 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-EA0091-R8-82C0526B" ], "supporting_locators": [ "WEBBODY-EA0091-R8-82C0526B", "content/staging/EA-091.md", "EA-091-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": "単一provider依存を減らし、model capability・価格・地域・quota・障害条件に応じてrouteできる一方、API互換性だけではsemantic equivalence、data residency、tool semantics、safety policy、observability、failover correctnessは保証されない。公開後版では「providerを複数登録する」から一段上のportable control planeが必要。" }, { "heading": "SCOPE_ROUTING", "text": "Enterprise AI Core / provider mapping / interoperability / reliability / governance / implementation" }, { "heading": "CLAIM_OR_RESEARCH_QUESTION", "text": "Multi-cloud AIは、共通request envelopeだけでなく、capability・policy・data-boundary・evaluation・fallback semanticsを明示したrouting contractとして設計すべきか。" }, { "heading": "EVIDENCE TABLE", "text": "1. [official spec / PRODUCT_VOLATILE] Amazon Bedrock, “Route model inference requests across AWS Regions with cross-Region inference”, AWS, accessed 2026-09-16. https://docs.aws.amazon.com/bedrock/latest/userguide/cross-region-inference.html — cross-Region profileは複数Regionへrouteし、Geo/Globalでdata-residency条件が異なる。CloudTrailのinferenceRegionで処理Regionを追跡可能。 relation=support/context.\n2. [official spec / PRODUCT_VOLATILE] Amazon Bedrock, “Supported Regions and models for inference profiles”, AWS, accessed 2026-09-16. https://docs.aws.amazon.com/us_en/bedrock/latest/userguide/inference-profiles-support.html — model/profileごとにsource/destination RegionとIDが異なり、SCP/IAM制約で失敗し得る。 relation=limit/context.\n3. [official product docs / PRODUCT_VOLATILE] “Use open models using Model as a Service (MaaS)”, Google Cloud, last updated 2026-01-02, accessed 2026-09-16. https://docs.cloud.google.com/vertex-ai/generative-ai/docs/open-models/use-maas — Model Garden/MaaSはGoogle/partner/open modelを扱い、API enablement等のgateを持つ。 relation=support/context." }, { "heading": "FINDINGS", "text": "- provider abstractionは「同じpromptを別APIへ送れる」だけでは不十分。model ID、context/tool/schema、streaming、structured output、safety、retention、region、quota、cost、latency、eval profileをrouting metadataにする。\n- AWS自身のcross-Regionでもdestination Region・SCP/IAM・data residencyがrouting correctnessを左右す。multi-cloudではこの差がさらに大きい。\n- portabilityの単位はproviderではなくcapability contract。tool use、JSON schema、vision、batch、cache等をfeature flagとして扱う。" }, { "heading": "LIMITS / COUNTEREVIDENCE / FAILURE ENVELOPE", "text": "同名/同系列modelでもhosted providerごとにrevision、system wrapping、safety、tool implementation、quota、loggingが一致するとは限らない。failover先が応答したことは業務上のequivalenceを意味しない。shared dependency（同一upstream model vendor、DNS、identity、network、common SDK）によりmulti-cloudでもcorrelated failureが成立する。" }, { "heading": "AVAILABILITY_GATES", "text": "provider/model/region/account/project、API enablement、quota、contract、data residency、IAM/SCP、egress、secret/KMS、model availability。current matrixはPRODUCT_VOLATILE。" }, { "heading": "IMPLEMENTATION_STATE", "text": "実装可能。将来Core候補 `MULTI_CLOUD_AI_ROUTING_CONTRACT`: request_class, required_capabilities, data_class/residency, preferred/fallback provider+model+region, policy version, timeout budget, retry/failover budget, eval profile, cost ceiling, trace ID, selected route, route reason, result status。" }, { "heading": "BENCHMARK_OR_EVAL", "text": "同一frozen fixtureを各routeでshadow評価し、task quality/tool correctness/schema compliance/refusal behavior/latency/costを比較。単一aggregate scoreでequivalence判定しない。" }, { "heading": "SECURITY / PRIVACY / AUDIT / COST / OPERABILITY", "text": "route変更でdata processor/region/logging/retentionが変わり得るため、route decisionをaudit artifact化。secretはprovider別。costはfallback amplificationとegressを含める。" }, { "heading": "SAFE_WORDING_FOR_FUTURE_BOOK", "text": "「Multi-cloud AIは可用性と選択肢を増やせるが、provider間の意味的・運用的同一性を保証しない。routeごとにcapability、data boundary、policy、評価、監査を固定する。」" }, { "heading": "UPDATE_WORK_HANDOFF", "text": "EA-092 DR/BCPと結合し、route tableを通常時最適化と障害時failoverの二用途に分離。provider/model/region matrixは公開直前に再pin。" }, { "heading": "OPEN_UNKNOWN / STOP_CONDITION", "text": "Azure/Vertex/AWS/OpenAI/Anthropic各routeの2026年公開時点model/revision/region/SLA/retention matrixは再確認必須。tenant実測なし。Core contractと主要failure boundary確立につき本RUN停止条件充足。\n\n\n---\n\n---" }, { "heading": "AUDITED_CURRENTNESS_BOUNDARY", "text": "Bedrock Geographic and Global cross-Region routing have distinct residency semantics; cross-Region is not cross-provider portability and destination/model/IAM sets are version-specific." } ], "human_url": "/tools/ea-091-multi-cloud-ai", "markdown_url": "/agent/article.md?path=%2Ftools%2Fea-091-multi-cloud-ai", "json_url": "/agent/article.json?path=%2Ftools%2Fea-091-multi-cloud-ai" }