https://real-life.org/rltp/v1

A collective actor with members, a policy, an authority log, and documents. Its identity is the digest of its genesis operation; its address is its group DID.

A fact in the authority log plus key possession, not a certificate. Entered only by explicit, cryptographically bound consent.

A person's identifier toward one context (did:key). Every enactment of a ceremony runs under a freshly derived pair anchor, a re-encounter too; a standing anchor never appears on the ceremony wire, and anchors never converge into a person.

The relation between two anchors constituted by the encounter credentials between them; incoming, outgoing, or mutual. One edge per anchor pair.

The immutable credential in which one party records that they recognized another. Issued by one party about the other, verifiable offline.

The mode in which a group is readable from outside; publication runs through the publication port (open visibility: world-readable).

One performed run of a ceremony between two people. Never reused; complete when both parties hold records.

An anchor derived for one enactment (DTG scope pairwise). The enacting anchor of a ceremony is a fresh pair anchor at every enactment.

Deliberately without counterpart in RLNP or the Stack: the fresh anchor a person uses for one enactment is pure protocol construction; for the person it is still the one relationship (RLNP Beziehung, mapped at rltp:Edge).

A person's signed self-description carrying the material needed to recognize and reach them and, in an enactment, a fresh challenge; displayed (shown for scanning) or sent (transmitted inside an enactment, naming its recipient). Not a credential.

Deliberately without counterpart in RLNP or the Stack: the card carries what the counterpart needs to reach and recognize an anchor; the Stack shows a profile, which is the view of a person, not a delivery address.

A fresh, single-use, high-entropy value carried in a contact card for one enactment. One concept; displayed and sent cards differ only in lifecycle.

Deliberately without counterpart in RLNP or the Stack: the fresh value each party shows during an enactment is a construction detail of the verification (mapped at rltp:Enactment).

A registered, versioned definition of an encounter interaction, including its time parameters.

Deliberately without counterpart in RLNP or the Stack: the registered form of an enactment (how the two parties see each other's challenges) is a construction detail of the verification (mapped at rltp:Enactment).

One credential issuance within an enactment.

Deliberately without counterpart in RLNP or the Stack: one party's confirmation inside an enactment is a construction detail of the verification; the Stack and RLNP see the whole act.

The digest, identical in both step credentials of an enactment, that ties them to one exchange descriptor: the multihash over JCS of the ceremony and both challenges in ascending order.

Deliberately without counterpart in RLNP or the Stack: the digest that ties the two challenges together is construction, invisible to the person.

A party's durable local record of an enactment, created before issuing; the records are also the consumed-challenge history.

Deliberately without counterpart in RLNP or the Stack: what a party keeps after its own step is local state of the protocol, not a thing in the network.

The multibase-encoded multihash over JCS of the complete credential including its proof.

Deliberately without counterpart in RLNP or the Stack: the content digest of an encounter credential is construction, invisible to the person.

The one-scan transmission (sent card plus step credential), specified as the Delivery Contract task encounter-bundle.

Deliberately without counterpart in RLNP or the Stack: the delivery unit of the one-scan path is construction of the transport, invisible to the person.

An edge, from a party's local view, when it has received the counterparty's credential and not issued its own.

Deliberately without counterpart in RLNP or the Stack: a direction state of rltp:Edge (only the counterpart has confirmed). For the person it is an unfinished verification; the Stack shows it as pending, not as a relationship.

An edge, from a party's local view, when it has issued its own credential and not received the counterparty's.

Deliberately without counterpart in RLNP or the Stack: a direction state of rltp:Edge (only this party has confirmed). For the person it is an unfinished verification; the Stack shows it as pending, not as a relationship.

An edge, from a party's local view, when for at least one enactment it has both issued and received.

Deliberately without counterpart in RLNP or the Stack: the state of rltp:Edge in which both parties have confirmed; this is the state RLNP Beziehung maps to.

The part of the Access Layer that decides membership, policy and authorization: log, materialization, conflict matrix, policy, views. Not replaceable by an adapter.

Deliberately without counterpart in RLNP or the Stack: the part of the Access Layer that decides membership, policy and authorization is internal protocol architecture. The person sees a circle and its members; the Stack sees a space (rltp:Group).

The interface through which a registered adapter produces epoch secrets satisfying the invariants KV1 to KV6.

Deliberately without counterpart in RLNP or the Stack: the interface through which an adapter produces epoch secrets is internal protocol architecture, invisible to the person and below the Stack's connector.

The key port's correction of its key structure to the materialized membership; the log decides, the keys follow.

Deliberately without counterpart in RLNP or the Stack: the key port's correction of its key structure to the materialized membership is internal key management. For the person and the Stack membership simply holds.

The per-group context anchor under which one member acts in one group (DTG scope directed).

Deliberately without counterpart in RLNP or the Stack: the per-group anchor under which a member acts is protocol construction, like every anchor (RLNP Mensch, related at rltp:Anchor). For the person it is still the one member of the circle (rls:member, mapped at rltp:Member).

The anchor of a person's personal community, an ordinary member anchor of Identity §6, serving as the person's chosen cross-relationship coordinate; it appears in no artifact of the Access Layer except inside member-mapping@1.

Deliberately without counterpart in RLNP or the Stack: an ordinary member anchor that a person uses as a chosen cross-relationship coordinate is protocol construction, like every anchor (RLNP Mensch, related at rltp:Anchor). The Stack shows a profile, which is the view of a person, not an anchor.

The signed binding of one device's key material to the member anchor of the person it belongs to; recorded in the authority log.

Deliberately without counterpart in RLNP or the Stack: the signed binding of a device's key material to a member anchor is protocol construction. Neither RLNP nor the Stack distinguish a person's devices.

A party that stores and forwards a group's items without holding its keys; its class (blind, view, log) is the registered statement of what it knows of the group.

Deliberately without counterpart in RLNP or the Stack: a party that stores and forwards a group's items without holding its keys is protocol infrastructure. The network knows only people and circles; the Stack's connector is the app-side access to a backend, not a party the group registers.

The statement, declared at registration, of what a service knows of a group: blind (ciphertext only), view (also authorization views) or log (also the authority log). The group chooses.

Deliberately without counterpart in RLNP or the Stack: what a service knows of a group (blind, view, log) is a registered protocol statement about rltp:Service, invisible to the person and the Stack.

The append-only operation DAG rooted in the genesis operation; the sole source of authorization state.

Deliberately without counterpart in RLNP or the Stack: the append-only operation DAG that is the sole source of authorization state is protocol construction. The person sees who belongs to the circle; the Stack sees the members of a space.

A signed, causally anchored envelope.

Deliberately without counterpart in RLNP or the Stack: a signed, causally anchored envelope in the authority log is protocol construction, invisible to the person and the Stack.

The deterministic derivation of group state from the log; its result is the materialized state.

Deliberately without counterpart in RLNP or the Stack: the deterministic derivation of group state from the log is protocol construction. The person and the Stack see only its result: the circle or space with its members.

An operation is canonical when materialization at its causal position accepts it and no outcome rule of 3.6 disposes of it.

Deliberately without counterpart in RLNP or the Stack: whether materialization accepts an operation at its causal position is a property inside the protocol's conflict resolution, invisible to the person and the Stack.

The set of parties holding, and entitled to hold, the group's replicated log at a given materialized state.

Deliberately without counterpart in RLNP or the Stack: the set of parties entitled to hold the group's replicated log is protocol construction. RLNP Sichtbarkeit is about what a person shows to whom, not about who stores the log.

The group state yielded by materialization, the deterministic derivation of group state from the log.

Deliberately without counterpart in RLNP or the Stack: the group state yielded by materialization is protocol construction; the person sees the circle, the Stack the space (rltp:Group), not a derived state.

The fail-closed materialization outcome of the fork pairings that 3.6 names: a policy change or a dissolution concurrent with an enforcement operation.

Deliberately without counterpart in RLNP or the Stack: a fail-closed outcome of materialization and a narrower case of rltp:MaterializedState, arising when a policy change or dissolution runs concurrent with an enforcement operation. It is conflict handling inside the protocol, invisible to the person and the Stack.

The normatively computed set of members an enforcement operation’s new epoch secret reaches.

Deliberately without counterpart in RLNP or the Stack: the computed set of members an enforcement operation's new epoch secret reaches is key-management construction. For the person and the Stack the circle simply keeps its members (rls:member, mapped at rltp:Member).

The state of a member whose member.leave has merged but whose discharging transition has not.

Deliberately without counterpart in RLNP or the Stack: the state between a merged member.leave and its discharging transition is protocol construction. For the person leaving a circle is one act; the Stack has no intermediate state for it.

Group-defined data stating, per rule key, which proof satisfies the group’s decision rule.

Deliberately without counterpart in RLNP or the Stack: group-defined data stating which proof satisfies the group's decision rule is protocol construction. RLNP lets a circle choose its own form and decisions without encoding them as rules; the Stack has no policy object.

The material an operation is judged by against its rule: its signer set and its admissible vouch set.

Deliberately without counterpart in RLNP or the Stack: the signer set and vouch set an operation is judged by is construction of rltp:Policy, invisible to the person and the Stack.

The standing obligation of members to (re)deliver verifiable current-epoch key material to a party the materialized state entitles to it.

Deliberately without counterpart in RLNP or the Stack: the members' standing obligation to (re)deliver current-epoch key material is a duty inside the protocol's key management. For the person and the Stack entitled members simply can read.

A numbered period of the group’s key world; enforcement takes effect as epoch transitions. Term aligned with MLS (RFC 9420).

Deliberately without counterpart in RLNP or the Stack: a numbered period of the group's key world, aligned with MLS, is key-management construction. Neither RLNP nor the Stack divide a circle or space into key periods.

The chain of per-transition entries by which the adapter linear/0.1 makes a previous content key readable under the next.

Deliberately without counterpart in RLNP or the Stack: the chain of per-transition entries by which the adapter linear/0.1 keeps earlier content keys readable is construction of one adapter (rltp:Adapter), invisible to the person and the Stack.

The chained, quorum-signed object by which a service of class view learns a group’s epoch and authorized device identities.

Deliberately without counterpart in RLNP or the Stack: the quorum-signed object by which a service of class view learns a group's epoch and authorized devices is protocol infrastructure (rltp:Service), invisible to the person and the Stack.

An operation of the closed catalog, each with its class (additive, enforcement, terminal), epoch effect and closed body profile.

Deliberately without counterpart in RLNP or the Stack: an operation of the closed catalog and a narrower case of rltp:Operation, each with its class, epoch effect and body profile. Admitting or removing a member is one act for the person and the Stack; the operation is its construction.

The read/write standing every member holds by membership alone.

Deliberately without counterpart in RLNP or the Stack: the read/write standing every member holds by membership alone is how the protocol states that belonging is enough. The Stack expresses it through membership itself (rls:member, mapped at rltp:Member); RLNP knows no membership list to attach it to.

A registered binding of one key-agreement procedure to the key port.

Deliberately without counterpart in RLNP or the Stack: a registered binding of a key-agreement procedure to the key port is internal protocol architecture, invisible to the person. The Stack's backend binding is the connector, which is pure Stack construction and unrelated.

Proposed: a signed, portable statement by one person about another's contribution, role, skill or promise, independently verifiable. Candidate: the DTG Verifiable Endorsement Credential (VEC), i.e. a Statement Credential with predicate endorses/1.

the multibase multihash over JCS(document) of a delivery document's plaintext; its identity for idempotency and acknowledgement

the encrypted form in which a document travels: ephemeral X25519, HKDF, AES-256-GCM

the receiver's classification of a processed envelope (staged, first failing stage names it)

the arrival acknowledgement: machine-generated at the durable recording of a document's defined effect; arrival, never acceptance