Repository navigation
Poppy: recheck against version 0.4 (the 1.0 release candidate) and move the pins - #33
Merged
Merged
Conversation
…ve the pins Version 0.4 was published on November 10, 2026 as the 1.0 release candidate, and Draft 1.0 started the next day. The page now names 0.4 as the specification and 1.0 as the draft in progress, links the Path to 1.0 page, and says what 0.4 changed for readers: direct sign-in is preferred, the protocol defines one scope of its own (browser sign-in), an agent can approve an operation on the user's instruction, and a company can serve several versions at once. The kit now follows draft 1.0. Deployments were rechecked on November 12: same small companies, none of the launch partners. The guide note for Poppy was still on Draft 0.2. Pins move to content/versions/0.4, the new versions.json blob, and the working draft pages, which now serve Draft 1.0, matching Ora's pins. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NWyUpGi6pqawG6T6LjjGCA
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
liady
pushed a commit
that referenced
this pull request
Nov 14, 2026
Bring in the Poppy rechecks from main (#33, #34, #35), which moved the page from Draft 0.3 to version 0.4 and the in-progress Draft 1.0 read 2026-11-13. - content/standards/poppy.md: keep main's prose, links, status_note, reality_check and last_verified (2026-11-13), with the branch's `spec: pap` in place of `spec_sources`. - spec-pins.json: keep it deleted. Main's eight poppy pins equal the reviewed sources of specs/pap/spec.yaml in the registry (reviewed 1.0, read 2026-11-13). - content/guide.json: main's updated Poppy note, unchanged. - vendor/ora-ai-specs-0.1.0.tgz: re-vendored from the registry with PAP reviewed at 1.0; package-lock.json integrity updated to match. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NWyUpDvmVGnxkjcJcd7nKm
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Poppy's version 0.4 was published on November 10, 2026 as the 1.0 release candidate, and Draft 1.0 started the next day. The Poppy page now names 0.4 as the specification and 1.0 as the draft in progress, links the Path to 1.0 page, says what 0.4 changed for readers, and moves the spec pins to 0.4 and the 1.0 working draft pages, matching Ora's pins in https://github.com/eralabs-ai/ora/pull/1674.
Details:
status_note,reality_check,linksand both prose sections updated. Status stays early: the live recheck on November 12 found the same small deployments, most still on drafts 0.1 or 0.2, and no launch partner serving apoppy.json.PROTOCOL_VERSION = "1.0"inkit/company/validate/catalog.ts).content/guide.json: the Poppy note still said "Draft 0.2 is from October 24, 2026, and 0.3 is in progress"; it now names 0.4 and 1.0.last_verifiedmoves to 2026-11-12: every claim on the page was rechecked.content/versions/0.4tree399ba1b,versions.jsonblobff7c9a3, and the six working draft page digests, which now hash the 1.0 pages.spec-pins.jsonregenerated withnpm run pins.Sources
content/versions/versions.json, https://github.com/personal-agent-protocol/personal-agent-protocol/blob/main/content/versions/versions.json)/.well-known/poppy.jsonfetched on 2026-11-12; walmart.com, shopify.com, stripe.com, rocketmortgage.com, genesys.com and nice.com answer 404.Checklist
status, the evidence meets the rules incontent/contribute.md. (Status unchanged.)last_verifiedon pages where I rechecked every claim.npm test,npm run lintandnpm run typecheckpass.Generated by Claude Code