{
  "items": [
    {
      "id": "plugin-format-scope",
      "topic": "Agent Plugins support in ChatGPT and Codex",
      "sourceA": {
        "id": "S-050",
        "claim": "The Agent Plugins compatible-client list names ChatGPT and Codex for the open package format.",
        "href": "https://agent-plugins.org/clients"
      },
      "sourceB": {
        "id": "S-090",
        "claim": "OpenAI first-party documentation describes a vendor package centered on .codex-plugin/plugin.json.",
        "href": "https://learn.chatgpt.com/docs/build-plugins"
      },
      "handling": "Keep open-standard and vendor-native package assertions separate; do not infer package-level conformance from either statement alone.",
      "status": "open"
    },
    {
      "id": "mcp-brand-claim",
      "topic": "MCP support as a single claim",
      "sourceA": {
        "id": "S-019",
        "claim": "MCP defines independent client and server primitives, transports, and utilities.",
        "href": "https://modelcontextprotocol.io/specification/2025-11-25"
      },
      "sourceB": {
        "id": "S-136",
        "claim": "Zed documents implemented MCP primitives and missing coverage separately.",
        "href": "https://zed.dev/docs/ai/mcp"
      },
      "handling": "Decompose MCP into atomic features and never publish one brand-level boolean.",
      "status": "resolved-by-model"
    },
    {
      "id": "hosted-version-identity",
      "topic": "Hosted product versioning",
      "sourceA": {
        "id": "method",
        "claim": "Browser compatibility normally targets enumerable product releases.",
        "href": "https://github.com/mdn/browser-compat-data/blob/main/schemas/compat-data-schema.md"
      },
      "sourceB": {
        "id": "S-088",
        "claim": "Hosted agent surfaces can change without a stable public build identifier.",
        "href": "https://learn.chatgpt.com/docs/extend/mcp"
      },
      "handling": "Use dated hosted observations and evidence timestamps; never fabricate releases.",
      "status": "open"
    },
    {
      "id": "plugin-hooks-portability",
      "topic": "Plugin hooks portability",
      "sourceA": {
        "id": "S-113",
        "claim": "VS Code supports host-specific plugin namespaces and compatible hook shapes.",
        "href": "https://code.visualstudio.com/docs/agent-customization/agent-plugins"
      },
      "sourceB": {
        "id": "S-053",
        "claim": "Agent Plugins 1.0 does not define hooks as a portable core component.",
        "href": "https://agent-plugins.org/specification/1.0/extensions"
      },
      "handling": "Represent hooks as host extensions instead of portable Agent Plugins core support.",
      "status": "resolved-by-model"
    },
    {
      "id": "gemini-acp-revision",
      "topic": "Gemini ACP naming and version",
      "sourceA": {
        "id": "S-132",
        "claim": "Gemini CLI exposes an ACP mode in its configuration surface.",
        "href": "https://github.com/google-gemini/gemini-cli/blob/main/docs/reference/configuration.md"
      },
      "sourceB": {
        "id": "S-065",
        "claim": "ACP evolves independently and remote transport work remains in progress.",
        "href": "https://github.com/agentclientprotocol/agent-client-protocol/discussions"
      },
      "handling": "Require protocol revision, transport, and role instead of treating a flag as full conformance.",
      "status": "open"
    }
  ],
  "openQuestions": [
    {
      "id": "Q-001",
      "title": "Hosted release identity",
      "question": "How should continuously deployed web and cloud-agent surfaces expose immutable compatibility targets?",
      "owner": "data-model",
      "priority": "high"
    },
    {
      "id": "Q-002",
      "title": "Normative feature profiles",
      "question": "Who approves required child features for a parent compatibility label?",
      "owner": "governance",
      "priority": "high"
    },
    {
      "id": "Q-003",
      "title": "Conformance authority",
      "question": "Which badge language may apply to project tests, vendor attestations, and community reproductions?",
      "owner": "governance",
      "priority": "high"
    },
    {
      "id": "Q-004",
      "title": "Plan and policy matrices",
      "question": "How far should public grids split by plan, policy, region, feature flag, and administrator configuration?",
      "owner": "ux",
      "priority": "medium"
    },
    {
      "id": "Q-005",
      "title": "Remote authorization safety",
      "question": "What credential and isolation model is acceptable for automated OAuth and remote MCP tests?",
      "owner": "security",
      "priority": "high"
    },
    {
      "id": "Q-006",
      "title": "Proprietary feature scope",
      "question": "Should vendor-native rules, hooks, and package formats be peers or a separate host-extension layer?",
      "owner": "taxonomy",
      "priority": "medium"
    },
    {
      "id": "Q-007",
      "title": "Evidence freshness",
      "question": "Which expiry windows apply to hosted observations and version-pinned local claims?",
      "owner": "operations",
      "priority": "medium"
    },
    {
      "id": "Q-008",
      "title": "Licensing",
      "question": "Which sourced facts may be redistributed and which should only be paraphrased and cited?",
      "owner": "legal",
      "priority": "high"
    },
    {
      "id": "Q-009",
      "title": "Community reports",
      "question": "What corroboration is required before a report affects the public support state?",
      "owner": "governance",
      "priority": "medium"
    },
    {
      "id": "Q-010",
      "title": "Test fixtures",
      "question": "Can standards projects share or review fixtures so tests match normative intent?",
      "owner": "partnerships",
      "priority": "medium"
    }
  ]
}