inbuilt-database

Every Doable project includes a built-in PGlite PostgreSQL-compatible database, so no external database is needed. Create tables with the data.migrate tool at build time, then query them from app code by importing db from the pre-linked @doable/data package.

Use the data.migrate tool with a unique migration_id in NNNN_short_name format and CREATE TABLE IF NOT EXISTS statements. Migrations are idempotent, and you should verify the result with data.schema before writing any app code that queries the table.

No, localStorage, sessionStorage, and IndexedDB are forbidden for persisting real user records like tasks or notes. They are only acceptable for trivial ephemeral UI state such as dark mode preference; all real data must go through the inbuilt database.

The @doable/data package is deliberately pre-linked into every project's node_modules by the platform, so it resolves at runtime despite being absent from package.json. Never add it to dependencies or run install_package for it.

The runtime db.query path only accepts SELECT/INSERT/UPDATE/DELETE and rejects CREATE TABLE, so tables must be created via data.migrate first. Also check that RLS policies match the session identity, since rows are auto-scoped to the current user's created_by value.

Yes, add a workspace_id column to your tables and create a second RLS policy that joins through a workspace-membership table. Row-level security is mandatory by default, with per-user owner policies generated from the required table template.