Taxila

Taxila is Phase 4: the first product module, a knowledge base of atomic notes and sources. Scope: notes and knowledge sources you can create, enrich with metadata, link and browse through the command palette. Every later module follows its pattern.

Milestone: The first product module, end-to-end: atomic notes and knowledge sources you can create, enrich with metadata, link, and browse — reached through the command-palette shell. Every future module follows this pattern. Learning payoff: The complete feature loop: PRD → schema → migration → API → repository → UI. Polymorphic content design. Command-palette UX. Prerequisite: Write the Taxila PRD in docs/02-prd/ before starting (new convention).

Phase 4 Exit Criteria: Notes and knowledge sources can be created, enriched with tags/links, edited, listed, and soft-deleted through the command-palette-driven UI. The API layer enforces auth and feature entitlement. All queries filter where(isNull(table.deletedAt)).

RLS template for all feature tables (combined pattern from Phase 1.1; bind the shared trigger functions from migration 0003):

-- RLS (combined pattern)
ALTER TABLE notes ENABLE ROW LEVEL SECURITY;
ALTER TABLE notes FORCE ROW LEVEL SECURITY;
CREATE POLICY "users_own_rows" ON notes FOR ALL
  USING (user_id::text = current_setting('app.current_user_id', true) AND deleted_at IS NULL)
  WITH CHECK (user_id::text = current_setting('app.current_user_id', true));

-- Trigger bindings (functions already exist from migration 0003)
CREATE TRIGGER no_hard_delete_notes
  BEFORE DELETE ON notes FOR EACH ROW EXECUTE FUNCTION enforce_soft_delete();
CREATE TRIGGER no_update_deleted_notes
  BEFORE UPDATE ON notes FOR EACH ROW EXECUTE FUNCTION block_update_on_deleted();