Private Trust Task types registered under https://real-life.org/trust-tasks/ by the Real Life Trust Protocol (ToIP DTGWG Trust Tasks 0.4 (draft), §6.5 private specifications).
Machine-readable registry: index.json — every type with its Type URI, payload-schema URL, defining section and SHA-256 digest. Each payload schema resolves as raw JSON at <Type URI>/schema.json.
| Type | Defined in | |
|---|---|---|
access-operation/0.1 | RLTP Membership Tasks 3.3 | The generic carrier for Access-layer operations crossing the replica boundary, incl. the member.add admission profile and the welcome seal. |
delivery-ack/0.1 | RLTP Delivery Contract 4.2 | The arrival acknowledgement: proof-carrying, terminal, arrival-only semantics. |
encounter-bundle/0.1 | RLTP Delivery Contract 4.1 | The one-scan transmission: the scanner's sent card and step credential. |
encounter-credential-delivery/0.1 | RLTP Delivery Contract 4.3 | Post-enactment delivery of a step credential (counter-step or standalone). |
key-delivery/0.1 | RLTP Access Layer 10.1 | Epoch key material to a specific party, and the authenticated request for it: transition key envelopes, welcomes and re-welcomes, refreshes under the key service duty. |
membership-accept/0.1 | RLTP Membership Tasks 3.2 | The consent artifact: signed by the person consenting, content-bound to exactly one invitation. |
membership-evidence/0.1 | RLTP Membership Tasks 3.4 | The evidence relay: the complete invite and accept documents, enclosed, so any authorized member can admit. |
membership-invite/0.1 | RLTP Membership Tasks 3.1 | The invitation: no key material, invitee signed into the payload, inviter card and validity window. |
removal-notice/0.1 | RLTP Access Layer 10.2 | The compact notice a removed member is owed: it states the removal without carrying the transition-bearing envelope, which never crosses the replica boundary. |