{ "format": "agent-article-v0", "article_id": "EA-046", "canonical_url": "/tools/ea-046-ai-gateway", "page_type": "reference", "claim_ids": [], "evidence_ids": [ "EA-046-R11-RESEARCH", "EA-046-R11-WEB-READBACK" ], "unknown_ids": [ "EA-046-UNKNOWN-01", "EA-046-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-038-EA0046", "WEBBODY-EA0046-R8-08FB04F3" ], "article_sources": [ { "id": "EA-046-R11-RESEARCH", "evidence_class": "RESEARCH", "title": "EA-046 監査済みresearch / canonical revision binding", "supports": [ "AI GatewayはAI trafficを共通のcontrol/enforcement pointへ集約する実装パターンとして扱う。単一の標準化済み製品カテゴリではない。共通Coreでは routing/fallback、provider/model abstraction、credential/auth boundary、rate/quota/budget control、AI-specific telemetry、policy hooks、MCP/tool mediationを分離して記述する。" ], "limit": "canonical監査・revision bindingの存在を示す。外部ソースcurrentnessが本文またはcontrol-planeで確定していない場合は、currentnessをUNKNOWNのまま保持する。", "origin_class": "AUDITED_CANONICAL_RESEARCH_PACKET", "source_or_experiment_ids": [ "COMM-038-EA0046" ], "supporting_locators": [ "COMM-038-EA0046", "EA-046-R5-LEGACY-MIGRATION-20261008-R1", "content/staging/EA-046.md" ], "scope": "監査済みEA本文・canonical revision・既存Source Graph relationの範囲。欠損currentnessは推測で閉じない。", "provenance_status": "AUDIT_PASS_CANONICAL_BINDING" }, { "id": "EA-046-R11-WEB-READBACK", "evidence_class": "IMPL", "title": "EA-046 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-EA0046-R8-08FB04F3" ], "supporting_locators": [ "WEBBODY-EA0046-R8-08FB04F3", "content/staging/EA-046.md", "EA-046-R5-LEGACY-MIGRATION-20261008-R1" ], "scope": "R9/R10 canonical readback後のProduction生成時body identity。", "provenance_status": "CANONICAL_READBACK_BODY_HASH_MATCH" } ], "research_sections": [ { "heading": "Public claim", "text": "AI GatewayはAI trafficを共通のcontrol/enforcement pointへ集約する実装パターンとして扱う。単一の標準化済み製品カテゴリではない。共通Coreでは routing/fallback、provider/model abstraction、credential/auth boundary、rate/quota/budget control、AI-specific telemetry、policy hooks、MCP/tool mediationを分離して記述する。" }, { "heading": "Control surfaces", "text": "- ROUTING_FALLBACK: model/provider route、conditional route、fallback。\n- PROVIDER_MODEL_ABSTRACTION: provider translation、model virtualization等。\n- CREDENTIAL_AUTH_BOUNDARY: credential mediationとbackend security policy。\n- RATE_QUOTA_BUDGET: rate、quota、budget enforcement。\n- AI_TELEMETRY: request、token、cost、error、latency等。\n- POLICY_HOOKS: request/response policy、redaction等。\n- MCP_TOOL_MEDIATION: MCP/tool traffic routingとprotocol handling。\n\nこれらは実装パターンの分解であり、全AI Gateway製品が全機能を備えるとは主張しない。" }, { "heading": "Currentness boundary — 2026-09-28", "text": "Cloudflare current Limits pageは2026-09-24変更を反映する。旧numeric log-limit wordingはcurrent source readbackなしに公開固定しない。CloudflareとEnvoyの二系統は独立にsubstantiatedだが、三系統以上のfeature-parity comparisonが完了したとは扱わない。" }, { "heading": "Failure envelope", "text": "- Gateway配置だけでpolicy enforcementやsecurityを保証しない。\n- Gatewayを迂回するdirect provider/tool pathが残ればcontrol coverageは不完全になり得る。\n- translation/parser差、protocol version差、streaming/tool-call semantics差がpolicy bypassや破損を生み得る。\n- 集中化はsingle point of failure / high-blast-radius compromiseを作り得る。\n- logging/telemetryはprompt、tool argument、response等のsensitive dataを保持し得るため、retention/redaction/access controlを別に設計する。\n- cache、semantic cache、routing、billing、GUI等の個別機能を全製品共通へ一般化しない。\n- provider/product limits、plan、region、logging backend、retention、pricingはPRODUCT_VOLATILE。\n- Gatewayの存在を「全AI経路が統制済み」の証明にしない。" }, { "heading": "Availability gates", "text": "provider/product / deployment topology / plan-region / supported upstream providers-models / auth mode / logging backend / retention / rate-budget primitive / MCP-tool support / protocol version / streaming / cache / organization policy / direct-path bypass inventoryを分離する。" }, { "heading": "Implementation pattern", "text": "APPLICATION / AGENT → AI GATEWAY → auth/credential boundary → route/provider translation → rate/quota/budget policy → request/response policy hooks → provider/model or MCP/tool backend → telemetry/readback。\n\ndirect pathが存在する場合はBYPASS_PATHとして明示し、Gateway coverageへ暗黙算入しない。" }, { "heading": "TEST_PROFILE", "text": "UNEXECUTED。非機密fixtureでprimary provider success、fallback route、rate/quota/budget deny、malformed/ambiguous MCP or tool message、provider translation差、gateway outage、direct-path bypass attempt、logging/redaction、retry時のduplicate side effect防止、policy update後のreadbackを検証する。実Production credential、実決済、実外部副作用は使用しない。未実施結果を推測しない。" }, { "heading": "OPEN_UNKNOWN", "text": "publication-timeの各製品feature matrix、limits、pricing、plan/region availability、managed gateway内部translation/parser、tenant固有logging/retention/data residency、direct provider path封鎖、三系統以上のcurrent feature-parity comparison。UNKNOWNを推測で閉じない。" }, { "heading": "AUDITED_BOUNDARY", "text": "AI Gateway is an implementation pattern, not a standardized single category. Current packet independently supports Cloudflare + Envoy only; do not represent three-family parity as completed. Preserve Cloudflare limits/log behavior currentness, Envoy security/version gate, privacy/logging limits, and all OPEN_UNKNOWN." } ], "human_url": "/tools/ea-046-ai-gateway", "markdown_url": "/agent/article.md?path=%2Ftools%2Fea-046-ai-gateway", "json_url": "/agent/article.json?path=%2Ftools%2Fea-046-ai-gateway" }