Skip to content

Add PACT, Decagon's personal agent protocol on A2A - #15

Open
liady wants to merge 1 commit into
mainfrom
claude/poppy-support-alpic-663g6z
Open

liady wants to merge 1 commit into
mainfrom
claude/poppy-support-alpic-663g6z

Conversation

@liady

@liady liady commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

What this PR does

Adds a page for PACT, the Personal Agent Consent & Trust Protocol (/standards/pact), the 13th standard on ax.guide. It sits in Identity, after auth.md, with status Draft. Decagon open-sourced it with Instinct on October 6, 2026, the same day Poppy was announced, and it covers much of the same ground: a person's agent acting for them at a company. PACT is a layer on A2A rather than its own protocol, so people will mix the two up. The PR also adds a "Poppy vs PACT" pair to /compare, lists PACT next to Poppy on /which and on Poppy's page, and changes the "twelve" counts to thirteen.

What changed

  • New content/standards/pact.md, Identity, order 4 (map number 08), status draft.
    • Why draft: the spec and an Apache-2.0 repository are public, but no business or personal agent is publicly known to use it. Decagon's Personal Agent Gateway (October 1) names no customer using PACT.
    • How it works: discovery is an A2A Agent Card at /.well-known/agent-card.json. The personal agent signs a JWT, which the Provider checks against the agent's published keys after a one-time registration per Provider. Delegation is optional: OAuth device sign-in on the Brand's own page, with scopes each Brand defines, and step-up when a request needs more.
    • Versioning: the spec has no version number (the packages are 0.1.0) and no standards body.
  • A difference from Poppy, stated neutrally: PACT requires a stable, opaque sub per user. Its spec doesn't say whether that ID must differ between companies, as Poppy's per-company User ID must.
  • content/pairs.json: new poppy-vs-pact pair.
  • content/guide.json: the "customers' own agents should sign in and act on their accounts" situation now lists Poppy and PACT.
  • content/standards/poppy.md: PACT added to related.
  • "twelve" changed to "thirteen" in content/site.json (share image alt), content/home.json (the /compare card) and content/standards/ucp.md.
  • README.md table (npm run readme) and spec-pins.json (npm run pins) regenerated.
  • Spec pin: a git-path source on openpactprotocol/openpactprotocol docs/spec.md, pinned to the blob that was read (294e4bd…). node scripts/spec-drift.mjs check spec-pins.json --only pact reports ok.

Visible side effects:

  • Every standard after PACT shifts one number on the map and in the README (UCP 08 to 09, x402 12 to 13).
  • The README banner and map images are static screenshots and still show twelve standards. This PR doesn't regenerate them, and their alt text still describes those images.

Sources

Checklist

  • Every new or changed claim links a primary source.
  • If I changed a status, the evidence meets the rules in content/contribute.md. (New page at draft: spec published, no deployment publicly known.)
  • I only changed last_verified on pages where I rechecked every claim. (Set only on the new page, where every claim was checked against the sources above on 2026-10-21.)
  • Plain words, no em dashes.

Also checked locally:

  • npx vitest run (17 passed), npm run lint, npm run typecheck and npm run build (24 static pages).
  • Screenshots of /standards/pact, the home map, /compare and /which at 375px and 1280px, with no horizontal overflow.

Generated by Claude Code

A new Identity page for the Personal Agent Consent & Trust Protocol,
open-sourced by Decagon with Instinct on October 6, 2026. Status is
draft: the spec is public and no deployment is publicly known. It also
adds a Poppy vs PACT pair to /compare, lists PACT next to Poppy on
/which and on Poppy's page, and moves the "twelve" counts to thirteen.
The spec pin is the blob of docs/spec.md read on 2026-10-21.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FZAH9C7mzHaJ5Dts71A2SC
@vercel

vercel Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
standards Ready Ready Preview Oct 22, 2026 12:09am UTC

Request Review

This branch was successfully deployed

1 active deployment
Preview — 290a1b79 Deployed Oct 22, 2026 by vercel[bot]
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