specs/push/register/v0_1/payload library

Classes

Payload

A device registers its platform push token (APNs / FCM / Web Push) with a push gateway and names the controller VTA permitted to provision its trigger allowlist. The gateway returns an opaque WakeHandle; the raw token is held by the gateway only. See the push wake-up binding (https://trusttasks.org/binding/push/0.1).

Response

Push Register — response payload

WakeHandle

An opaque, gateway-issued reference to a device's push channel (push wake-up binding, https://trusttasks.org/binding/push/0.1). The push gateway returns it to the device at registration; the device conveys it to its VTA (device/set-wake), and the VTA provisions it to authorized triggers (its mediator and/or itself). The raw platform push token (APNs/FCM/WebPush) is held ONLY by the gateway and is never represented here — the handle abstracts the platform, so adding new push methods (e.g. PWA Web Push) needs no change to triggers or VTA config. A handle is a bearer capability to request a wake (subject to the gateway's allowlist), never to read the channel.

Constants

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.

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.

PushRegistration = Object?

A device's platform push channel — the body the device registers with its push GATEWAY (push wake-up binding, https://trusttasks.org/binding/push/0.1; modeled on Aries RFC 0699/0734). The gateway holds this token and returns an opaque WakeHandle in exchange; the token is held by the gateway ONLY, never by the mediator or the maintainer/VTA. The gateway uses it to send a contentless wake-up when an authorized trigger asks — the push payload never carries Trust Task content. Tagged union over the discriminator platform.