Source conflicts
Contradictions and open questions
Public sources can disagree because they describe different roles, revisions, package formats, or products. The catalog keeps each conflict visible until a source or schema change resolves it.
MCP support as a single claim
Hosted product versioning
Plugin hooks portability
Gemini ACP naming and version
Needs a decision
Open questions
These questions do not block publication. They do prevent a general "verified" claim.
Q-001Hosted release identitydata-model · highHow should continuously deployed web and cloud-agent surfaces expose immutable compatibility targets?
Q-002Normative feature profilesgovernance · highWho approves required child features for a parent compatibility label?
Q-003Conformance authoritygovernance · highWhich badge language may apply to project tests, vendor attestations, and community reproductions?
Q-004Plan and policy matricesux · mediumHow far should public grids split by plan, policy, region, feature flag, and administrator configuration?
Q-005Remote authorization safetysecurity · highWhat credential and isolation model is acceptable for automated OAuth and remote MCP tests?
Q-006Proprietary feature scopetaxonomy · mediumShould vendor-native rules, hooks, and package formats be peers or a separate host-extension layer?
Q-007Evidence freshnessoperations · mediumWhich expiry windows apply to hosted observations and version-pinned local claims?
Q-008Licensinglegal · highWhich sourced facts may be redistributed and which should only be paraphrased and cited?
Q-009Community reportsgovernance · mediumWhat corroboration is required before a report affects the public support state?
Q-010Test fixturespartnerships · mediumCan standards projects share or review fixtures so tests match normative intent?