Skip to content
PPCP
Draft proposal · 0.1.1

Changelog

Versions, kept apart

Two version numbers exist here and they mean different things. Confusing them is exactly the kind of mistake this proposal asks implementations to avoid.

Download CHANGELOG.md

PPCP changelog

Protocol version: 0.1.1 · Website software version: 0.1.0-alpha.4 Canonical: https://ppcp.jardenberg.net/CHANGELOG.md License: CC BY 4.0, Joakim Jardenberg.

Protocol

0.1.1 — 2026-09-16

  • Added freshness, version identity, complete catalog discovery and compatibility guidance.
  • Distinguished source editions, HTTP caching, MCP freshness hints and host adoption.
  • Documented optional catalog diagnostics and the limits of signatures and version-tool checks.
  • No new required profile fields. Preserved the 0.1.0 specification and schema for existing documents.

0.1.0 — 2026-09-13

  • Initial PPCP proposal, renamed and expanded from the Public Context Profile working concept.
  • Static/download, discovery and read-only MCP bindings.
  • Public/private separation with whole-person scope.
  • Version, provenance, rights and receiving-agent authority distinctions.
  • First reference profile at joakim.jardenberg.net.

Website software

0.1.0-alpha.4 — 2026-09-16

  • Linked the public protocol repository at https://github.com/jardenberg/ppcp from the site navigation, footer, home page and llms.txt, with an invitation to read, fork or raise an issue at https://github.com/jardenberg/ppcp/issues.
  • The repository holds the published protocol editions 0.1.0 and 0.1.1, schemas, fictional examples, a portable validation helper, contribution guidance and the licence. It is not this website's application source, it is not automatically synchronised with this site, and it implies no external ratification.
  • Website software only. Protocol draft 0.1.1, both specification editions, schemas, examples, the validator and the separate reference profile and MCP server are unchanged.

0.1.0-alpha.3 — 2026-09-16

  • Published PPCP draft 0.1.1 with new section 11 on freshness, updates and compatibility; sections 1–10 and their anchors are unchanged.
  • Preserved the exact 0.1.0 specification text at https://ppcp.jardenberg.net/spec/0.1.0.md and added a stable https://ppcp.jardenberg.net/spec/0.1.1.md; /spec.md remains the latest pointer.
  • Added https://ppcp.jardenberg.net/schema/profile-0.1.1.json with the same fields and constraints as 0.1.0; https://ppcp.jardenberg.net/schema/profile-0.1.0.json is unchanged byte-for-byte.
  • Validator now selects the schema matching the document's declared ppcp_version (0.1.0 or 0.1.1), reports which version it validated, and rejects missing or unsupported versions. It still runs entirely in the browser with no upload.
  • Added a plain-language Keeping context current overview and a practical freshness guide on the MCP page.
  • Recorded dated reference-server evidence from independent production testing on 2026-09-16 at 12:42:36Z: software 0.1.0-alpha.8, profile 0.6, declared PPCP 0.1.0, all 6 tools exercised across MCP 2026-07-28, 2025-11-25 and 2025-06-18, 27 signed tool, resource and error responses verified, and both official Verifiable MCP v0.2.1 verifiers passing 9 vectors including negatives plus a live signed version-tool check.
  • No external model-facing host inventory (ChatGPT, Claude or others) was checked. This is dated reference-server evidence, not protocol-wide certification or a current unbounded guarantee.
  • Replaced the earlier pending-error-correction and 13 September-only status language, while keeping the historical hosting limitation on record without implying it was resolved.
  • Host refresh instructions are dated implementation guidance linked to the host's own documentation, not permanent PPCP rules.

0.1.0-alpha.2 — 2026-09-13

  • Reference MCP server is live: selected live tool and resource signatures independently verified · 13 September 2026.
  • Status panel updated from pending to live reference MCP; protocol-wide or client-wide certification is not implied.
  • Added links to the reference server card and /api/health as self-reported status, kept distinct from independent verification.
  • Documented hosting observation: Cloudflare Browser Integrity Check returns 403 error code: 1010 for Python-urllib/3.11; empty and descriptively named user agents worked in our check. No supported Lovable exemption is exposed; support escalation is needed.
  • No guaranteed automatic discovery or arbitrary-client compatibility is claimed.

0.1.0-alpha.1 — 2026-09-13

  • First working release of the PPCP documentation site.
  • Full specification, Markdown source, JSON Schema, examples, browser-only validator.