specs/trust_task_next_step/v0_1/payload library

Classes

Payload: The recipient-suggested continuation reserved at SPEC.md §8.6: the original task was understood, but cannot complete in isolation, and this names what the recipient party expects in order to proceed. A next step is neither a success response nor a failure. The originating task is left open — a consumer that means 'no' returns a trust-task-error instead, and one that means 'done' returns the originating specification's #response variant. This specification declares no response anchor: a producer answers a next step by issuing a document of the expected type, not by responding to this one.
PayloadExpectsItem: PayloadExpectsItem, generated from its schema.
PayloadInResponseTo: Identifies the Trust Task document this next step answers. SHOULD be populated, for the reason SPEC §8.2 gives for the identical member on an error response: threadId correlates the exchange only for a party that already saw the request, so a retained next step otherwise names neither the task it interrupted nor the instance.

payloadSchemaJson → const String: This specification's payload schema, as JSON text.
spec → const SpecPolicy: The SPEC §7.2 policy for the request variant, taken from this specification's front matter.
typeUri → const String: The Trust Task type URI this library's Payload is carried under.

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.