specs/process_attestation/v0_1/payload
library
Classes
-
Artifact
-
Deterministic identification of the object whose production is in question.
-
Assessment
-
Opaque at the task layer. The task standardizes the interaction, not the receipt.
-
Disclosed
-
Only the categories the request asked for.
-
DisclosedAnchorsItem
-
DisclosedAnchorsItem, generated from its schema.
-
DisclosedDocument
-
DisclosedDocument, generated from its schema.
-
DisclosedIntegrity
-
DisclosedIntegrity, generated from its schema.
-
DisclosedTimeline
-
DisclosedTimeline, generated from its schema.
-
Payload
-
What a Verifier asks of a Holder: identify an artifact by digest, supply a
freshness challenge, and name the disclosure categories wanted. The outer document
members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the
framework — SPEC §6.3.
Extension Types
-
ArtifactAlgorithm
-
Carried verbatim from the IANA Named Information Hash Algorithm registry, not
re-cased — SPEC §4.10 externally-owned values.
-
DisclosedAnchorsItemKind
-
DisclosedAnchorsItemKind is a closed set of string values defined by this
specification's schema.
-
DisclosedIntegrityKeyCustody
-
DisclosedIntegrityKeyCustody is a closed set of string values defined by this
specification's schema.
-
DisclosureCategory
-
Derived aggregates only. An enum rather than a pattern so a primitive cannot widen
its own disclosure surface by inventing a name. The determination itself is not a
category: it is always in
assessment when the result is attested. Raw
behavioral samples and fingerprints are out of scope for 0.1.
Typedefs
-
Ext
= Map<String, dynamic>
-
Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a
reverse-DNS namespace; structure under each namespace is opaque to the framework.
-
ReceiptReference
= Object?
-
Tagged union. Inline exists for Verifiers that cannot dereference a URI at
verification time.
-
Response
= Object?
-
The Holder's answer. Failures use trust-task-error, not this shape. Both results
share one response type so the envelope carries no observable distinction between
them.
result is the discriminator and stays inside the payload, so one envelope
type covers both branches.