Merged
Conversation
…mance vectors - Add PEAC-PROOF-RFC9421.md normative profile spec defining how receipts capture RFC 9421 HTTP Message Signature verification results - Add extension schema (specs/extensions/rfc9421-proof/0.1/schema.json) for validating the org.peacprotocol/rfc9421-proof@0.1 extension payload - Add 5 conformance vectors: verified-signature, expired-signature, key-not-found, base-mismatch, verified-full-metadata - Update manifest.json with rfc9421-proof fixture entry Design decisions: - Extension lives on http.request interactions (no new registry entries) - Three-state result: verified/failed/unavailable (DD-49 alignment) - Privacy by construction: covered_components = names only, never values - canonical_base_sha256 for audit trail (not raw base string)
- Add RFC 9421 proof profile to SPEC_INDEX.md and specs/README.md - Create conformance test validating fixtures against both InteractionEvidenceV01Schema (Zod) and extension JSON Schema (Ajv) - Change "Minimum PEAC Version" to "Introduced in" in profile spec
Add Related Profiles section to TRANSPORT-PROFILES.md linking to PEAC-PROOF-RFC9421.md for discoverability. Filed #380 for fixture versioning model follow-up.
Create PROFILES.md as the central index for transport, proof capture, and wire format profiles. Links from SPEC_INDEX.md and TRANSPORT-PROFILES.md. Documents design principles (independence, verification equivalence, extension-based, three-state results) and lists upcoming profile categories.
jithinraj
changed the title
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.
Summary
docs/specs/PEAC-PROOF-RFC9421.md) defining how receipts capture RFC 9421 HTTP Message Signature verification resultsspecs/extensions/rfc9421-proof/0.1/schema.json) for validating theorg.peacprotocol/rfc9421-proof@0.1extension payloadspecs/conformance/fixtures/manifest.jsonwith the new fixture entryDesign decisions
http.requestinteractions -- no new registry entries needed (http.requestkind already exists)verified/failed/unavailable(DD-49 alignment with policy binding model)covered_componentscontains component names only (e.g.,@method,content-digest), never actual header valuescanonical_base_sha256: SHA-256 hash of the signature base string for audit trail, preferred over storing the raw base stringsig_valid,sig_expired,sig_future,sig_key_not_found,sig_alg_unsupported,sig_base_mismatchTest plan
pnpm build && pnpm lint && pnpm typecheck:core && pnpm test-- all pass (3734 tests)bash scripts/guard.sh-- all checks passpnpm format:check-- cleanbash scripts/check-planning-leak.sh-- cleaninteractioncategory)