{
  "format": "agent-article-v0",
  "article_id": "EA-031",
  "canonical_url": "/tools/ea-031-ai",
  "page_type": "update_note",
  "claim_ids": [],
  "evidence_ids": [
    "EA-031-R11-RESEARCH",
    "EA-031-R11-WEB-READBACK"
  ],
  "unknown_ids": [
    "EA-031-UNKNOWN-01",
    "EA-031-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-188-EA0031",
    "WEBBODY-EA0031-R8-59CC8B7D"
  ],
  "article_sources": [
    {
      "id": "EA-031-R11-RESEARCH",
      "evidence_class": "RESEARCH",
      "title": "EA-031 監査済みresearch / canonical revision binding",
      "supports": [
        "AI更新の互換性は、単一のversion番号やAPI疎通ではなく、wire/API、schema/tool、instruction、model behavior、state/storage、interoperability/protocol、operational、economic、governance/auditの九つの変更面を分離して評価する。API requestが成功することはWIRE_API_COMPATの一部しか確立しない。"
      ],
      "limit": "canonical監査・revision bindingの存在を示す。外部ソースcurrentnessが本文またはcontrol-planeで確定していない場合は、currentnessをUNKNOWNのまま保持する。",
      "origin_class": "AUDITED_CANONICAL_RESEARCH_PACKET",
      "source_or_experiment_ids": [
        "COMM-188-EA0031"
      ],
      "supporting_locators": [
        "COMM-188-EA0031",
        "EA-031-R5-LEGACY-MIGRATION-20261008-R1",
        "content/staging/EA-031.md"
      ],
      "scope": "監査済みEA本文・canonical revision・既存Source Graph relationの範囲。欠損currentnessは推測で閉じない。",
      "provenance_status": "AUDIT_PASS_CANONICAL_BINDING"
    },
    {
      "id": "EA-031-R11-WEB-READBACK",
      "evidence_class": "IMPL",
      "title": "EA-031 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-EA0031-R8-59CC8B7D"
      ],
      "supporting_locators": [
        "WEBBODY-EA0031-R8-59CC8B7D",
        "content/staging/EA-031.md",
        "EA-031-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更新の互換性は、単一のversion番号やAPI疎通ではなく、wire/API、schema/tool、instruction、model behavior、state/storage、interoperability/protocol、operational、economic、governance/auditの九つの変更面を分離して評価する。API requestが成功することはWIRE_API_COMPATの一部しか確立しない。\n\nこの九層compatibility modelとCOMPATIBILITY_MANIFESTはDICTIONARY PROPOSALであり、外部標準の固定taxonomyではない。"
    },
    {
      "heading": "Nine compatibility layers",
      "text": "1. WIRE_API_COMPAT — endpoint、auth、request/response fields、API version、streaming/error semantics。\n2. SCHEMA_TOOL_COMPAT — function/tool schema、structured output、tool-result format、protocol feature subset。\n3. INSTRUCTION_COMPAT — system/developer/user instruction、prompt template、reserved semantics。\n4. BEHAVIOR_COMPAT — task accuracy、refusal/safety boundary、style、reasoning/tool-selection、citation/source behavior。\n5. STATE_COMPAT — conversation/session、memory、files/index、checkpoint等の継続性。\n6. INTEROP_COMPAT — protocol revision、extension、transport、client/server negotiation。\n7. OPERATIONAL_COMPAT — latency、rate/quota、region、availability、concurrency。\n8. ECONOMIC_COMPAT — price、token/accounting、cache/batch discount、quota model。\n9. GOVERNANCE_AUDIT_COMPAT — logs、retention、admin controls、approval/audit evidence。"
    },
    {
      "heading": "Compatibility manifest",
      "text": "provider / exact model ID or snapshot + alias / endpoint and API version / SDK-library version / tool-function schema version / protocol revision + supported feature subset / system-instruction-prompt-template version / context-output-token constraints / structured-output contract / eval fixture-scorer-judge versions / safety-policy assumptions / organization-plan-region gates / pricing-rate-limit-cache assumptions。"
    },
    {
      "heading": "Version and lifecycle boundaries",
      "text": "OpenAIのsnapshot claimはspecific model versionのperformance/behavior scopeに限定し、provider policy、SDK、quota、price、region、endpoint lifecycleまで固定されるとは扱わない。\n\nAnthropicのAPI versionとmodel lifecycleは別軸として扱う。固定API versionだけでmodel retirementを回避できるとは扱わない。\n\nGeminiのstable / preview / latest / experimentalはprovider-specific semanticsとして保持する。`latest`のhot-swap性を全providerのaliasへ一般化しない。解決先model IDが取得不能ならUNKNOWNとする。\n\nMCPはrevision、feature subset、extension、transportを記録し、単なる「MCP compatible」を互換性証明として扱わない。2026-07-28 revisionはbreaking protocol revisionとformal minimum twelve-month deprecation windowを伴うcurrent exampleとして扱う。"
    },
    {
      "heading": "Change classes",
      "text": "ADDITIVE / BEHAVIORAL / BREAKING / AVAILABILITY / ECONOMIC / GOVERNANCE_POLICY。1更新が複数classへ属してよい。providerのnon-breaking表現をtask-level behavioral compatibilityへ自動拡張しない。"
    },
    {
      "heading": "Failure envelope",
      "text": "snapshot/model pinningはfull-stack reproducibility guaranteeではない。protocol/API互換はsemantic compatibilityを証明しない。retirement/deprecationによりpinningは有限寿命になり得る。stochastic outputではbyte-for-byte equalityを標準互換条件にしない。2023 Chen et al.のhistorical evidenceをcurrent-product guaranteeへ使用しない。public docsは個別tenant/region/planの実挙動証明ではない。benchmark/fixture/scorer変更時はEA-030のFROZEN/CURRENT/BRIDGE seriesでtest changeとmodel changeを分離する。"
    },
    {
      "heading": "Availability gates",
      "text": "exact snapshot/model IDの公開有無、direct provider API vs partner platform、stable/preview/latest/experimental、organization plan、region、rate tier、feature flag、admin policy、protocol revision/transport/extensionのclient/server双方対応をproduct existenceとは別に記録する。"
    },
    {
      "heading": "Evidence / provenance",
      "text": "AUTHORITY COMM-188-EA0031。OpenAI GPT-5.1 model docs、Anthropic API versioning/model deprecations、Gemini model-version naming、MCP 2026-07-28 specification、Chen et al. historical researchを根拠として使用する。provider固有version/lifecycle factはPRODUCT_VOLATILEとしてas-ofを保持する。"
    },
    {
      "heading": "TEST_PROFILE",
      "text": "UNEXECUTED。旧新versionで同一非機密fixtureを実行し、schema/tool exactness、task score、failure rate、side effect、latency/cost、availabilityを層別比較する。fixture/scorer自体が変わる場合はbridge runを置く。未実施結果を推測しない。"
    },
    {
      "heading": "OPEN_UNKNOWN",
      "text": "tenant/region/plan固有挙動、非公開alias解決先、provider内部routing、安全policy/backend変更、partner platform固有retirement schedule、protocol feature subsetの実装差。UNKNOWNを推測で閉じない。"
    }
  ],
  "human_url": "/tools/ea-031-ai",
  "markdown_url": "/agent/article.md?path=%2Ftools%2Fea-031-ai",
  "json_url": "/agent/article.json?path=%2Ftools%2Fea-031-ai"
}