Capability matrix: claims versus what has actually run
This page is a standalone English reference and pairs with no Chinese page. It answers the implementer’s first question — which implementation covers which capability — without ever turning a local result or an author’s statement into a compatibility verdict.
How to read a cell
Every cell is one of exactly three evidence states, and they do not upgrade each other:
- tested (scope) — this site ran it at a pinned revision; the scope states what was and was not exercised.
- claimed (evidence) — the project’s own README/docs/tests assert it at the pinned revision, with the evidence location cited. A claim, not a result.
- unknown — no evidence either way. Unknown never means incompatible.
A row with tested in Discovery and unknown in OAuth says exactly that: discovery conformance was verified here, OAuth was not. It is not a score and not a certification. No cell in the community rows was executed by this site.
The matrix
| Implementation | Protocol revision | Discovery | Session | OAuth | APIs | Revocation |
|---|---|---|---|---|---|---|
| Official spec + validator, this site’s fixture | 1.0 @ 65618532 | tested (schema-valid fixture survey; localhost domain deviation documented) | unknown — not covered by the fixture | unknown — not covered | unknown — not covered | unknown — not covered |
adewale/pda @ d9323daa (Apache-2.0, alpha) | 0.4; pre-release 1.0 draft retrieved before the official release, not deployed | claimed (README: fetches poppy.json + resource/OAuth metadata, validator checks) | claimed (README conformance table step 3: per-request Poppy-Session via delegated key, “works in tests”) | claimed (README: sign-in on the company’s page; live sign-in/out at 0.1–0.2) | claimed (README: “calls its APIs”; print-with-poppy interop scenarios at 0.4, author-reported) | unknown — no revocation statement at 0.4 found in README |
datalayer/personal-agent-protocol @ 3a6f345c (BSD-3-Clause) | 0.4 as published; pre-1.0 draft as SDK default | claimed (README: DiscoveryClient reads /.well-known/poppy.json) | claimed (README five-step model: signed-out session, per-request Session JWT) | claimed (README: company authorization page, refresh/access tokens; sequence diagram) | claimed (README: converse and continue with access token) | claimed (README test section: sign-out tests, refresh refused after sign-out) |
richardanaya/pi-poppy @ 11ea1063 (MIT) | 0.1 draft (explicit) | claimed (README tools: poppy_discover) | claimed (README: opens a signed-out session; session tool group) | claimed (README: signs the user in; per-user per-company DPoP keys and account tokens) | claimed (README: calls the company’s APIs; chat/API/MCP per company) | claimed (README: poppy_sign_out “detach the account”; S064 conformance row “met”) |
The first row consumes the run recorded on the version matrix page (fixtures/company-survey/): the official validator’s own suite (121/121) plus a read-only survey against a local, schema-valid fixture. That proves static discovery conformance for the fixture — sessions, OAuth, APIs and revocation were not covered by that run (recorded as unknown above), and no community implementation was run against any other.
One revision warning the matrix encodes: none of the three community rows targets the official 1.0 published 2026-11-14. PDA’s and Datalayer’s “1.0” references predate the official release (pre-release drafts), and pi-poppy is explicit 0.1. Official-1.0 compatibility of every community row is unknown.
Reproducing the one tested cell
No new validator is needed — the official tool is the reference:
sh fixtures/company-survey/run.sh # official validator suite + survey, offline fixtureTo test a deployed company endpoint instead, run the validator’s survey (GET-only) against the domain, and its full check only after confirming you may create sessions there — the online check acts as a personal agent and is not side-effect free. Details on the version matrix page.
Why not a single verdict column
Poppy spans discovery, session headers, OAuth issuance, business APIs and revocation, each with its own failure surface. A single “supports Poppy: yes/no” cell would force five independent facts into one bit and hide exactly the differences an implementer needs — including which protocol revision a claim targets. The version matrix carries the same discipline across revisions; this page carries it across capabilities.
Sources: official 1.0 specification and validator README at 65618532 (baseline, unchanged); community evidence read at the pinned commits above from each repository’s README (paths registered in site/data/poppy-sources.json under poppy-community-*); checked 2026-11-16. No community repository was installed or executed.