Fluid's Distributed Data Structures (DDSes) packages live here. Documentation for using them can be found here.
This documentation (below) is for people working on DDS implementations. This document is incomplete and extensions to it are welcome.
When a session ends between summaries, the most recent ops might not be included in the latest summary. These ops are still persisted by the service as "trailing ops". When a DDS is loaded, first the summary is loaded, then the trailing ops are applied. These trailing ops may remain in documents indefinitely, only being removed if a client opens, edits and re-summarizes the document. Fluid typically does not provide a service to update summaries by applying these trailing ops to the DDS. This means DDSes need to support processing all versions of ops that were ever used (in addition to supporting all past summary formats) to ensure all documents continue to be openable.