Gateway Decision Evidence

Adds portable, signed evidence for terminal gateway access decisions using PEAC’s existing access-decision record and access extension.

Highlights

• Informative profile and integration guidance for issuing, abstaining, and verifying gateway decision records.
• Runnable offline-verifiable example with explicit issuer and key policy.
• Privacy, data-minimization, document-binding, and telemetry-correlation guidance.
• Improved developer documentation and repository entry points.
• Updated the qs resolution to patched version 6.15.2.

Compatibility

Wire remains 0.2. No public schema, registered record type, extension group, signing envelope, published package, or public protocol API changes.

Verification establishes record integrity and possession of the signing key. It does not independently establish that a decision occurred, was correct, was enforced, or that the issuer was authorized.

PEAC Protocol is an open-source project stewarded by Originary and community.

PEAC Protocol - Portable Evidence Pack

PEAC Protocol v0.16.2 expands portable, independently verifiable evidence for agent, API, tool, gateway, and payment workflows.

Highlights

• Added offline-verifiable examples for paid resources and paid MCP tool calls.
• Added evidence flows for counterparty acknowledgment, action approval, and agent-run lineage.
• Added runtime-export, external-anchoring, and agent-spend-attribution guidance.
• Added Merkle commitment and inclusion-proof helpers to @peac/audit.
• Preserved x402 settlement extensions for portable evidence.
• Improved OpenTelemetry correlation with peac.record.ref.

Compatibility

Wire format remains 0.2. This release introduces no public schema, receipt-type, extension-group, or API-contract changes. Existing integrations remain compatible.

PEAC records establish the integrity and internal consistency of the supplied evidence; they do not independently prove that every relevant real-world event was captured.

PEAC Protocol is an open-source project stewarded by Originary and community.

CLI Metadata Alignment

PEAC updates CLI observation and record metadata so platform.peac_cli_version is sourced from package metadata.

No wire-format, schema, signing, registry, or verification behavior change.

PEAC Protocol is an open-source project stewarded by Originary and community.

Deterministic Verification for Portable Records

PEAC v0.16.0 strengthens portable record verification across runtimes, with no wire-format or public schema change.

Changed

• Defined the PEAC Ed25519 verification profile across the TypeScript and Go implementations.
• Added raw I-JSON validation for JWS protected header and payload bytes before parsing.
• Added shared verification corpora for Ed25519 edge cases and raw I-JSON inputs.
• Added an optional bounded replay guard for consumers that need online replay detection after local verification.
• Raised the supported Node.js floor to >=22.13.0.

Compatibility

• Current record format remains interaction-record+jwt.
• Wire version remains 0.2.
• Existing Wire 0.2 records remain compatible.
• Wire 0.1 remains frozen legacy.
• No signing algorithm change.
• No public schema change.
• No CLI or Go SDK behavior expansion beyond the verification alignment above.

Upgrade

Update PEAC packages to 0.16.0.

npm install @peac/[email protected]

PEAC Protocol is an open-source project stewarded by Originary and community.

Portable signed records across AI and agent workflows

This release improves PEAC’s documentation, examples, and release metadata for portable signed interaction records across AI, agent, API, gateway, and verification workflows.

Highlights

• Adds an open-model inference example using existing PEAC record semantics.
• Adds an interop crosswalk for evaluation, audit, transparency, and agentic infrastructure contexts.
• Adds a concise evidence-primitive note for portable signed interaction records.
• Refreshes developer-facing guidance, verification paths, and integration references.
• Includes small documentation hygiene fixes and release metadata updates.

Compatibility

No migration is required.

This release does not change PEAC’s schema, registry, wire format, signing envelope, public API, CLI behavior, or package set. Wire format remains 0.2.

PEAC remains a records layer: it records what another system reported, binds it to issuer/time/context, and makes the record portable and verifiable across boundaries.

Verification

The release was validated with the full test suite, conformance tests, codegen-drift checks, registry validation, API-contract checks, semantic no-widening checks, and release-fact verification.

PEAC Protocol is an open-source project stewarded by Originary and community.

Verification and Signing Hardening

This release strengthens PEAC verification and signing-related surfaces without changing the wire format, public schemas, registered receipt types, or extension groups.

Highlights

• Adds request-shaped UCP HTTP Message Signatures verification.
• Hardens receipt verification failure behavior and SHA-256 boundary checks.
• Tightens Structured Field byte-sequence parsing for signature and digest handling.
• Keeps internal helper exports out of public package barrels.
• Refreshes security and advisory checks for release readiness.
• Adds a checked README quickstart path for offline sample generation and verification.

Compatibility

• Wire format unchanged: 0.2.
• Public schemas unchanged.
• Registered receipt types unchanged.
• Registered extension groups unchanged.
• No dependency or lockfile change.
• No breaking protocol change.

PEAC Protocol is an open-source project stewarded by Originary and community.

Samples and offline verification.

Makes the local verification path self-contained: generated samples now
pass local verification out of the box, and peac verify accepts a local
public key for fully offline verification. Aligns the MCP recipe,
quickstart, and distribution metadata with the current API, and adds a
gateway-mediated MCP records example with policy decisions and content
digests.

Public API: additive only (peac verify --public-key).
Wire format: unchanged (0.2).
Public schema: unchanged.
Registered extension groups: unchanged (19).
Registered receipt types: unchanged (61).
Conformance sections: unchanged (32).

Added

• peac verify --public-key <file>: offline receipt verification with a
  local Ed25519 public JWK or single-key JWKS; rejects private keys,
  multi-key sets, and non-Ed25519 keys; the network JWKS path is unchanged
  when the flag is omitted (#833).
• examples/mcp-gateway-receipts: gateway-mediated MCP tool calls with a
  signed tool-definition manifest, allow and deny decision records,
  deterministic content digests, redaction recorded as a fact, and two
  tamper checks; includes an in-process runtime smoke test and the
  docs/SOLUTIONS/mcp-gateway-receipts.md recipe (#834).
• Workspace package boundary gate: fail-closed test deriving published,
  private, and example surfaces from the publish manifest (#825).
• Release-process gates: split-stage release closeout verification (#826),
  dependency-audit exception expiry gate (#827), and an OpenTelemetry
  version-currency gate with a documentation version-currency check (#828).

Changed

• peac samples generate issues valid samples through the canonical
  issuance path so every generated record passes local verification;
  sample inputs validated before any write (#829).
• MCP tool-call recipe, INTEROP tool listing, server README, and the HTTP
  transport version log aligned with the current API and protocol version
  (#831).
• MCP Streamable HTTP quickstart: session header capture and reuse, current
  protocol version, modern _meta carrier demo with tamper checks, and
  current plugin-pack pins (#832).
• Repository surface streamlined: retired pre-0.10 archive tree removed
  from HEAD with name-based guards retained (#823).
• Emitted telemetry version derives from a single source (#828).

Fixed

• MCP HTTP quickstart issuer-key example emits an Ed25519 private JWK as
  the key loader expects (#835).
• vitest updated for GHSA-5xrq-8626-4rwp (#820); MCP Registry publisher
  workflow updated (#819); GitHub Actions runtime dependencies updated
  (#822).

Security

• Dependency-audit allowlist review dates renewed for dev-only exceptions
  (#830).

PEAC Protocol is an open-source project stewarded by Originary and community.

Interoperability for portable signed records

PEAC v0.15.0 refines the interoperability surface for portable signed records.

This release focuses on clearer records-first entry points, public interop references, and release metadata consistency. It does not change the wire format, signing envelope, public schema, public API, CLI surface, package-publication surface, or runtime behavior.

Highlights

• Refined the records-first front door for developers evaluating PEAC.
• Added and aligned interoperability references for record-carrier and composition surfaces.
• Added conformance vectors covering ERC-8126 and AP2-related record semantics.
• Added a COSE-Sign1 carrier design note for future signing-envelope interoperability.
• Updated workspace metadata, release metadata, and package version stamps for 0.15.0.

Compatibility

• Wire format remains 0.2.
• Published package count remains 36.
• Conformance requirement IDs remain 290.
• Existing integrations should not require code changes for this release.

Install

npm install @peac/[email protected]

For MCP server usage:

npx -y @peac/[email protected]

See the changelog for the complete file-level release notes.

PEAC Protocol is an open-source project stewarded by Originary and community.

Verification documentation

This release aligns PEAC's public documentation and release metadata with the current verification surface.

It updates security, SLO, stability, compatibility, README, MCP metadata, and release artifacts so reviewers and integrators can more easily understand what PEAC records, how records are verified, which surfaces are current, and which historical packages are archived.

Highlights

• Refreshes supported-version and security disclosure documentation.
• Adds measured local issue() and verifyLocal() SLO baselines.
• Marks reference-verifier and MCP rows as outside the measured baseline where no benchmark is published.
• Clarifies archived package status for historical compatibility surfaces.
• Aligns README and MCP metadata with records-first terminology.
• Preserves conformance requirement history while updating review metadata.
• Keeps PEAC's boundary explicit: PEAC records and verifies signed interaction records; it does not operate runtimes, enforce policy, authenticate actors, or settle payments.

Unchanged

• No wire-format change.
• No signing-envelope change.
• No schema change.
• No public API change.
• No CLI behavior change.
• No runtime behavior change.
• No package set change.
• No conformance-ID change.

The release preserves the current protocol counters: 19 extension groups, 61 receipt-type identifiers, 290 conformance requirement IDs, 32 conformance sections, 107 build targets, and 36 published packages.

PEAC Protocol is an open-source project stewarded by Originary and community.

Composition Surfaces

v0.14.4 adds practical composition guidance for using PEAC records across adjacent runtimes, tools, and verification surfaces without expanding the protocol boundary.

PEAC remains a portable signed-record layer. It records, preserves, verifies, and exports interaction records. It does not run workloads, enforce policy, authenticate runtimes, score systems, route requests, process payments, or replace adjacent protocols.

Highlights

• Added composition guidance for runtime governance, edge verification, evaluation workflows, harness records, and MCP tool-call contexts.
• Added a committed-fixture .NET quickstart verifier for offline verification of PEAC records.
• Added Go chi middleware parity coverage and documentation.
• Added runnable runtime-composition examples and smoke/doc-truth coverage.
• Refreshed release metadata, changelog, compatibility matrix, and example discoverability.

Composition surfaces

This release documents how PEAC records compose with systems that already own execution, routing, authorization, evaluation, or lifecycle control.

New and updated guidance covers:

• runtime-governance composition,
• edge-side record verification,
• evaluation-platform record capture,
• harness and bounded-command records,
• MCP composition and SEP-aligned boundaries.

The guidance is intentionally composition-first. PEAC records what happened in a portable form; the adjacent system remains responsible for its own runtime behavior.

Developer examples and adapter parity

This release adds:

• examples/runtime-composition-records/
• examples/dotnet-quickstart/
• chi middleware README and parity tests
• additional doc-truth and smoke coverage for the new examples and guides

The .NET quickstart is an example only. It is not a PEAC .NET SDK, does not introduce a NuGet package, and does not add a new package-publication surface.

Public surface

No protocol surface expansion.

Unchanged:

• Wire format
• public schema
• registries
• type URIs
• conformance requirement IDs
• public API
• CLI surface
• package-publication surface
• signing behavior

Package names are unchanged. The package count remains 36.

PEAC does not:

• host registries,
• route requests,
• implement external transports,
• enforce authorization policy,
• authenticate external runtimes,
• score systems,
• control execution,
• process settlement.

The release strengthens PEAC’s capabilities as a neutral records layer that composes with existing systems without absorbing them.

PEAC Protocol is an open-source project stewarded by Originary and community.