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

The shared context for work, membership and visibility. In the data contract it is called Group.

A read-only snapshot of an item in a space other than its home. There it appears as an ordinary item with the relation mirrorOf pointing at the original; editing always opens the home. The same form holds for every connector: with a signing identity (RLTP) the snapshots are author-signed and verified before they are shown, without one they come without a JWS from a single trust domain.

A directed link between items with predicate and target. Back-references show it from the opposite direction.

The domain representation of a person as an item under the profile contract. The user identity is a separate term.

The implementation of the DataInterface for one data source, plus the capabilities it supports. The stack's socket downward.

Deliberately without counterpart in RLNP and RLTP. The connector is pure Stack construction.

Proposed: who belongs to a space. The application layer reads membership through the connector and does not construct it; how it is stored and proven is decided by the connector in use (the local connector keeps it in groupMembers, the RLTP connector derives it from the group log and key).

Proposed: where an item lives and who therefore sees it: within its space, mirrored into another space, or published without sign-in. Which backend serves a published item is the connector's decision.

The flow in which two people record an encounter in the app, for example by QR code; a capability of the connector in its own right. Contacts and verifications are not the same as profiles.

Proposed: an item lies in more than one space and has a home space responsible for it. How this is done, by association in a central database or by copy with a bridge across distributed groups, is the connector's decision.