Add Agent Action Records section - #82
Conversation
Adds a section for standards and services that record and verify what an agent actually did (signed, offline-verifiable action records/receipts/logs), distinct from Agent Identity & Attestation (who the agent is). Seeds it with Agent Action Capsule, capsule-anchor, and capsule-emit, and moves three existing entries that fit it better — Nobulex, PIC Standard, and Signed Decision Receipts. Also adds scitt-cose under Agent Identity & Attestation. Signed-off-by: Steven Mih <stevenmih88@gmail.com>
|
🟡 Contributor Check: MEDIUM
Automated check by AgenTrust Contributor Check. |
github-actions
Bot
added
the
needs-review:MEDIUM
imran-siddique
left a comment
imran-siddique
left a comment
There was a problem hiding this comment.
Merging. The section is a real axis and the disclosure is what makes it mergeable.
On the axis. "What the agent did" and "who the agent is" are different questions and they were being answered in the same section because there was nowhere else to put the first one. Nobulex, PIC Standard and Signed Decision Receipts were all filed under Attestation or Standards for want of a better home, and the section makes that legible rather than inventing a category.
On the disclosure, which is the part that decides it. Four of seven entries being yours is a structural favour, and a section whose shape you propose and whose contents you mostly supply is exactly the submission I would decline if the relationship had to be inferred by a reviewer. You named all four projects, said plainly which entries are others' work, and stated the licensing. That converts it from something I have to investigate into something I can check.
What I checked rather than took:
agent-action-capsule,capsule-anchor,capsule-emitandscitt-coseall exist, all pushed within the last three days.draft-mih-scitt-agent-action-capsuleanddraft-farley-acta-signed-receiptsboth resolve at the IETF datatracker.- The diff moves the three existing entries rather than duplicating them, which is what makes this a reorganisation rather than an expansion of your own footprint.
One correction for the record, not blocking. The disclosure says "All four of mine are Apache-2.0". agent-action-capsule is BSD-3-Clause; the other three are Apache-2.0. Both are permissive OSI licences so nothing about eligibility changes, and the entry text does not repeat the claim. Worth knowing since you will presumably reuse that sentence.
2 participants
What & why
Proposes a new Agent Action Records section: standards and services for recording, attesting, and verifying what an agent actually did — signed, content-addressed, offline-verifiable action records, receipts, and transparency logs.
This is a distinct axis from the existing Agent Identity & Attestation section (which is about who the agent is). Right now several action-record projects are filed under Standards or Attestation because there's no better home; grouping them makes the "prove what happened" category legible.
New entries
Moved (3 existing entries that fit the new section better)
Happy to adjust placement or leave those three where they were if you'd prefer — the moves are a suggestion, not a demand.
Disclosure
I maintain the action-state-group projects (AAC / capsule-anchor / capsule-emit / scitt-cose); the other entries in the new section are others' work that I believe genuinely belongs in this category. All four of mine are Apache-2.0 with published specs and running free services.