Seeds
Defined data. Compact changes. Shared understanding.
Design Direction
Collections Bound to Definitions
Define the object. Work with its changes. Let the collection layer coordinate replication, event subscriptions, and write consistency.
Identity & Revision
Bind object identity and revision roles to the definition. Keep changes associated with the object they describe, with explicit handling of absent and null fields.
Replay & Subscribe
The intended experience combines a consistent starting state with subsequent changes, handling reconnects and catch-up through the collection layer.
Write With a Contract
Expose clear acknowledgement, retry, conflict, and ordering rules through the collection API. Callers should not have to implement those rules separately for every integration.
What Exists, What Comes Next
Available Today
Collection indexing and object replay provide the foundation for inspecting recorded revisions in Snoot.
Explore Snoot ↗Still to Define
The collection API, live subscription handoff, conflict policy, and consistency guarantees. This is the direction for the framework, not a claim of distributed database guarantees today.