cpb: provisional Artifact Type entry for verifiable-agent-conversation (Henk review) - #44
Open
StevenMih wants to merge 2 commits into
Open
Conversation
Re-render from 1e1edb2 (Iman Schrock confirmed 2026-07-24, line as written per email). No source changes — artifacts only. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds spec/cpb-provisional-registry.md — a companion file that tracks proposed CPB Artifact Type registry entries under discussion with artifact-type owners. Entries here target CPB -01 or later; none enter the -00 text. First entry: `verifiable-agent-conversation` (owner: Henk Birkholz, draft-birkholz-verifiable-agent-conversations-00). All digest-context parameters are [OWNER TO CONFIRM] because -00 does not specify a CPB-compatible canonicalization algorithm for verifiable-agent-record payloads. The content-hash in trace-metadata is SHA-256 hex of raw payload bytes with no normalization step defined; the exclusion set, canonicalization algorithm, and preferred type name all need Henk's input before this entry can be finalized. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
Author
|
@henkbirkholz — the conversation-container registry entry, drafted strictly from your -00's text; every digest-context field is deliberately [OWNER TO CONFIRM] and merges only on your approval. Full context in my email." |
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
1 participant
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.
Purpose
Proposes a provisional Artifact Type registry entry for the
verifiable-agent-conversationtype (draft-birkholz-verifiable-agent-conversations-00) to the CPB Artifact Type Registry (§11.2 of draft-mih-sokolov-scitt-payload-binding-00).This PR merges only on your approval. Edit or close freely.
What is here
A new file
spec/cpb-provisional-registry.md— a companion tracking file for CPB registry entries under discussion with artifact-type owners. The entry forverifiable-agent-conversationquotes the relevant structures from your draft and marks every digest-context parameter as[OWNER TO CONFIRM]because draft -00 does not specify a CPB-compatible canonicalization algorithm.Fields requiring your input
verifiable-agent-conversationis suggested; confirm or substitute.content-hashintrace-metadatadescribes "SHA-256 hex digest of the payload bytes" but without a normalization step. For a CPB Artifact Type entry, we need a named algorithm (jcs-n / cde-n / new). Please specify.verifiable-agent-record(if any) are excluded before the derived identifier is computed?content-hash: tstr; please confirm.What this is NOT
verifiable-agent-recorda stable CPB-addressable type, if you want one.Context
Steven Mih will follow up separately. This PR exists so you have a concrete artifact to react to rather than an abstract ask.
🤖 Generated with Claude Code