specs/push/provision/v0_2/payload library

Classes

Payload: The controller VTA sets a wake handle's trigger allowlist on the push gateway — the DIDs permitted to wake the device. The gateway accepts it only from the handle's recorded controller VTA and enforces it on every push/wake. See the push wake-up binding (https://trusttasks.org/binding/push/0.1).
Response: Push Provision — response payload
WakeTriggerPolicy: VTA-owned allowlist of the DIDs permitted to trigger a wake for a given WakeHandle (push wake-up binding, https://trusttasks.org/binding/push/0.1). The VTA is the source of truth for this policy — all device config state resides at the VTA — and provisions it to the gateway, which ENFORCES it: a wake request from a DID not on the list is refused. Typically holds the device's mediator DID (queue-driven wake, where the mediator alone knows the device is offline) and/or the VTA's own DID (policy-driven wake, e.g. a step-up the VTA is delegating to this device).

payloadSchemaJson → const String: This specification's payload schema, as JSON text.
responsePayloadSchemaJson → const String: As payloadSchemaJson, for the success-response variant.
responseSpec → const SpecPolicy: The SPEC §7.2 policy for the success-response variant.
responseTypeUri → const String: The success-response form of typeUri (SPEC §4.4.1).
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.