Trust Protocol

RLTP Trust Task types

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). Every type is a URI at which its payload schema lives. Conforming implementations pre-register every schema by its $id and resolve nothing over the network at runtime.

Machine-readableindex.json

access-operation/0.1rltp-membership@0.16RLTP Membership Tasks · 3.3The generic carrier for Access-layer operations crossing the replica boundary, incl. the member.add admission profile and the welcome seal. delivery-ack/0.1rltp-delivery@0.79RLTP Delivery Contract · 4.2The arrival acknowledgement: proof-carrying, terminal, arrival-only semantics. encounter-bundle/0.1rltp-delivery@0.79RLTP Delivery Contract · 4.1The one-scan transmission: the scanner's sent card and step credential. encounter-credential-delivery/0.1rltp-delivery@0.79RLTP Delivery Contract · 4.3Post-enactment delivery of a step credential (counter-step or standalone). key-delivery/0.1rltp-access@0.54RLTP Access Layer · 10.1Epoch 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.1retired version, superseded by membership-accept/0.2 membership-accept/0.2rltp-membership@0.16RLTP Membership Tasks · 3.2The consent artifact: signed by the person consenting, subject equals issuer and the invite's invitee, content-bound by credential digest to exactly one invitation. membership-evidence/0.1rltp-membership@0.16RLTP Membership Tasks · 3.4The evidence relay: the complete invite and accept documents, enclosed, so any authorized member can admit. membership-invite/0.1retired version, superseded by membership-invite/0.2 membership-invite/0.2rltp-membership@0.16RLTP Membership Tasks · 3.1The invitation as a conformant DTG InvitationCredential: issued by the inviting member, subject is the invitee, no key material; bound to the membership thread. registry-declaration/0.1rltp-delivery@0.79RLTP Delivery Contract · 4.4Per-party declaration of fixed operational constants for a served role; the envelope is generic, each role's specification registers the constant names. removal-notice/0.1rltp-access@0.54RLTP Access Layer · 10.2The compact notice a removed member is owed: it states the removal without carrying the transition-bearing envelope, which never crosses the replica boundary.

Nothing matches the search.