---
title: "Contradictions and open questions"
canonical: "https://canmyagentuse.com/contradictions"
contentKind: "page"
locale: "en"
description: "Visible evidence conflicts, scope mismatches, and unresolved governance questions."
llmSummary: "Visible evidence conflicts, scope mismatches, and unresolved governance questions."
publishedAt: null
updatedAt: null
verifiedAt: null
tags: []
---

# Contradictions and open questions

Visible evidence conflicts, scope mismatches, and unresolved governance questions.

- HTML: https://canmyagentuse.com/contradictions
- JSON: https://canmyagentuse.com/api/v1/contradictions.json
- Markdown: https://canmyagentuse.com/contradictions.md

Credible sources can disagree because they target different roles, revisions, formats, or product surfaces. Conflicts remain visible until resolved.

## Contradiction ledger

### Agent Plugins support in ChatGPT and Codex

- ID: `plugin-format-scope`
- Status: open
- [S-050](https://agent-plugins.org/clients): The Agent Plugins compatible-client list names ChatGPT and Codex for the open package format.
- [S-090](https://learn.chatgpt.com/docs/build-plugins): OpenAI first-party documentation describes a vendor package centered on .codex-plugin/plugin.json.
- Handling: Keep open-standard and vendor-native package assertions separate; do not infer package-level conformance from either statement alone.

### MCP support as a single claim

- ID: `mcp-brand-claim`
- Status: resolved-by-model
- [S-019](https://modelcontextprotocol.io/specification/2025-11-25): MCP defines independent client and server primitives, transports, and utilities.
- [S-136](https://zed.dev/docs/ai/mcp): Zed documents implemented MCP primitives and missing coverage separately.
- Handling: Decompose MCP into atomic features and never publish one brand-level boolean.

### Hosted product versioning

- ID: `hosted-version-identity`
- Status: open
- [method](https://github.com/mdn/browser-compat-data/blob/main/schemas/compat-data-schema.md): Browser compatibility normally targets enumerable product releases.
- [S-088](https://learn.chatgpt.com/docs/extend/mcp): Hosted agent surfaces can change without a stable public build identifier.
- Handling: Use dated hosted observations and evidence timestamps; never fabricate releases.

### Plugin hooks portability

- ID: `plugin-hooks-portability`
- Status: resolved-by-model
- [S-113](https://code.visualstudio.com/docs/agent-customization/agent-plugins): VS Code supports host-specific plugin namespaces and compatible hook shapes.
- [S-053](https://agent-plugins.org/specification/1.0/extensions): Agent Plugins 1.0 does not define hooks as a portable core component.
- Handling: Represent hooks as host extensions instead of portable Agent Plugins core support.

### Gemini ACP naming and version

- ID: `gemini-acp-revision`
- Status: open
- [S-132](https://github.com/google-gemini/gemini-cli/blob/main/docs/reference/configuration.md): Gemini CLI exposes an ACP mode in its configuration surface.
- [S-065](https://github.com/agentclientprotocol/agent-client-protocol/discussions): ACP evolves independently and remote transport work remains in progress.
- Handling: Require protocol revision, transport, and role instead of treating a flag as full conformance.

## Open governance questions

- `Q-001` **Hosted release identity** — How should continuously deployed web and cloud-agent surfaces expose immutable compatibility targets? Owner: data-model; priority: high.
- `Q-002` **Normative feature profiles** — Who approves required child features for a parent compatibility label? Owner: governance; priority: high.
- `Q-003` **Conformance authority** — Which badge language may apply to project tests, vendor attestations, and community reproductions? Owner: governance; priority: high.
- `Q-004` **Plan and policy matrices** — How far should public grids split by plan, policy, region, feature flag, and administrator configuration? Owner: ux; priority: medium.
- `Q-005` **Remote authorization safety** — What credential and isolation model is acceptable for automated OAuth and remote MCP tests? Owner: security; priority: high.
- `Q-006` **Proprietary feature scope** — Should vendor-native rules, hooks, and package formats be peers or a separate host-extension layer? Owner: taxonomy; priority: medium.
- `Q-007` **Evidence freshness** — Which expiry windows apply to hosted observations and version-pinned local claims? Owner: operations; priority: medium.
- `Q-008` **Licensing** — Which sourced facts may be redistributed and which should only be paraphrased and cited? Owner: legal; priority: high.
- `Q-009` **Community reports** — What corroboration is required before a report affects the public support state? Owner: governance; priority: medium.
- `Q-010` **Test fixtures** — Can standards projects share or review fixtures so tests match normative intent? Owner: partnerships; priority: medium.