docs: update specification overview for v0.4.0 release#624
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the public specification overview page to align with the Agent Receipt Protocol v0.4.0 documentation, reflecting the new action.idempotency_key concept, updated verifier guidance, and a clearer positioning of the protocol relative to related standards/projects.
Changes:
- Bumped the spec overview badge from v0.3.0 to v0.4.0 and refreshed the “What’s new” callout for v0.4.0 (including
idempotency_keyand updated version acceptance guidance). - Clarified verifier behavior for duplicate non-empty
idempotency_keyvalues (warning, not failure). - Reorganized “Relationship to existing work” into “Normative ancestry” vs “Adjacent projects” with updated entries and an ecosystem link.
… table (closes #620) Bump the version badge from v0.3.0 to v0.4.0 (matching spec/v0.4.0/spec.md frontmatter: Version 0.4.0, Status Draft) and refresh the "What's new" aside to v0.4.0 so its version-acceptance note agrees with the Schema page (accepts 0.1.0-0.4.0, verifiers MUST accept all five). Rewrite "Relationship to existing work": split into normative ancestry (W3C VC 2.0, RFC 8785) and adjacent projects in the same Audit & Provenance layer (draft-sharif, W3C AIVS CG, Pipelock EvidenceReceipt, Microsoft AGT, Asqav, nono, InALign), with neutral one-line framing drawn from the May 2026 landscape. Remove the research-only entries (Grantex, AgentStamp, MolTrust). https://claude.ai/code/session_01TLtCmvdFbKLiWsTEN5Y9rn
DIDs are the identifier scheme for issuer and principal identities, so they belong with the normative ancestors rather than dropped alongside the removed research-only entries. https://claude.ai/code/session_01TLtCmvdFbKLiWsTEN5Y9rn
The Overview now links to the ecosystem landscape, which describes nono as Sigstore/Rekor anchored. Match that wording so the two pages agree on nono's signing scheme rather than describing it as in-toto/DSSE. https://claude.ai/code/session_01TLtCmvdFbKLiWsTEN5Y9rn
ojongerius
force-pushed
the
claude/quirky-mendel-w4jEq
branch
from
2af68e5 to
04aca7f
Compare
7 tasks
ojongerius
added a commit
that referenced
this pull request
May 25, 2026
Introduces `docs/operations/current.md` as the curated active-subgraph view of in-flight, blocked, and next work. Reduces ~77 open issues to ~15 active nodes with editorial overlay (closures, blocked-on-Otto framing, conflicts). Adds an "Operational state" pointer to AGENTS.md so agents and humans open this file at session start. Initial content includes the post-ADR-0021/0022 merge state with a verification pass: #597 and #614 closed, ADR-0022 PR #619 recorded, and the four closure-1 implementation PRs (#621/#623/#624/#625) recorded as in-flight rather than farmable.
5 tasks
ojongerius
added a commit
that referenced
this pull request
May 26, 2026
ojongerius
added a commit
that referenced
this pull request
May 26, 2026
* chore: remove committed binary and expand .gitignore Removes the accidentally committed agent-receipts Mach-O binary and adds /agent-receipts, /bin/, and /daemon/bin/ to .gitignore so built binaries cannot be committed again. * docs(ops): update current.md for 2026-05-26 Mark closure-1 nodes shipped (#621/#623/#624/#625/#628), add daemon-setup-stale-api and py-readme-daemon-refresh nodes, record #632/#633/#634, note #592 trusted-publishing blocker, refresh Next farmable section.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Updated the specification overview documentation to reflect v0.4.0 changes, including the new
idempotency_keyfield, updated verifier rules, and a reorganized "Relationship to existing work" section that distinguishes normative ancestry from adjacent projects.Why
The v0.4.0 release introduces idempotency tracking to help verifiers distinguish legitimate retries from duplicate emissions. The documentation needs to reflect this new capability and the updated version support matrix. Additionally, the relationship section has grown and benefits from clearer categorization to help readers understand which standards are foundational (normative ancestry) versus which projects are working adjacent problems (adjacent projects).
Changes
credentialSubject.action.idempotency_keyfield for stable operation identificationidempotency_keysurface as warnings, not failures"0.4.0"with guidance that new receipts SHOULD use itChecklist
https://claude.ai/code/session_01TLtCmvdFbKLiWsTEN5Y9rn