Glossary: documents and attachments
Terms for documents, Loro updates, blobs, and attachment slots.
Published from docs/glossary/content.md (GitHub)
Part of the glossary.
Attachment Binding
A server-visible signed relationship between a document slot and a blob. Active bindings are the authority for attachment listing, blob reachability, blob read access, replacement, and detach behavior.
Related docs:
Attachment Plane
The protocol plane for encrypted blob staging and signed attachment bind/detach metadata. Attachment metadata stays server-indexable even though blob bytes and document content remain encrypted.
Related docs:
Attachment Slot
An opaque stable identifier inside a document, such as a
product-level “front image” or “back image” slot. The protocol only treats it as
a slotId; at most one active binding may occupy a slot
at a time.
Related docs:
Blob
An encrypted binary object stored separately from document CRDT updates. Blob access is derived from active signed attachment bindings and the linked document/container access graph.
Related docs:
Blob Stage
A temporary holding record for encrypted blob bytes before an attachment bind promotes them to committed blob storage. The server validates byte length, digest, ownership, and expiry, but does not decrypt the bytes. Stages are multipart uploads that the attachment bind assembles and verifies.
Related docs:
Document
An encrypted CRDT object whose plaintext is opaque to the server. Documents do not own direct ACLs. Access is resolved through their signed link-set manifest and the active linked container paths.
Related docs:
Document Plane
The protocol plane for encrypted Loro updates plus visible causal metadata. The server indexes and relays encrypted updates but does not decrypt document content.
Related docs:
Loro Update
An encrypted CRDT update produced by the Loro document layer. The server can see causal metadata such as version-vector spans, but the update payload remains encrypted with the document content key.
Related docs:
Signed Write Header
A signed commitment that binds an encrypted document update or blob record to the object id, access manifest hash, content-key epoch, target hash, metadata hash, ciphertext hash, nonce domain, writer identity, and encryption suite.
Related docs:
Version Vector
Visible causal metadata for Loro sync. Clients submit their local frontier, and the server uses stored update spans to return encrypted updates not covered by that frontier.
Related docs: