Work log: Scholexis — March 11, 2026

What shipped today

The Next.js port foundation is now complete. Four issues shipped in a single session, taking Scholexis from an empty monorepo structure to a fully scaffolded three-tier application with a complete database schema.

Application scaffolding. Built the Next.js 16 web app (#66) with App Router, Tailwind v4, shadcn/ui v4, and Drizzle ORM. The Scholexis brand color system is wired into the CSS custom properties — primary blue, dark navy secondary, amber accent, full dark mode palette. Alongside that, the Python FastAPI engine (#67) is set up with health check endpoint, Pydantic settings, and the dependency stack (anthropic, asyncpg, apscheduler). Both services run via Procfile.dev.

Database schema. Ported the entire Rails schema to Drizzle across two issues. Core tables (#70) covered users, academic_years, terms, weeks, instructors, courses, meetings, and meeting_patterns — the structural backbone. Feature tables (#71) added assignments, tasks, events, energy_check_ins, ai_task_breakdowns, access_grants, app_preferences, and attachments. The tricky bit was the circular FK between assignments and ai_task_breakdowns — handled by defining one direction in Drizzle’s references() and the other as raw SQL in the migration. All 16 tables are live in local PostgreSQL with correct constraints and indexes.

Pipeline housekeeping. Decomposed the parent issues (#49, #50, #51, #60) into grindable children, prepped specs, triaged the queue. Unblocked #61 (database seeding) now that schema work is complete.

Completed

• #66 — Scaffold Next.js web app with Drizzle and shadcn/ui
• #67 — Scaffold Python FastAPI engine
• #70 — Define Drizzle schema for core tables (users, academic structure)
• #71 — Define Drizzle schema for feature tables (assignments, tasks, events, energy)
• #50 — Scaffold Next.js app from next-saas-starter template (decomposed → #66, #67)
• #51 — Set up Supabase project and port database schema (decomposed → #70, #71)
• #49 — Port from Rails to Next.js (decomposed → #50-#59)
• #60 — Port access grants, admin panel, and deploy (decomposed → #62-#65)

Release progress

• Next.js port: 8/21 closed (13 open). Foundation layer complete — scaffold, engine, full schema. Moving into feature implementation.

Carry-over

• #61 (database seeding) just unblocked — needs prep and exec
• #52 (auth system) is the critical path blocker for all feature work — needs decompose
• #53-#59 all need decompose before any can be prepped/executed
• #62-#65 (admin panel children) remain blocked on auth + schema seeding

Risks

• No .env file was tracked — DATABASE_URL was appended to apps/web/.env locally but it’s gitignored. New clones will need to set this up manually.
• Port 3000 conflict between Rails dev server and Next.js — Next.js auto-selects 3001 but this will need cleanup when Rails is decommissioned.

Flags and watch-outs

• shadcn/ui v4 deprecated the toast component — use sonner instead
• Python 3.14’s setuptools uses "setuptools.build_meta" as the build backend string (not the _legacy variant)
• Drizzle’s decimal type maps to PostgreSQL numeric — pass precision/scale explicitly

Next session

1. Decompose #52 (auth system) — this is the critical path. Everything downstream (features, admin, deployment) depends on auth.
2. Prep and exec #61 (database seeding) — now unblocked, quick win to get dev data flowing.
3. Decompose #53 (design system port) — parallel track to auth, can unblock UI work.
4. Decompose #54 (dashboard/navigation) — sets up the app shell for all feature pages.