MyPaddie is a private life-coaching system: a rules engine (XP, modes, money
stages) on Supabase Postgres with RLS, an MCP connector, and a Next.js PWA.
Blueprint: ~/code/personal/mypaddie/docs/BLUEPRINT.md. Decisions:
~/code/personal/mypaddie/DECISIONS.md.
Read in order:
- 01-supabase-schema-and-rls — owning rows, composite FKs, deferred constraint triggers, ledgers, the 2026 grants change
- 02-rules-engine-design — pure functions, injecting
now, largest remainder, the rolling-window bug - 03-testing —
bun test, testing time, table tests, pgTAP for RLS - 04-shell — slow networks,
--prefer-offline,timeoutexit codes, zsh vs bashPIPESTATUS; re-creating SQL functions withawk+sed+diff <(…), proving a test can fail - 05-mcp-server — the remote MCP server: auth, per-user context,
ok/toolError, and tool-design lessons from real bugs - 06-scheduling-and-push —
pg_cronevery minute, the database decides and the app delivers, unique indexes as memory, holds - 07-time — local days, the 23:59 “any time” sentinel, quiet hours as the day’s end, “later”, Sunday vs Monday weeks
- 08-data-modelling-choices —
started_atover a new status, derive vs store, jsonb vs table, defaulted flags, two limits - 09-nextjs-app — feature folders, server components read, server actions write, small client islands
See also (general vault): tools and MCP · sed and awk · sql-reference · 02-authorization ·
gees-arise (the previous Supabase + RLS project) ·
linux
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering