@feltdb/core 0.8.7 → 0.9.0

package/dist/create/server-source/crates/feltdb/src/state_model.rs

@@ -1089,9 +1089,22 @@ pub fn reconcile(
 /// Proven for this type: durable single-writer append, retrieval by identity
 /// across restart, ancestry by parent traversal, and independence between
 /// records. **Not** proven and not claimed: multi-writer persistence semantics,
-/// concurrent revision creation, authorization, resource isolation, garbage
-/// collection, server lifecycle integration, current/head semantics, and
+/// concurrent revision creation, resource isolation, garbage collection, and
 /// distributed replication of revision history.
+///
+/// Two entries left that list when `/v1/state/*` began serving this type.
+/// *Server lifecycle integration*: `feltdb-server` opens a store over its own
+/// `FeltDb` through [`crate::FeltDBStateSystem`] and serves history, diff,
+/// classification and reconciliation from it. *Authorization*: those routes are
+/// authorized like every other route — `state:read` to read, `state:write` to
+/// commit — which is authorization **at the route**, not in this type. This
+/// type still has none of its own, and a caller holding a `StateStore` still
+/// reaches every resource in it.
+///
+/// *Current/head semantics* also left, but only partly, and the distinction
+/// matters: [`head_of`](Self::head_of) answers "the newest retained revision of
+/// this resource, by sequence". That is not a branch head and there is still no
+/// ref anything can move.
 pub struct StateStore {
     backing: Backing,
 }