π Adapter-First Architecture Every subsystem is a pluggable adapter. Compose your database from the exact components you need. Runtime swappable with zero recompilation.
βοΈ Equivalent Nodes Browser and server are peers implementing identical traits. Same CRDT engine, same storage interface, just different adapter implementations.
π― Path-Level Policies Per-path control over storage, sync, and auth. Different data, different rules. Configure at runtime without rebuilding.
π§© Shared Implementations Pure Rust core with unified traits. Browser WASM and native servers share the same CRDT logic, differ only in platform adapters.
π CRDT-Based Sync Built on Automerge for conflict-free replicated data. Multi-user by default, with incremental delta sync and merge semantics.