Skip to content

Trust Tasks

Every RLTP message is a Trust Task document of a private, versioned type, named https://real-life.org/trust-tasks/spec/<slug>/<version>, with in-band issuer and recipient anchors and no expiresAt. An unknown type is rejected, never silently ignored. The types target the Trust Tasks framework 0.6.0. A carrier that carries Trust Task documents itself carries every sealed message as the payload of one more type, sealed-envelope/0.1, whose parties are the carrier’s identifiers.

The types form one register, the task registry of the Delivery Contract. Each type is registered by the specification where its semantics live, which names its payload schema, its proof and its rules. Each type also declares, in the framework’s vocabulary, whose identifiers fill its parties, what it changes at the recipient, what it carries about people, what the recipient keeps, and its largest document: 65 536 bytes, 16 384 bytes for the invitation and the acceptance, and 90 112 bytes for sealed-envelope/0.1, which carries an encrypted document of up to 65 536 bytes. The declarations stand with each registration: Delivery §4.5 for its own types and the Trust Layer’s, Membership §3, Access §10, and Message Tasks §3.4.

The verifiable credentials some of these documents carry are listed under Credentials.

The two transmissions of the encounter ceremony (Encounter §5.8), registered by the Delivery Contract itself.

Type Carries Rules Schema
encounter-bundle/0.1 { card, credential }: the scanner’s sent card and step credential, in one scan Delivery §4.1 payload-encounter-bundle
encounter-credential-delivery/0.1 { credential }: a step credential after the scan, as counter-step or standalone delivery Delivery §4.3 payload-encounter-credential-delivery

The standing artifacts of the trust-layer family, the continuity tasks and the five steps of the introduction act. The payload is the artifact; the artifacts carry their own MACs or signatures, the documents carry no proof.

Type Carries Rules Schema
star/0.2 one chunk of a star@2: the contacts who gave you their community anchor, blinded per recipient Trust §5.2 · §5.2a · Delivery §4.4 visibility-star
group-star/0.1 one chunk of a group-star@1: your groups, blinded to every contact, your member anchor sealed to the ones you choose Trust §5.2b · Delivery §4.4 visibility-group-star
anchor-mapping/0.3 an anchor-mapping@4: links a pair anchor to the community anchor for one addressee Trust §6.1 · Delivery §4.4 visibility-anchor-mapping
profile/0.1 a profile@1: your name, with an optional picture and text, for one contact Trust §6b · Delivery §4.4 trust-profile
continuity-probe/0.1 a continuity-probe@1: blinded values, one per existing relationship, padded to a fixed size Trust §6a.2 visibility-continuity-probe
continuity-mapping/0.1 a continuity-mapping@1: chains a re-encounter to the existing relationship Trust §6a.4 visibility-continuity-mapping
introduction-request/0.1 { introduction, card }, requester to mediator: the request and the requester’s fresh card Trust §8.1 · §8.2 visibility-payload-introduction-request
introduction-forward/0.1 { introduction, card }, mediator to target: the request, byte-identical Trust §8.1 visibility-payload-introduction-forward
introduction-reply/0.1 { introduction, card }, target to mediator to requester: the reply and the target’s fresh card Trust §8.1 · §8.2 visibility-payload-introduction-reply
introduction-ack/0.1 { introduction }, mediator to requester: an introduction-ack@1, after a fixed delay Trust §8.1 · §8.4 visibility-payload-introduction-ack
introduction-voucher/0.1 { voucher }, mediator to each side: which fresh anchor belongs to the other Trust §8.1 · §8.5 visibility-payload-introduction-voucher

A text message from one contact to the other. The payload is the artifact; it carries its own MAC, the document carries no proof.

Type Carries Rules Schema
message/0.1 a message@1: a text of at most 4096 characters for one contact, deniable Message Tasks §3 · §4 message

Key material and the removal notice.

Type Carries Rules Schema
key-delivery/0.1 { keyDelivery }: epoch keys, welcomes, refresh material, and the request for them Access §10.1 payload-key-delivery
removal-notice/0.1 the signed notice object: tells a removed member of the member.remove Access §10.2 payload-removal-notice

The transport of membership changes: the Vorgespräch Der Austausch vor einer Einladung: Die einladende Person fragt über eine bestehende Beziehung nach dem Mitgliedsanker, den die eingeladene Person für die Gruppe ableitet, und bindet die Frage mit einer Signatur unter ihrem eigenen Mitgliedsanker an diese Beziehung. Die Antwort trägt eine Karte an diesem Anker. Die Bindung ordnet die folgende Einladung der Beziehung zu. GlossarPrelude The exchange before an invitation: the inviter asks, over an existing relationship, for the member anchor the invitee derives for the group, and binds the question to that relationship with a signature under its own member anchor. The answer carries a card at that anchor. The binding attributes the invitation that follows to the relationship. Glossary that precedes an invitation, invitation, consent, the admitting operation, and the evidence relay. A sender issues membership-evidence/0.2; a receiver also accepts /0.1 (RLTP-MT-3815).

Type Carries Rules Schema
membership-prelude-request/0.1 { genesisDigest, group, name, inviter, binding }: the inviter asks, on an existing relationship, for the invitee’s member anchor; the binding is signed under the inviter’s member anchor, the document under the sender’s pair anchor Membership §3.5 payload-membership-prelude-request
membership-prelude-reply/0.1 { genesisDigest, card }: the invitee’s card at its member anchor for the group, signed under the invitee’s pair anchor Membership §3.5 payload-membership-prelude-reply
membership-invite/0.2 { invite }: a DTG InvitationCredential, with no keys and no operation Membership §3.1 payload-membership-invite
membership-accept/0.2 { accept }: the invitee’s signed consent to exactly one invite Membership §3.2 payload-membership-accept
access-operation/0.1 { operation, welcome }: the admitting member.add and its Willkommen Das versiegelte Dokument rltp-welcome/0.1, das einer aufgenommenen Person das Schlüsselmaterial eines Schlüsselzustands bringt, gebunden an Gruppe, Person und die beantwortete Annahme. Die aufnehmende Operation verpflichtet sich über den Digest auf seinen Klartext; Geschichte trägt es nicht. GlossarWelcome The sealed rltp-welcome/0.1 document that carries the key material of one key state to an admitted person, bound to the group, the person and the accept it answers. The admitting operation commits to its plaintext by digest; it carries no history. Glossary, sent to the new member Membership §3.3 payload-access-operation
membership-evidence/0.2 { evidence }: the enclosed invite and accept, with up to 16 vouches, for any member who can admit Membership §3.4 payload-membership-evidence
membership-evidence/0.1 { evidence }: the same without vouches; accepted, not issued Membership §3.4 payload-membership-evidence-0.1

The Delivery Contract’s own types: the acknowledgement every document earns, a party’s operational constants, and the form in which a carrier of Trust Task documents carries a sealed document.

Type Carries Rules Schema
delivery-ack/0.1 { ref, meaning: "received" }: arrival of one document, never acceptance Delivery §4.2 payload-delivery-ack
registry-declaration/0.1 { declaration }: a party’s signed operational constants for one role Delivery §4.4 payload-registry-declaration
sealed-envelope/0.1 { rkid, epk, nonce, ciphertext }: one sealed document, carried in a Trust Task binding; its parties are the carrier’s identifiers, its id follows from seal and parties, it carries no proof Delivery §4.6 payload-sealed-envelope

https://real-life.org/trust-tasks/spec/delivery-carrier/0.1 names the carrier role in a registry-declaration/0.1. It is not a document type: a document of that type is rejected as unknown.