alkstore

The core crate of the alkstore family: the contract artifact — the unified Store trait surface, value types, error taxonomy, and the naming / reserved-namespace contract of the reactive store substrate. It has no driver dependencies, ever (payload encoding's serde/serde_json are its only dependencies); engine crates depend on it and implement its traits.

Downstream consumers depend on alkstore plus exactly one engine crate: alkstore-sqlite, alkstore-postgres, or alkstore-mem. Engine identity is compile-time — the engine crate your binary depends on is the deployment statement; there is no runtime capability surface.

See the family README for the interface, the engine postures, and the deployment matrix; the crate's own docs are part of the contract.