Ramose — an immutable, Datomic-inspired graph database for Cloudflare (Workers + Durable Objects + R2), built on Effect. One package: the schema and client (`ramose/db`), the Alchemy resources (`ramose`), the peer Worker (`ramose/worker`), the React hooks

Alchemy 2 + Effect interface for Ramose: the portable `@ramose/alchemy/db` entry, the Ramose.Server and Ramose.Database resources, the ReadWriteDatabases / ReadDatabases capabilities and the ServerBinding / ServerHttp transports.

Ramose core engine: datoms, segments, segment trees, novelty, datalog. Pure TypeScript, no Cloudflare dependencies.

Ramose storage adapters for Cloudflare: R2-backed content-addressed node store (memory → Cache API / SQLite → R2), root records, log chunks.

Ramose Transactor Durable Object: single writer per database, group commit, novelty WebSocket hub, alarm-driven incremental indexer + GC.

Ramose QueryReplica Durable Object: long-lived novelty subscriber (WS to the Transactor), hot-segment cache, basis/novelty endpoint for Workers.

Better Auth plugins for Ramose: `ramoseToken` adds the mint route that signs the workspace-scoped JWT a Ramose peer verifies (same JWKS as the jwt plugin), and `ramoseTokenClient` pairs it with `Ramose.token.jwt` in the browser.

Ramose peer Worker: HTTP API (/transact /query /pull /db-info), datalog at the edge over cached segments + replica novelty; exports the DO classes.

React bindings for Ramose: RamoseProvider owns one Client per subtree, useRamose hands it back, useDb memoises a Db from it. Hooks only — no UI, no styling.