Skip to content

v0.3.3 — CTEF envelope-shape alignment

Latest

Choose a tag to compare

@kenneives kenneives released this 10 Jun 19:01
· 16 commits to main since this release

Composable Trust Evidence Format v0.3.3 — published 2026-06-10. CTEF-scoped.

Envelope-shape alignment (RFC 9421 wire-signing, #1829)

  • wire_binding block — optional/additive; RFC 9421 signature-input components + RFC 9530 content-digest, binds the claim to the wire bytes the verifier saw.
  • claim_type tag parametertag= on Signature-Input equals the envelope claim_type; gateway discriminates by byte match. RECOMMENDED.
  • Two-canonicalization binding — wire content-digest + structured JCS, formally bound; neither subsumes the other.
  • Backward-compatible — additive/optional; no change to existing-field JCS, so the 8 byte-match implementations validate the unchanged surface.

Error vocabulary (published)

18 codes / 5 layers (wire / identity / authority / continuity / correlation), every code structural + fail-closed. Live at /.well-known/ctef-error-codes.json; #1496 §5 negative paths mapped.

In-flight (cross-spec, non-blocking)

Unified error-enum umbrella (aeoess/agent-governance-vocabulary), exact wire_binding field names (#1829 final), cross-extension fixture matrix, a2a-1496-negative-paths/ directory.

Read

Next: v0.4 trust-gated payments + transactional claim_type (pre-execution-verdict-v0 envelope + verifier-side reference fixture).