Skip to content

docs: stop describing the seal as bound to an attested measurement - #169

Merged
imran-siddique merged 1 commit into
mainfrom
docs/honest-claims
Sep 14, 2026
Merged

docs: stop describing the seal as bound to an attested measurement #169
imran-siddique merged 1 commit into
mainfrom
docs/honest-claims

Conversation

@imran-siddique

Copy link
Copy Markdown
Member

The JSON-LD on every docs page described "a sealed peer channel bound to the peer's attested measurement". The README says binding the seal to a verified attested measurement on a live call "is on the roadmap". The description now says the channel is sealed and that the binding is on the roadmap.

Also in this PR

  • SPONSORS.md and ADOPTERS.md name OPAQUE as sponsor without the ownership disclaimer.
  • The social card alt text no longer calls cA2A "an AgenTrust open standard".

Left alone on purpose: the README's "A2A (Linux Foundation / AAIF)" row is correct, since A2A became an AAIF project on 2026-08-17.

Checked: each edit asserted its old text existed once; the JSON-LD block still parses.

Generated with Claude Code

https://claude.ai/code/session_013aK3gVWzNdcM3hZ2o2awK2

The structured data on every docs page said the sealed peer channel is bound
to the peer's attested measurement. The README says binding the seal to a
verified measurement on a live call is on the roadmap. The description now
says that.

Also: SPONSORS.md and ADOPTERS.md name OPAQUE as sponsor without the ownership
disclaimer, and the social card alt text no longer calls cA2A a standard.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013aK3gVWzNdcM3hZ2o2awK2
@imran-siddique
imran-siddique merged commit b36f290 into main Sep 14, 2026
13 checks passed
@imran-siddique
imran-siddique deleted the docs/honest-claims branch September 14, 2026 16:47
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.

1 participant