diff --git a/CHANGELOG.md b/CHANGELOG.md
index ccde8c10..61de897e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,21 @@
# Changelog
+## 1.0.1 (2026-11-21)
+
+The cases describe Poppy 1.0. In both SDKs; no change to the code, the API or the protocol
+behaviour.
+
+- **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 version 3 of the Operations
+ extension: 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); the company's consent page
+ is shown at every sign-in and lists every scope; a company describes its agent in a line.
+- **The docs and examples** that described draft 0.3: the getting-started page, the coverage
+ page (Operations v3), the Two companies and Operations example decks, the Specification menu
+ (version 1.0), and the Pydantic AI examples' READMEs.
+
## 1.0.0 (2026-11-21)
The SDK's version follows Poppy's: 1.0. Poppy, the Personal Agent Protocol, reached 1.0 on
diff --git a/docs/decks/examples/operations.deck.json b/docs/decks/examples/operations.deck.json
index 55f7cd3b..b80695b6 100644
--- a/docs/decks/examples/operations.deck.json
+++ b/docs/decks/examples/operations.deck.json
@@ -10,13 +10,13 @@
"title": "Operations",
"subtitle": "Approve exactly what the company proposed, performed at most once, and recover a lost answer",
"meta": "Personal Agent Protocol · example",
- "notes": "An operation is an action a company performs only once the user approves its exact terms: a payment, an exchange, a cancellation. This example gets Ada's approval of Northwind Bank's payments with the Operations extension, version 2."
+ "notes": "An operation is an action a company performs only once the user approves its exact terms: a payment, an exchange, a cancellation. This example gets Ada's approval of Northwind Bank's payments with the Operations extension, version 3."
},
{
"type": "statement",
"title": "Why operations",
"statement": "The approval is **exact** and **durable**: a chat message never approves anything.",
- "notes": "Money moves only on an explicit approval of one revision of the terms. The user approves in the host's own interface, every time, and the company performs an approved action at most once, even when answers get lost."
+ "notes": "Money moves only on an explicit approval of one revision of the terms. Every approval says who approved; here Ada approves in the host's own interface, every time, and the company performs an approved action at most once, even when answers get lost."
},
{
"type": "mermaid",
@@ -29,7 +29,7 @@
"type": "flow",
"title": "Approval, and changed terms",
"items": [
- { "label": "1", "title": "Negotiate", "detail": "Both sides list operations version 2" },
+ { "label": "1", "title": "Negotiate", "detail": "Both sides list operations version 3" },
{ "label": "2", "title": "Proposal", "detail": "An operation: EUR 1250.00 to Acme GmbH" },
{ "label": "3", "title": "Approve", "detail": "Ada approves this revision" },
{ "label": "4", "title": "New revision", "detail": "EUR 1262.50, a fee added: nothing done", "current": true }
diff --git a/docs/decks/examples/session-transport.deck.json b/docs/decks/examples/session-transport.deck.json
index 5a4f626b..f5b97df3 100644
--- a/docs/decks/examples/session-transport.deck.json
+++ b/docs/decks/examples/session-transport.deck.json
@@ -40,7 +40,7 @@
"type": "mermaid",
"title": "The redirect is refused",
"diagram": "sequenceDiagram\n participant A as Agent tool\n participant H as Session client\n participant C as Company API\n A->>H: GET orders again\n H->>C: Token + JWT 3\n C-->>H: 307 to /orders/current\n H-->>A: redirect_refused",
- "notes": "On the second call the company answers with a redirect. The client does not follow it: under draft 0.3 no token, Session JWT, assertion or body goes to the URL a protocol endpoint redirects to. The tool gets redirect_refused, and nothing reaches the new URL."
+ "notes": "On the second call the company answers with a redirect. The client does not follow it: no token, Session JWT, assertion or body goes to the URL a protocol endpoint redirects to. The tool gets redirect_refused, and nothing reaches the new URL."
},
{
"type": "bullets",
diff --git a/docs/decks/examples/two-companies.deck.json b/docs/decks/examples/two-companies.deck.json
index 576ee588..1142eb8a 100644
--- a/docs/decks/examples/two-companies.deck.json
+++ b/docs/decks/examples/two-companies.deck.json
@@ -15,7 +15,7 @@
{
"type": "statement",
"title": "Composition, not a new protocol",
- "statement": "Draft 0.3 defines **no company-to-company protocol**. Two ordinary PAP relationships, for the same user, are enough.",
+ "statement": "Poppy 1.0 defines **no company-to-company protocol**. Two ordinary PAP relationships, for the same user, are enough.",
"notes": "There is no special protocol between companies. Ledgerly is a company to Ada's personal agent, and, separately, a personal agent at Northwind for the same Ada, with its own client_id and keys on its own domain."
},
{
@@ -35,7 +35,7 @@
"type": "statement",
"title": "Every approval is an Operation",
"statement": "Never a chat message, and **Ada is asked about every payment**.",
- "notes": "Approving money movement in a chat message would be too easy to fake or misread. In this example every approval is an Operation with a summary and terms the user approves, and draft 0.3 asks the user about each one."
+ "notes": "Approving money movement in a chat message would be too easy to fake or misread. In this example every approval is an Operation with a summary and terms, and says who approved. Atlas may approve on an instruction Ada gave it, but Ledgerly declines that for a payment, since it tells Northwind that Ada approved: so Ada is asked about each one."
},
{
"type": "flow",
@@ -45,14 +45,14 @@
{ "label": "2", "title": "Nothing carries over", "detail": "An approval covers one revision of one payment" },
{ "label": "3", "title": "INV-0043", "detail": "EUR 980.00: a new Operation for Ada", "current": true }
],
- "notes": "Ada approves the first payment. That approval covers that revision alone: every operation Northwind returns goes to Ada, and nothing approves one in her name. So the next bill, INV-0043, is a new Operation for her to approve."
+ "notes": "Ada approves the first payment. That approval covers that revision alone: every operation Northwind returns goes to Ada, and an approval Atlas gives in her name is declined by Ledgerly. So the next bill, INV-0043, is a new Operation for her to approve."
},
{
"type": "mermaid",
"title": "How Ledgerly approves",
"diagram": "flowchart LR\n N[\"Northwind proposes\"] --> O[\"Operation for Ada\"]\n O -- \"Ada approves\" --> U[\"Revision and terms
unchanged?\"]\n U -- \"yes\" --> C[\"Sends Northwind
the approval\"]\n O -- \"Ada declines\" --> X[\"Nothing is paid\"]",
"caption": "Ledgerly approves at Northwind only the exact revision Ada approved.",
- "notes": "Follow one Northwind proposal. Ledgerly proposes an Operation for Ada, which Atlas shows with its summary and terms, as it would for any company. If Ada declines, nothing is paid. When Ada approves, Ledgerly checks that Northwind's revision and terms have not changed, and only then sends Northwind the approval of that revision. Northwind's records keep the revision approved and when, and Ledgerly relays what Northwind says it came to, as written."
+ "notes": "Follow one Northwind proposal. Ledgerly proposes an Operation for Ada, which Atlas shows with its summary and terms, as it would for any company. If Ada declines, nothing is paid. When Ada approves, Ledgerly checks that Northwind's revision and terms have not changed, and only then sends Northwind the approval of that revision. Northwind's records keep the revision approved, that Ada approved it, and when, and Ledgerly relays what Northwind says it came to, as written."
},
{
"type": "two-columns",
diff --git a/docs/docs/examples/cases/pap-approve-once.mdx b/docs/docs/examples/cases/pap-approve-once.mdx
index 85986d57..7f41a022 100644
--- a/docs/docs/examples/cases/pap-approve-once.mdx
+++ b/docs/docs/examples/cases/pap-approve-once.mdx
@@ -11,8 +11,10 @@ import CaseDeck from '@site/src/components/CaseDeck';
Ada's jacket isn't warm enough. Manzanita doesn't exchange it yet: it returns an
operation, its exact terms. Her agent shows them to her, and sends the same
-request again only with her approval of that revision. Ada is asked about every
-operation, and nothing approves in her place.
+request again only with her approval of that revision. The approval says that
+Ada gave it herself: at Poppy 1.0 every approval names its approver, the person
+or her agent on an instruction she gave it, and the company may decline one her
+agent gave.
- The wire, with new terms and a lost answer: the [Operations](/examples/operations) example flow.
- How to build it: the [Operations guide](/guides/operations/).
diff --git a/docs/docs/examples/cases/pap-two-companies.mdx b/docs/docs/examples/cases/pap-two-companies.mdx
index b64f0a0d..a1a1182b 100644
--- a/docs/docs/examples/cases/pap-two-companies.mdx
+++ b/docs/docs/examples/cases/pap-two-companies.mdx
@@ -12,7 +12,8 @@ import CaseDeck from '@site/src/components/CaseDeck';
Ledgerly, an accounting firm, is a company to Ada's agent, Atlas, and a personal
agent at her bank, Northwind. There is no company-to-company protocol: two
ordinary relationships meet in Ledgerly. Every payment the bank returns goes to
-Ada, the first and the next, and she can't ask for that to stop.
+Ada, the first and the next: an approval Atlas gives on her instruction is
+declined by Ledgerly, which tells the bank that Ada approved.
The [Two companies](/examples/two-companies) example flow is this case on the
wire, with all three parties running in one process.
diff --git a/docs/docs/examples/two-companies.mdx b/docs/docs/examples/two-companies.mdx
index 3aacbd96..b0f472e6 100644
--- a/docs/docs/examples/two-companies.mdx
+++ b/docs/docs/examples/two-companies.mdx
@@ -10,9 +10,9 @@ import deck from '@site/decks/examples/two-companies.deck.json';
-:::caution Composition, not a version 0.4 feature
+:::caution Composition, not a version 1.0 feature
-PAP version 0.4 defines no company-to-company protocol. This example composes
+Poppy 1.0, like 0.4, defines no company-to-company protocol. This example composes
two ordinary PAP relationships for the same user. Ledgerly is a **company** to
Ada's personal agent, Atlas, and a **personal agent** at Northwind Bank for
the same Ada, with its own `client_id` and keys on its own domain.
@@ -23,8 +23,9 @@ The case [Two Companies Together](/examples/cases/pap-two-companies) tells this
story in a reader's words; this page is the same story on the wire.
Ledgerly, an accounting firm, pays Ada's supplier invoices from her Northwind
-account. Every approval is an Operation, never a chat message, and Ada is asked
-about every payment.
+account. Every approval is an Operation, never a chat message, and says who
+approved. Ledgerly declines an approval Atlas gives on an instruction, so Ada is
+asked about every payment.
```mermaid
sequenceDiagram
diff --git a/docs/docs/getting-started/index.mdx b/docs/docs/getting-started/index.mdx
index 72017843..a497d3d7 100644
--- a/docs/docs/getting-started/index.mdx
+++ b/docs/docs/getting-started/index.mdx
@@ -6,8 +6,9 @@ title: Getting started
# Getting started
This quick start discovers a company, validates its declaration and OAuth
-metadata, and prints the interfaces it offers. The SDKs target PAP draft 0.3
-and are preview software.
+metadata, and prints the interfaces it offers. The SDKs implement Poppy 1.0 as
+published, the default, and 0.4 when named (see
+[Compatibility](/releases/compatibility/)).
## Prerequisites
diff --git a/docs/docs/protocol/conformance-report.mdx b/docs/docs/protocol/conformance-report.mdx
index 1cc88002..c771d595 100644
--- a/docs/docs/protocol/conformance-report.mdx
+++ b/docs/docs/protocol/conformance-report.mdx
@@ -6,7 +6,7 @@ title: Compatibility and conformance report
# Compatibility and conformance report
-SDK version **1.0.0**, PAP profile **0.4** (as published 2026-11-10), Operations extension **v3**; the pairings run at protocol version **1.0**, the default (1.0 as published 2026-11-14); the suite also runs at 0.4 in every pairing. Each pairing runs every positive, negative and recovery fixture case over real TCP and TLS, the personal agent in one language and the reference company (Manzanita) in the other. A case is skipped, never passed, when a side lacks what it needs; the reason is listed below.
+SDK version **1.0.1**, PAP profile **0.4** (as published 2026-11-10), Operations extension **v3**; the pairings run at protocol version **1.0**, the default (1.0 as published 2026-11-14); the suite also runs at 0.4 in every pairing. Each pairing runs every positive, negative and recovery fixture case over real TCP and TLS, the personal agent in one language and the reference company (Manzanita) in the other. A case is skipped, never passed, when a side lacks what it needs; the reason is listed below.
## Pairings
diff --git a/docs/docs/protocol/coverage.mdx b/docs/docs/protocol/coverage.mdx
index 3f1d3809..2ec3ef50 100644
--- a/docs/docs/protocol/coverage.mdx
+++ b/docs/docs/protocol/coverage.mdx
@@ -86,7 +86,7 @@ changes, applied at 1.0; one marked `(0.4)` holds at 0.4 only.
| Conversations | Create, retry idempotently, read cursor events (`cursor`, `wait` as query parameters; `conversation_id` and `events` on every read), poll or stream (`Last-Event-ID` wins), identify speakers (`role` set by the company, `author` with its `type` and, for a company's person or persona, `id`, `name`, `image`), hand off and close idempotently, sign in, stay open after sign-out. |
| Extensions | Negotiate named major versions while ignoring unsupported extensions and unknown fields. |
| Excluded tasks and feedback | Read the tasks a company doesn't offer (`excluded_tasks`, each with an optional alternative); report a missing task (`task`, `description`) with the Session header; the company answers 202, or 200 with an alternative when the task can be done after all. |
-| Operations v2 | Refuse an action with 403 `approval_required` and its operation, ask the user about every operation, retry the same request with its approval, perform at most once, across interfaces, with 503 and `Retry-After` while performing. |
+| Operations v3 | Refuse an action with 403 `approval_required` and its operation, ask the user (or approve on the user's instruction, the approval naming its `approver`), decline an approval, retry the same request with its approval, perform at most once, across interfaces, with 503 and `Retry-After` while performing. |
## Coverage expectations
@@ -112,19 +112,19 @@ regardless of the channel where an operation was refused.
| Mediated Sign-In | Python and TypeScript | Python and TypeScript reference companies | [Mediated Sign-In](/examples/mediated-sign-in/) |
| Refresh tokens | Python and TypeScript | Python and TypeScript reference companies | [Refresh tokens](/examples/account-tokens/) |
| Conversations: messages, events, SSE, handoff, Direct, sign-in, close | Python and TypeScript | Python and TypeScript reference companies | [Streaming](/examples/conversation-streaming/), [control](/examples/conversation-control/) |
-| Operations v2 | Refuse an action with 403 `approval_required` and its operation, ask the user about every operation, retry the same request with its approval, perform at most once, across interfaces, with 503 and `Retry-After` while performing. |
+| Operations v3 | Refuse an action with 403 `approval_required` and its operation, ask the user (or approve on the user's instruction, the approval naming its `approver`), decline an approval, retry the same request with its approval, perform at most once, across interfaces, with 503 and `Retry-After` while performing. |
| Web (Browser Session) | Python and TypeScript | Python and TypeScript reference companies | [Browser Session](/examples/browser-session/) |
| OpenAPI and MCP | Python and TypeScript (`ApiClient`, `McpClient`, a token by `resource`) | Python and TypeScript reference companies | [TypeScript SDK](/sdk/typescript/#openapi-and-mcp) |
| Feedback | Python and TypeScript (`FeedbackClient`) | Python and TypeScript reference companies (`POST /poppy/feedback`) | [Feedback coverage](/protocol/coverage/feedback/) |
The end-to-end journeys, [a user with a company](/examples/user-with-a-company/)
-and [two companies](/examples/two-companies/) (composition, not a draft 0.3
+and [two companies](/examples/two-companies/) (composition, not a 1.0
company-to-company feature), run in Python only, on the demo worlds in
`personal_agent_protocol.demo`.
## Deliberate boundaries
-Draft 0.3 does not define payments, push notifications, or message
+Version 1.0 does not define payments, push notifications, or message
attachments. The SDKs preserve unknown extension data but do not invent wire
formats for those areas. Company registration policy is also outside the
protocol; implementations may expose allow/block policy without presenting it
diff --git a/docs/docs/releases/compatibility.mdx b/docs/docs/releases/compatibility.mdx
index 6afd7a2e..55d403df 100644
--- a/docs/docs/releases/compatibility.mdx
+++ b/docs/docs/releases/compatibility.mdx
@@ -4,7 +4,7 @@ title: Compatibility
# Compatibility
-This page is versioned with the SDK: it describes **SDK 1.0.0**.
+This page is versioned with the SDK: it describes **SDK 1.0.1**.
## The PAP version implemented
@@ -35,6 +35,7 @@ profile, never picked up from an unattended fetch.
| SDK (PyPI and npm) | PAP profile | Specification revision | Operations | Breaking changes |
| --- | --- | --- | --- | --- |
+| `1.0.1` | `0.4` | 2026-11-10 | v3 | none: the four case decks (`./decks`) and the docs describe the cases at Poppy 1.0 as published, with Operations version 3, no longer draft 0.3 |
| `1.0.0` | `0.4` | 2026-11-10 | v3 | none: the SDK's version follows Poppy's own, 1.0; the code is 0.37.5's |
| `0.37.5` | `0.4` | 2026-11-10 | v3 | none: a client that registers itself (`client_registration`) is registered as a public client whatever `token_endpoint_auth_method` it asked for among `none`, `client_secret_post`, `client_secret_basic` or none at all, and told `none`; a request that sends a client secret is refused |
| `0.37.4` | `0.4` | 2026-11-10 | v3 | none: a company may let clients that are no personal agents sign in (`public_clients`: MCP clients, with PKCE alone, verified by their client ID metadata document or registered at `/oauth/register` with `client_registration`), for tokens that work at one service and at no endpoint of the protocol; off by default |
diff --git a/docs/docusaurus.config.js b/docs/docusaurus.config.js
index 50c0e2a2..967417c1 100644
--- a/docs/docusaurus.config.js
+++ b/docs/docusaurus.config.js
@@ -101,7 +101,7 @@ module.exports = {
label: 'Specification',
items: [
{label: 'personalagentprotocol.org', href: 'https://personalagentprotocol.org'},
- {label: 'Draft 0.3', href: 'https://personalagentprotocol.org/docs/0.3/spec'},
+ {label: 'Version 1.0', href: 'https://personalagentprotocol.org/docs/1.0/spec'},
{label: 'Changelog', href: 'https://personalagentprotocol.org/docs/changelog'},
{
label: 'GitHub: personal-agent-protocol',
diff --git a/examples/pydantic-ai/conversation-control/README.md b/examples/pydantic-ai/conversation-control/README.md
index 75518461..56607d3f 100644
--- a/examples/pydantic-ai/conversation-control/README.md
+++ b/examples/pydantic-ai/conversation-control/README.md
@@ -1,7 +1,7 @@
# Conversation control
-This example drives one Manzanita conversation through every control in PAP
-draft 0.3 §7.9 to §7.12 with the real Python SDK: an `authorization` event
+This example drives one Manzanita conversation through every control in Poppy
+1.0 §8.9 to §8.12 with the real Python SDK: an `authorization` event
(`insufficient_scope`, with the scope the request needs) answered by signing
the same Session in mid-conversation (the conversation keeps its ID), a
Direct Conversation that locks its parent (`direct_conversation_open` names
diff --git a/examples/pydantic-ai/session-transport/README.md b/examples/pydantic-ai/session-transport/README.md
index eba49731..dc77d152 100644
--- a/examples/pydantic-ai/session-transport/README.md
+++ b/examples/pydantic-ai/session-transport/README.md
@@ -2,8 +2,8 @@
This example sends a PAP API request with the `Poppy-Session` header and a Bearer
access token, starts a new Session once after `session_ended` and resends the
-request in it, refuses a redirect (draft 0.3 §3: no token or Session JWT goes to
-the URL a protocol endpoint redirects to), and rejects caller-supplied
+request in it, refuses a redirect (no token or Session JWT goes to the URL a
+protocol endpoint redirects to), and rejects caller-supplied
authorization headers.
Access tokens, Session JWTs, and Session IDs remain host-owned.
diff --git a/examples/pydantic-ai/two-companies/README.md b/examples/pydantic-ai/two-companies/README.md
index 10ba405d..208ea52a 100644
--- a/examples/pydantic-ai/two-companies/README.md
+++ b/examples/pydantic-ai/two-companies/README.md
@@ -2,13 +2,15 @@
Ledgerly, an accounting firm, pays Ada's invoices at Northwind Bank for her.
-This is **composition**, not a company-to-company protocol: PAP draft 0.3
+This is **composition**, not a company-to-company protocol: Poppy 1.0
defines none. Ledgerly is a PAP company to Atlas (Ada's personal agent) and,
for the same Ada, a PAP personal agent at Northwind with its own `client_id`
and keys. Ada connects Ledgerly to Northwind on Northwind's own page. Every
approval is an Operation: Northwind's payment is relayed to Ada as a Ledgerly
operation quoting it as written, and Ledgerly sends Northwind the approval of that
-exact revision once she approves it. Ada is asked about every payment.
+exact revision once she approves it. Every approval says who approved, and
+Ledgerly declines an approval Atlas gives on an instruction: Ada is asked about
+every payment.
The tool returns summaries as the companies wrote them and who approved each
payment. No token, code, or proof enters it.
diff --git a/examples/pydantic-ai/two-companies/app.py b/examples/pydantic-ai/two-companies/app.py
index 6e5eb03d..0210e91b 100644
--- a/examples/pydantic-ai/two-companies/app.py
+++ b/examples/pydantic-ai/two-companies/app.py
@@ -3,9 +3,10 @@
"""A Pydantic AI agent showing two companies working together over PAP, by composition.
-Draft 0.3 defines no company-to-company protocol. Ledgerly, an accounting firm, is
+Poppy 1.0 defines no company-to-company protocol. Ledgerly, an accounting firm, is
a PAP company to Ada's personal agent (Atlas) and, for the same Ada, a PAP personal
-agent at Northwind Bank. Every approval is an Operation, and Ada is asked about each.
+agent at Northwind Bank. Every approval is an Operation that says who approved, and
+Ledgerly declines an agent's approval of a payment, so Ada is asked about each.
"""
from __future__ import annotations
diff --git a/package.json b/package.json
index 38807d85..5bd4c361 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
{
"name": "@datalayer/personal-agent-protocol",
- "version": "1.0.0",
+ "version": "1.0.1",
"description": "TypeScript SDK for Personal Agent Protocol 0.4 (2026-11-10) and its Operations extension v3",
"repository": {
"type": "git",
diff --git a/personal_agent_protocol/__version__.py b/personal_agent_protocol/__version__.py
index 3065b423..2f10032a 100644
--- a/personal_agent_protocol/__version__.py
+++ b/personal_agent_protocol/__version__.py
@@ -7,4 +7,4 @@
"""Personal Agent Protocol."""
-__version__ = "1.0.0"
+__version__ = "1.0.1"
diff --git a/personal_agent_protocol/company/__init__.py b/personal_agent_protocol/company/__init__.py
index d7b36130..cab43cad 100644
--- a/personal_agent_protocol/company/__init__.py
+++ b/personal_agent_protocol/company/__init__.py
@@ -191,7 +191,7 @@ def build_company(
reactor.register_plugin(
PluginManifest(
name="personal-agent-protocol.company",
- version="1.0.0",
+ version="1.0.1",
contribution_points=[
COMPANY_STORES.id,
COMPANY_ACCOUNTS.id,
diff --git a/personal_agent_protocol/demo/ledgerly.py b/personal_agent_protocol/demo/ledgerly.py
index 6a4e8cd7..9d64ac70 100644
--- a/personal_agent_protocol/demo/ledgerly.py
+++ b/personal_agent_protocol/demo/ledgerly.py
@@ -4,7 +4,7 @@
"""Ledgerly: a fictional accounting firm that is a company and a personal agent at once.
-Two companies working together, in draft 0.3's own terms. Draft 0.3 defines
+Two companies working together, in Poppy 1.0's own terms. Version 1.0 defines
no company-to-company protocol, so this is **composition**:
- To Ada's personal agent (Atlas), Ledgerly is a PAP company: discovery,
diff --git a/personal_agent_protocol/reactor.py b/personal_agent_protocol/reactor.py
index c73c4cff..55c45815 100644
--- a/personal_agent_protocol/reactor.py
+++ b/personal_agent_protocol/reactor.py
@@ -1088,7 +1088,7 @@ def build_pap_reactor(
platform.register_plugin(
PluginManifest(
name="personal-agent-protocol.core",
- version="1.0.0",
+ version="1.0.1",
contribution_points=[
DISCOVERY_TRANSPORTS.id,
URL_SAFETY_POLICIES.id,
diff --git a/personal_agent_protocol/requirements.py b/personal_agent_protocol/requirements.py
index 0be84c92..de5ee9d1 100644
--- a/personal_agent_protocol/requirements.py
+++ b/personal_agent_protocol/requirements.py
@@ -4,11 +4,11 @@
"""The normative requirement ledger (`protocol/requirements.yaml`) and shared fixtures.
-Every MUST, MUST NOT, SHOULD, and SHOULD NOT of draft 0.3 and its extensions
-has one entry: its section, level, role, exact text, where it is implemented
-(`module:symbol`), and the test that shows it (`file::name`), or an `open`
-status with the reason. Recommendations from the upstream guides are kept
-apart (`source: guide`).
+Every MUST, MUST NOT, SHOULD, and SHOULD NOT of version 0.4 as published, of
+what 1.0 adds (`version: '1.0'`), and of their extensions has one entry: its
+section, level, role, exact text, where it is implemented (`module:symbol`),
+and the test that shows it (`file::name`), or an `open` status with the reason.
+Recommendations from the upstream guides are kept apart (`source: guide`).
The ledger and the conformance fixtures ship inside the wheel
(`personal_agent_protocol/protocol/`); in a source checkout they are read from
diff --git a/src/__tests__/decks.test.mjs b/src/__tests__/decks.test.mjs
index 7cc3bc09..ba1b1d93 100644
--- a/src/__tests__/decks.test.mjs
+++ b/src/__tests__/decks.test.mjs
@@ -5,8 +5,8 @@
*/
// The four cases as decks: the package's `./decks` entry, and the docs pages that
-// show them. One deck per case, in the deck format, each naming its case, at draft
-// 0.3: every operation is asked of the person, and nothing stands in for them.
+// show them. One deck per case, in the deck format, each naming its case, at Poppy
+// 1.0 as published: every approval says who approved.
import assert from "node:assert/strict";
import { existsSync, readFileSync } from "node:fs";
import test from "node:test";
@@ -98,9 +98,12 @@ for (const [id, name] of CASES) {
assert.equal(deck.spec.slides.at(-1).type, "closing");
});
- test(`${id}: it says draft 0.3 and no standing permission`, () => {
- const words = textOf(papDeck(id).spec);
- assert.match(words, /draft 0\.3/);
+ test(`${id}: it says Poppy 1.0, no draft, and no standing permission`, () => {
+ const spec = papDeck(id).spec;
+ const words = textOf(spec);
+ assert.equal(spec.slides[0].meta, "Personal Agent Protocol · 1.0 · a case");
+ assert.match(words, /version 1\.0 of the protocol, Poppy 1\.0, as published/);
+ assert.doesNotMatch(words, /draft|0\.3|version two of the Operations/i);
assert.doesNotMatch(words, /standing|approved_by|in advance without asking/i);
});
@@ -135,8 +138,10 @@ test("the words a company says are the demo company's own", () => {
}
});
-test("no deck of the docs site keeps a standing permission: draft 0.3 asks every time", () => {
+test("no deck of the docs site keeps a standing permission, nor describes draft 0.3", () => {
for (const name of ["two-companies", "operations", "user-with-a-company"]) {
- assert.doesNotMatch(read(`docs/decks/examples/${name}.deck.json`), /standing|approved_by|Session Key/i);
+ const deck = read(`docs/decks/examples/${name}.deck.json`);
+ assert.doesNotMatch(deck, /standing|approved_by|Session Key/i);
+ assert.doesNotMatch(deck, /draft 0\.3|version 2\b/i);
}
});
diff --git a/src/company/index.ts b/src/company/index.ts
index 1845f470..ffa74e61 100644
--- a/src/company/index.ts
+++ b/src/company/index.ts
@@ -137,7 +137,7 @@ export function createCompanyDefaultsPlugin(
) {
return definePlugin({
name: "personal-agent-protocol.company",
- version: "1.0.0",
+ version: "1.0.1",
contributionPoints: [
CompanyStores,
CompanyAccounts,
diff --git a/src/decks/index.ts b/src/decks/index.ts
index 7c1ce5e7..aee080a2 100644
--- a/src/decks/index.ts
+++ b/src/decks/index.ts
@@ -14,9 +14,10 @@
* The documentation site and the Datalayer home page read them here, in the
* same order, under the same names, so the three tell one story.
*
- * Decks describe draft 0.3: every operation is asked of the person, and
- * nothing approves in their place. No part of the SDK proper imports this
- * entry, and it imports no part of the SDK.
+ * Decks describe Poppy 1.0, as published, with version 3 of the Operations
+ * extension: every approval says who approved, the person or their agent on
+ * an instruction they gave it. No part of the SDK proper imports this entry,
+ * and it imports no part of the SDK.
*/
import { parse } from "yaml";
diff --git a/src/decks/pap-a-person-and-a-company.ts b/src/decks/pap-a-person-and-a-company.ts
index a821df1e..e5b3077d 100644
--- a/src/decks/pap-a-person-and-a-company.ts
+++ b/src/decks/pap-a-person-and-a-company.ts
@@ -14,7 +14,7 @@ slides:
type: title
title: A Person and a Company
subtitle: Ada’s agent asks a shop about her order, and she signs in at the shop itself.
- meta: Personal Agent Protocol · draft 0.3 · a case
+ meta: Personal Agent Protocol · 1.0 · a case
notes: >-
Ada bought a jacket from an online shop and wants to know where it is.
She asks her personal agent. This is the first thing the Personal Agent
@@ -80,8 +80,8 @@ slides:
Every company publishes one page for personal agents, at a well-known
address on its domain. The agent reads it and checks that the domain and
whoever signs the company’s sign-ins belong together. Then it opens a
- Session, proving its own identity with a short-lived key, and starts a
- conversation. Nobody is signed in yet, so the company answers only what
+ Session, signing every request with a short-lived key that its own
+ published keys vouch for, and starts a conversation. Nobody is signed in yet, so the company answers only what
anybody may ask.
- id: asked-to-sign-in
type: statement
@@ -102,6 +102,7 @@ slides:
type: bullets
items:
- The agent never sees her password
+ - The page lists every permission, each time she signs in
- She can keep fewer permissions than it asks for
- The Session the agent already has becomes signed in
right:
@@ -112,8 +113,10 @@ slides:
- Tokens kept by the host, out of the model’s reach
- The order, answered by the company
notes: >-
- Ada signs in on manzanita.example, never in the chat. She can allow less
- than the agent asked for. The same Session carries on, now signed in,
+ Ada signs in on manzanita.example, never in the chat. Manzanita shows its
+ own page every time, listing every permission, even ones she allowed
+ before, so a forwarded link cannot sign anybody in unseen. She can allow
+ less than the agent asked for. The same Session carries on, now signed in,
and the company answers with what it knows. The tokens are held by the
host around the agent, so the model that writes the agent’s replies
never sees them.
@@ -145,7 +148,7 @@ slides:
cta: The next case takes the same order further, A Change, Approved Once.
notes: >-
This case is played from the SDK’s demo company, Manzanita Outfitters,
- and described at draft 0.3 of the protocol. The example flow called A
- user with a company runs the whole journey in one process, both sides
- from the SDK.
+ and described at version 1.0 of the protocol, Poppy 1.0, as published.
+ The example flow called A user with a company runs the whole journey in
+ one process, both sides from the SDK.
`;
diff --git a/src/decks/pap-approve-once.ts b/src/decks/pap-approve-once.ts
index 2ab3233f..fe18a1a8 100644
--- a/src/decks/pap-approve-once.ts
+++ b/src/decks/pap-approve-once.ts
@@ -14,18 +14,19 @@ slides:
type: title
title: A Change, Approved Once
subtitle: The shop proposes an exchange; Ada approves its exact terms, and it is done once.
- meta: Personal Agent Protocol · draft 0.3 · a case
+ meta: Personal Agent Protocol · 1.0 · a case
notes: >-
Reading an order is harmless. Changing one costs money. This case is
about the moment an agent is about to do something that matters, and how
- the protocol makes sure the person is the one who decides.
+ the protocol makes sure the person decides, and that the company knows
+ who approved.
- id: who
type: three-columns
title: Who is in this case
columns:
- heading: Ada
type: text
- content: The person. Only she can approve.
+ content: The person. The decision is hers.
- heading: Her agent
type: text
content: Asks, shows her what is proposed, and carries her answer.
@@ -74,23 +75,25 @@ slides:
- A revision, naming this exact version
- When it expires
notes: >-
- An operation has a summary, written by the company in plain language, and
- terms, the same thing as data. The agent compares the two with what Ada
- asked for and points out any difference. A revision names this exact
- version, and the operation expires.
+ An operation always has terms, what the company proposes as data, and
+ here a summary too, the same thing written by the company in plain
+ language. The agent compares the two with what Ada asked for and points
+ out any difference. A revision names this exact version, and the
+ operation expires.
- id: asked
type: statement
- title: Every operation is asked of the person
+ title: Every approval says who approved
statement: >-
- Ada is asked **every time**. Nothing approves on her behalf, not the
- model, not a rule, not something she said before.
- attribution: Draft 0.3 of the protocol
+ Here **Ada approves it herself**. The approval says so, and the company
+ knows whether it came from her or from her agent.
+ attribution: Poppy 1.0, with version 3 of the Operations extension
notes: >-
- In draft 0.3 the personal agent must ask the person about each operation,
- and no permission replaces that. Text from the company is never an
- approval, and the model can explain a proposal but cannot accept it. A
- company that lets people allow an action ahead of time simply does not
- return an operation for it.
+ At 1.0 every approval names its approver, the person or the personal
+ agent. Her agent may approve only on an instruction Ada gave it in its
+ own interface, and only when its check shows the terms fall within it;
+ every doubt goes to Ada. The company sees which it is and may decline an
+ approval her agent gave. Text from the company is never an approval, and
+ the model can explain a proposal but cannot accept it.
- id: approved-or-not
type: comparison
title: What Ada’s answer does
@@ -101,7 +104,7 @@ slides:
- label: The agent
values:
- Sends the same request with her approval
- - Tells the company no
+ - Sends nothing
- label: The company
values:
- Performs that exact revision
@@ -111,7 +114,8 @@ slides:
- Exchanged, USD 70.00 charged
- Stays as it is
notes: >-
- She may say no, and then nothing happens. If she approves, her approval
+ She may say no, and then her agent sends nothing, nothing happens, and the
+ operation simply expires. If she approves, her approval
covers one revision. If the terms change, the company returns a new
revision and Ada is asked again: approving version one never approves
version two.
@@ -147,14 +151,14 @@ slides:
Ada does not have to trust the model’s reading of a chat, and the company
does not have to trust that a chat message meant yes. Both hold the same
exact terms, and the company’s record keeps the revision that was
- approved and when.
+ approved, who approved it, and when.
- id: run-it
type: closing
title: Run it yourself
cta: The next case turns it round, Your Application, a Company.
notes: >-
- This case is played from the SDK’s demo company and described at draft
- 0.3 of the protocol, with version two of the Operations extension. The
- Operations example flow shows the exact revision, new terms, and a lost
- answer sent again.
+ This case is played from the SDK’s demo company and described at version
+ 1.0 of the protocol, Poppy 1.0, as published, with version 3 of the
+ Operations extension. The Operations example flow shows the exact
+ revision, new terms, and a lost answer sent again.
`;
diff --git a/src/decks/pap-two-companies.ts b/src/decks/pap-two-companies.ts
index 5e759194..4d459f2b 100644
--- a/src/decks/pap-two-companies.ts
+++ b/src/decks/pap-two-companies.ts
@@ -14,7 +14,7 @@ slides:
type: title
title: Two Companies Together
subtitle: An accounting firm pays a bill at Ada’s bank, and every payment is Ada’s approval.
- meta: Personal Agent Protocol · draft 0.3 · a case
+ meta: Personal Agent Protocol · 1.0 · a case
notes: >-
Ada’s accounting firm pays her suppliers from her bank account. That means
one company acting for a person at another company, with real money, and
@@ -43,7 +43,7 @@ slides:
type: statement
title: Composition, not a new protocol
statement: >-
- Draft 0.3 defines **no company-to-company protocol**. Two ordinary
+ Poppy 1.0 defines **no company-to-company protocol**. Two ordinary
relationships, for the same person, are enough.
notes: >-
There is no special protocol between companies. To Atlas, Ledgerly is a
@@ -69,9 +69,9 @@ slides:
sees her bank password**.
notes: >-
Before it can do anything at the bank, Ledgerly needs Ada’s Northwind
- account. Ada approves Ledgerly on Northwind’s own page, with a code. It is
- the same sign-in any personal agent would ask for, and the password never
- leaves the bank.
+ account. Ada approves Ledgerly on Northwind’s own page, with a code, and
+ the page lists every permission Ledgerly asks for. It is the same sign-in
+ any personal agent would ask for, and the password never leaves the bank.
- id: what-happens
type: mermaid
title: The first payment
@@ -95,7 +95,8 @@ slides:
Northwind proposes the payment and does not make it yet. Ledgerly passes
the proposal on to Ada, quoting the bank as written. Ada approves. Ledgerly
checks that the bank’s revision has not changed, sends the bank the
- approval of that exact revision, and relays what the bank says it did.
+ approval of that exact revision, saying that Ada approved it, and relays
+ what the bank says it did.
- id: every-payment
type: comparison
title: “Pay Acme without asking me each time”
@@ -103,18 +104,24 @@ slides:
- Amount
- What happens
rows:
- - label: INV-0042
+ - label: INV-0042, approved by Atlas
values:
- EUR 1250.00
- - Paid, with Ada’s approval
+ - Declined by Ledgerly, nothing sent
+ - label: INV-0042, approved by Ada
+ values:
+ - EUR 1250.00
+ - Paid
- label: INV-0043
values:
- EUR 980.00
- Waits for Ada’s approval
notes: >-
- Ada asks not to be bothered, and the answer is no. Every operation the bank
- returns goes to Ada, this one and the next, and nothing approves one in
- her name. So the next bill, INV-0043, waits for her like the first did.
+ At 1.0 Atlas may approve on an instruction Ada gives it, and the approval
+ says so. Ledgerly declines that for a payment, before anything reaches
+ the bank: it tells Northwind that Ada approved, and only her own approval
+ makes that true. So Ada approves INV-0042 herself, and the next bill,
+ INV-0043, waits for her like the first did.
- id: seen
type: two-columns
title: What the model sees
@@ -123,7 +130,7 @@ slides:
type: bullets
items:
- Summaries, as the companies wrote them
- - Who approved each payment
+ - Who approved each payment, Ada or her agent
right:
heading: Never
type: bullets
@@ -141,15 +148,16 @@ slides:
Firms can work for a person across companies, and **the person’s approval
reaches the bank intact**.
notes: >-
- Northwind’s records show the exact revision approved and when. Ledgerly can
- only ever carry an approval Ada gave. No company needed a bilateral
+ Northwind’s records show the exact revision approved, that Ada approved
+ it, and when. Ledgerly only ever carries an approval Ada gave herself. No company needed a bilateral
integration, and no new protocol was invented.
- id: run-it
type: closing
title: Run it yourself
cta: The Two companies example flow runs all three parties in one process.
notes: >-
- This case is the SDK’s own demonstration, described at draft 0.3 of the
- protocol, with Ledgerly and Northwind Bank as demo companies. Read the
+ This case is the SDK’s own demonstration, described at version 1.0 of the
+ protocol, Poppy 1.0, as published, with Ledgerly and Northwind Bank as
+ demo companies. Read the
Operations guide for approvals, and the company guide to build either side.
`;
diff --git a/src/decks/pap-your-application-a-company.ts b/src/decks/pap-your-application-a-company.ts
index eb0d8d96..07a38b46 100644
--- a/src/decks/pap-your-application-a-company.ts
+++ b/src/decks/pap-your-application-a-company.ts
@@ -14,7 +14,7 @@ slides:
type: title
title: Your Application, a Company
subtitle: An application answers people’s own agents as a company does.
- meta: Personal Agent Protocol · draft 0.3 · a case
+ meta: Personal Agent Protocol · 1.0 · a case
notes: >-
So far a person’s agent has gone to a shop. Now look from the other side.
You built an application, and you want people’s own agents to use it.
@@ -44,15 +44,16 @@ slides:
title: What the Maker makes public
items:
- Its own domain, with the page personal agents read first
- - "How agents reach it: its agent, its API and its server for agents"
+ - "How agents reach it: its agent, described in a line, its API and its server for agents"
- "What it offers: orders:read and orders:write"
- - What changes something is proposed, and done only with the person’s approval
+ - What changes something is proposed, and done only once it is approved
notes: >-
- The Maker turns on working with personal agents, and names what the
- application offers. That publishes one page at the application’s own
- domain, which says how to reach it and how a person signs in. What changes
- something is an operation the application proposes, never something an
- agent may simply do.
+ The Maker turns on working with personal agents, names what the
+ application offers, and describes in a line what its agent answers
+ about, which 1.0 requires. That publishes one page at the application’s
+ own domain, which says how to reach it and how a person signs in. What
+ changes something is an operation the application proposes, never
+ something an agent may simply do.
- id: what-happens
type: mermaid
title: What happens
@@ -105,12 +106,14 @@ slides:
detail: Once, with the application’s own code, on exactly those terms
- label: "3"
title: Records
- detail: Which agent, which revision, approved by Sam and when
+ detail: Which agent, which revision, who approved it and when
current: true
notes: >-
When the approval arrives, the application checks that this Session may
approve, that the action has not been performed already, and that the
- revision is one it returned, unexpired, for exactly this request. Its own
+ revision is one it returned, unexpired, for exactly this request. Every
+ approval says who gave it, Sam himself or his agent on an instruction
+ from him, and the application may decline one his agent gave. Its own
code does the work once, and the record keeps the approval.
- id: why
type: statement
@@ -120,14 +123,16 @@ slides:
with its rules intact and no integration built for each of them.
notes: >-
The Maker writes no integration per agent, and does not give up control.
- Sign-in stays on the application’s page, what anybody may ask is what the
- Maker allowed, and every change is approved by the person it affects.
+ Sign-in stays on the application’s page, shown every time, what anybody
+ may ask is what the Maker allowed, and every change is approved, with the
+ approval saying who gave it.
- id: run-it
type: closing
title: Build one
cta: The next case puts two companies together, Two Companies Together.
notes: >-
- This case is a story, described at draft 0.3 of the protocol. The SDK’s
+ This case is a story, described at version 1.0 of the protocol, Poppy
+ 1.0, as published. The SDK’s
company kit is how an application takes this role: the company guide
shows it, and the reference company in the SDK is built that way.
`;
diff --git a/src/reactor.ts b/src/reactor.ts
index 833a7f31..ed00c48a 100644
--- a/src/reactor.ts
+++ b/src/reactor.ts
@@ -371,7 +371,7 @@ export function createPapCorePlugin(options: PapCoreOptions = {}) {
}
return definePlugin({
name: "@datalayer/personal-agent-protocol-core",
- version: "1.0.0",
+ version: "1.0.1",
contributionPoints: [
DiscoveryTransports,
UrlSafetyPolicies,