https://real-life.org/rltp/v1The vocabulary namespace of the Real Life Trust Protocol. Permanent term identifiers are https://real-life.org/rltp/v1#<Fragment>; the fragments resolve to the table below.
The JSON-LD context document is context.jsonld. Per the interim securing profile, credentials pin their @context by value and implementations never process JSON-LD at runtime — this document defines meaning, not machinery.
Machine-readable registry: index.json — all terms with IRI and definition, plus context and schema URLs with SHA-256 digests.
| Fragment | Meaning | Defined in |
|---|---|---|
#Anchor | the stable Layer-1 identifier of a person (in the interim profile: a did:key) | Encounter 2.2 |
#ContactCard | a person's signed self-description: verification material, key-agreement key, challenge when used in an enactment | Encounter 6 |
#Challenge | a fresh, single-use, high-entropy value carried in a contact card for one enactment; governed by the own-challenge state model | Encounter 5.3 |
#Ceremony | a registered, versioned definition of an encounter interaction, including its time parameters | Encounter 5.1 |
#Enactment | one performed run of a ceremony between two people; never reused | Encounter 5.2 |
#Step | one credential issuance within an enactment | Encounter 5.2 |
#EnactmentBinding | the digest, identical in both step credentials, tying them to one exchange descriptor | Encounter 5.4 |
#EncounterCredential | the immutable credential in which one party records that they recognized another | Encounter 7 |
#CredentialDigest | the multibase multihash over JCS(document) of the complete credential including its proof | Encounter 2.2 |
#Edge | the relation between two anchors constituted by the encounter credentials between them: incoming, outgoing, or mutual; one edge per anchor pair | Encounter 4.2 |
#DocumentDigest | the multibase multihash over JCS(document) of a delivery document's plaintext; its identity for idempotency and acknowledgement | Delivery 2 |
#SealedEnvelope | the encrypted form in which a document travels: ephemeral X25519, HKDF, AES-256-GCM | Delivery 5 |
#Disposition | the receiver's classification of a processed envelope (staged, first failing stage names it) | Delivery 6.2 |
#DeliveryAck | the arrival acknowledgement: machine-generated at the durable recording of a document's defined effect; arrival, never acceptance | Delivery 4.2 |
access-material · access-operation-envelope · access-registration · authorization-view · contact-card · encounter-credential · rltp-delivery-document · sealed-envelope · welcome
Task payload schemas live at their Type URIs under /trust-tasks/.