Skip to content

0.14.4

Choose a tag to compare

View all tags
@jithinraj jithinraj released this 19 May 03:02
· 46 commits to main since this release
v0.14.4
01d88e7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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.

Assets 2
Loading