Adoption records

SCITT

Version pinned

• RFC 9943, An Architecture for Trustworthy and Transparent Digital Supply Chains, June 2026, Proposed Standard (from draft-ietf-scitt-architecture-22).
• RFC 9942, CBOR Object Signing and Encryption (COSE) Receipts, June 2026, Proposed Standard (from draft-ietf-cose-merkle-tree-proofs-18).

What is taken

Nothing yet. RFC 9943 registers single-issuer signed statements with a Transparency Service that keeps an append-only verifiable data structure and returns a receipt proving registration. RFC 9942 defines those receipts as signed CBOR inclusion and consistency proofs. An evaluation will decide whether the A9 per-read receipt and the owner's hash-chained log can be expressed this way.

Why

SCITT-compatible receipt or transparency mechanisms are evaluated before a proprietary format is fixed, so the accountability log can align with a published transparency standard. The decision is due before a provider issues receipts from its read path. The reference implementation's stored chain keeps each event's exact signed bytes and refers to an event by its partition, position and hash, so either outcome can be added without rewriting them.

What is extended

Not yet decided.

What is replaced or not used

Until that decision, A9 keeps its JWS-signed, hash-chained receipts (see the JOSE record).

Deviations

Both SCITT documents were published as RFCs in June 2026, and this record cites the RFCs rather than the earlier Internet-Drafts.

Conformance checks

LOG-01 in the conformance manifest, with runtime evidence pending.

References to other standards and projects describe intended technical alignment only and do not imply endorsement or partnership.