Proposal: evidence-backed capability matrix across AgenTrust projects #104

Contribution proposal

The cross-repository contribution review identified a need for a public capability matrix that distinguishes implemented behavior, tested behavior and prerequisites. This is a scoped documentation proposal for maintainer review, not a claim of platform equivalence.

Proposed deliverable

A website table with project/capability, implementation source and revision, executable validation source, evidence class (synthetic fixture, captured artifact, live run), limitations, and last verified date. Link to canonical repository material rather than copying normative requirements.

Acceptance criteria

• Every supported claim has a source and exact revision or released version.
• Synthetic fixtures, captured artifacts and live runs are visibly distinct; an implementation alone does not imply independent validation.
• Unsupported and untested paths are explicit; no equivalence inferred between hardware vendors.
• Include a reproducible link/source validation check and a documented owner/update process.
• Preserve private security work and exclude credentials, private endpoints and unpublished evidence.

First slice

Agree the table schema and one reviewed WCM profile plus one telemetry example before expanding across repositories. Telemetry PR #99 supplies SDK fault-test evidence only, not collector or durable-backend acceptance: agentrust-io/agentrust-telemetry#99 .

Decision needed

Maintainer selection of page location, claim owner and acceptable evidence sources. Implementation should follow that decision; this issue does not close underlying hardware or interoperability work.