Open design documents for MorphDB — the gaps worth closing and the systems worth building. Read them, and comment on any section right inline.
▸ For contributors: each section has a comment thread. Pick something, weigh in, or claim it to implement. Comments are public and stored in the cloud MorphDB app morphdb-spec-comments — MorphDB hosting its own discussion.
What the generic MorphDB backend can't do yet — 13 limitations found while building the LinkedIn / Notion / Figma / Linear clones, plus a full map of what a production rebuild would categorically require. This is the prioritized to-do list.
A design for per-end-user permissions enforced inside MorphDB: a two-tier key split, real end-users with stdlib auth, and a rule model where the rule is the index-backed WHERE clause — portable across SQLite and Postgres. Closes gap #8.
Streaming for MorphDB: GET /stream/{type} over Server-Sent Events, taking the same query grammar as the list endpoint — pushed as whole fresh results (snapshot) or per-object enter/update/leave deltas. A survey of how Supabase, Firestore, RethinkDB, Hasura, Convex & Meteor do it, and the performance walls a generic subscription interface must bound. Closes gap #5; lights up watch() with zero app-code change.
A Firebase-style client SDK served by the backend itself at GET /sdk.js — one zero-dependency script, host inferred from the script tag, typed errors, polling-based watch() live queries, and a browser-side init for the portable schema file. Retires the copy-pasted db() helper.