Syngraphe Countersign receipt profile v1

What a relying party receives today

The issued receipt schemas on this source revision are https://syngraphe.org/schemas/ai-interaction-receipt/v1 (schemas/ai-interaction-receipt-v1.schema.json), https://syngraphe.org/schemas/ai-interaction-receipt/v2 (schemas/ai-interaction-receipt-v2.schema.json), and https://syngraphe.org/schemas/internal/platform-emitter-receipt/v1 (schemas/platform-emitter-receipt-v1.schema.json).

The v1 and v2 interaction schemas contain the eight members required by https://syngraphe.org/schemas/internal/receipt-profile-v1/receipt under the same names; those eight members are the mapping to the profile receipt, while the remaining issued members stay outside that closed internal schema. The platform-emitter receipt is a batch-authority record and is not covered by receipt profile v1.

https://syngraphe.org/schemas/countersign-scitt-receipt/v1 (schemas/countersign-scitt-receipt-v1.schema.json) maps a statement digest to a transparency-inclusion receipt, and https://syngraphe.org/schemas/verified-receipt-projection/v2 (schemas/verified-receipt-projection-v2.schema.json) maps a receipt digest to a derived verification projection; neither is an issued interaction-receipt shape or a member of the internal receipt-profile-v1 family.

The receipt profile is PROPOSED until C2-A admission.

Every in-scope exchange resolves to a receipt or a signed gap, and no link's verification requires the cooperation of any party: customer, provider, cloud, code host, or Syngraphe.