Skip to content

Release 1.0.1: the case decks describe Poppy 1.0 - #25

Merged
echarles merged 2 commits into
mainfrom
release/1.0.1
Nov 21, 2026
Merged

echarles merged 2 commits into
mainfrom
release/1.0.1

Conversation

@echarles

Copy link
Copy Markdown
Member

The four case decks (@datalayer/personal-agent-protocol/decks), shown on the docs site and on the Datalayer home page, said draft 0.3. Each now says "Personal Agent Protocol · 1.0 · a case" and describes its case at 1.0 as published, with Operations version 3:

  • every approval says who approved (the person, or the personal agent on an instruction the person gave it), and a company may decline an agent's approval: Ledgerly declines one for a payment, so Ada is asked about every payment, as the SDK's two-companies demo does;
  • the company's consent page is shown at every sign-in and lists every scope;
  • a company describes its agent in a line (agent_description).

Docs and examples that described draft 0.3 follow: getting started, coverage (Operations v3), the Two companies, Operations and Session transport example decks, the Specification menu (version 1.0), and the Pydantic AI example READMEs.

No code, API or protocol change. Versions: __version__.py, package.json, the four plugin manifests, compatibility page (1.0.1 row), conformance report header, CHANGELOG.

Tests: Python 1688 passed; TypeScript 1128 passed, 1 skipped (decks.test.mjs checks the 1.0 meta line and that no deck says draft or 0.3).

The four case decks (./decks), shown on the docs site and the Datalayer home page, said
draft 0.3. Each now says "Personal Agent Protocol · 1.0 · a case" and describes its case at
1.0 as published, with Operations version 3: every approval says who approved, a company may
decline an agent's approval (Ledgerly declines one for a payment), the consent page is shown
at every sign-in and lists every scope, and a company describes its agent in a line. The docs
and examples that described draft 0.3 follow (getting started, coverage, the Two companies,
Operations and Session transport example decks, the Specification menu, the example READMEs).

Version bumps: __version__.py, package.json, the four plugin manifests, the compatibility page,
the conformance report header, the CHANGELOG.
Copilot AI balanced review requested due to automatic review settings November 21, 2026 06:03

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are recorded for the SDK 1.0.1 documentation and release-metadata update.

No open issues 🎉

What changed in this PR

This release aligns the SDK’s case decks, documentation, and examples with published Poppy 1.0 and Operations v3, while updating release metadata to 1.0.1. Runtime logic, APIs, and protocol behavior remain unchanged.

Changes:

  • Update case narratives to explain approver identity, agent approvals, consent pages, and company agent descriptions.
  • Refresh documentation and example references, and strengthen deck checks against outdated wording.
  • Bump SDK and plugin versions and update release records.
File Description
src/​reactor.ts Bump TypeScript core plugin version.
src/​decks/​pap-your-application-a-company.ts Update company responsibilities and approval narrative.
src/​decks/​pap-two-companies.ts Explain Ledgerly’s rejection of agent payment approvals.
src/​decks/​pap-approve-once.ts Describe Operations v3 approvals and approver identity.
src/​decks/​pap-a-person-and-a-company.ts Clarify Session signing and sign-in consent.
src/​decks/​index.ts Update deck documentation to Poppy 1.0.
src/​company/​index.ts Bump TypeScript company plugin version.
src/​__tests__/​decks.test.mjs Check current version wording and reject stale references.
personal_agent_protocol/​requirements.py Clarify requirement-ledger version coverage in the docstring.
personal_agent_protocol/​reactor.py Bump Python core plugin version.
personal_agent_protocol/​demo/​ledgerly.py Update the demo docstring’s protocol reference.
personal_agent_protocol/​company/​__init__.py Bump Python company plugin version.
personal_agent_protocol/​__version__.py Set Python SDK version to 1.0.1.
package.json Set npm package version to 1.0.1.
examples/​pydantic-ai/​two-companies/​README.md Document current payment approval policy.
examples/​pydantic-ai/​two-companies/​app.py Refresh the example docstring’s approval description.
examples/​pydantic-ai/​session-transport/​README.md Remove the outdated draft citation.
examples/​pydantic-ai/​conversation-control/​README.md Update protocol version and section references.
docs/​docusaurus.config.js Link the Specification menu to version 1.0.
docs/​docs/​releases/​compatibility.mdx Add the SDK 1.0.1 release entry.
docs/​docs/​protocol/​coverage.mdx Update Operations coverage and protocol references.
docs/​docs/​protocol/​conformance-report.mdx Update the report’s SDK version header.
docs/​docs/​getting-started/​index.mdx Describe supported Poppy versions and the default.
docs/​docs/​examples/​two-companies.mdx Refresh composition and payment approval guidance.
docs/​docs/​examples/​cases/​pap-two-companies.mdx Explain why every payment still requires Ada’s approval.
docs/​docs/​examples/​cases/​pap-approve-once.mdx Clarify person and agent approval attribution.
docs/​decks/​examples/​two-companies.deck.json Update composition, approval, and audit narratives.
docs/​decks/​examples/​session-transport.deck.json Remove outdated draft wording from redirect notes.
docs/​decks/​examples/​operations.deck.json Describe Operations v3 and attributed approvals.
CHANGELOG.md Record the documentation-focused 1.0.1 release.

Review effort: Balanced

@echarles
echarles merged commit f1e1026 into main Nov 21, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants