POPPY / Field notes
From personal intent to company services.
Explore Poppy discovery, sessions and authorization. Connect personal agents to company capabilities with clear identities and verifiable steps.
Official 1.0 · Published 2026-11-14 · Reviewed 2026-11-16
From the model, to a verified implementation choice.
Evidence-first implementation reading.
One path, both sides, including the refusal.
An implementation path for both sides
Plan a verifiable Poppy 1.0 integration from discovery and sign-in through session setup to a denied request, with each step tied to a checkable artifact.
Scripted against pinned fixtures; per-capability evidence levels stay in the matrix.
Read the implementation path- Agent → CompanyFetch .well-known/poppy.json and verify the issuer
discovery - Agent → CompanySign-in and consent with pinned credentials
sign-in - Company → AgentIssue the session JWT
session - Agent → CompanyA denied request and its error branch
deny
Credentials, revocation and retries.
Credentials, revocation and retries
Separate session JWTs, OAuth tokens, DPoP proofs and business idempotency before you debug.
Pinned sources and the validator.
Sources & implementations
Every reference resolves to the pinned revision: the 1.0 spec, guides and the reference validator kit.
- Reference validatorGitHub
The company-side validation kit: offline file checks and local verification, not a full sign-in substitute.
- Official 1.0 specGitHub
spec.mdx source at the pinned revision.
- Official guidesGitHub
guides.mdx — the first-party basis for each integration step.