Skip to content

About

A calm, personal, desktop-first workday planner.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

North Haven

North Haven is a calm, personal, desktop-first workday planner. It separates a large work inventory from the small, deliberate plan that deserves attention today.

Open North Haven and know what to do next in less than ten seconds.

The interface is English. Product documentation and collaboration may be in Spanish.

Current phase

The core Work Inventory, Daily Planning, End of Day, and read-only Google Calendar application layers are implemented. The repository contains real persisted Today and Plan data, Supabase authentication, private workspace provisioning, Tickets, Tasks, Reminders, meetings, official OOO handling, and protected Google OAuth routes.

The live corporate OAuth feasibility check and refresh-token exchange passed on August 1, 2026. Phase 7 now includes shared reporting projections, retrospective Calendar and Day Summary, monthly notes, Week/Month/Quarter/Custom Insights, accessible trend summaries, and the Daily/Weekly/Monthly Report Builder with designed PDF and data CSV exports. Phase 7.5 product completion is now in progress: Profile, Work schedule, manual non-working days, password changes, session revocation, Calendar connection, and Ticket types are functional in Settings. Phase 7.5B adds versioned workspace backup/restoration, closed-day reopening, and visible archived-work recovery. Phase 7.5C now completes Plan navigation and filters, operational Work Inventory actions, richer Work Detail, embedded next-day planning in End of Day, and private Global Search. Phase 7.5D authenticated coverage is in progress: CI provisions a clean Supabase stack and exercises RLS plus the full browser acceptance path, including PDF/CSV downloads and test-data cleanup. The same path will next run against hosted Supabase and Vercel before Phase 8 hardening. No customer data, production credentials, or Google tokens are committed.

Local setup

Requirements:

  • Node.js 24.15.0, recorded in .nvmrc; Vercel deploys the latest compatible Node.js 24 patch
  • npm
  • Docker-compatible runtime only when starting the local Supabase stack

Install and run the interface:

nvm use
npm install
npm run dev

Open http://127.0.0.1:3000. The root route sends signed-out visitors to Sign in and authenticated users to Setup or Today.

Copy .env.example to .env.local and replace the placeholders with local or hosted project values. Never commit .env.local.

For the live Google Calendar check, configure a Google Cloud Web application OAuth client with this exact local redirect URI:

http://127.0.0.1:3000/api/google-calendar/callback

The ignored local environment then needs the client ID, client secret, a local Supabase service-role key, and a base64-encoded 32-byte token-encryption key. Generate the encryption key with openssl rand -base64 32. Keep every value server-only.

Run the local database and reproduce its schema with:

npm run db:start
npm run db:reset
npm run db:types

db:types regenerates the checked-in TypeScript database contract after a schema migration changes.

Settings and recovery are documented in docs/20-settings-implementation.md and docs/21-recovery-and-lifecycle-implementation.md. Product-completion parity is documented in docs/22-operational-parity-implementation.md. Hosted Supabase and Vercel setup is documented in docs/23-hosted-environment-implementation.md.

With the local stack running, the opt-in database and browser authentication checks are:

npm run test:integration:local
npm run test:e2e:local

Verification commands

npm run format
npm run lint
npm run typecheck
npm test
npm run build
npm run test:e2e
npm audit

Playwright needs its Chromium binary once per machine:

npx playwright install chromium

Project structure

src/
  app/                    Routes and layouts
  features/               Domain-owned UI, rules, and tests
  server/                 Server-only auth and database boundaries
  shared/                 Reusable UI, content, and validation
supabase/
  migrations/             Reviewed SQL migrations and RLS policies
  seed.sql                 Synthetic local data only
tests/e2e/                 Browser-level workflows
docs/                     Canonical product and technical specifications
design/                   Approved wireframes and high-fidelity references

Security baseline

  • Supabase SSR sessions will use cookies and PKCE.
  • Every exposed business table requires RLS.
  • Service-role and Google secrets stay server-only.
  • Customer content must never appear in URLs, logs, analytics, or errors.
  • Generated report files are streamed with private/no-store behavior and are never retained by North Haven.
  • The initial dependency audit passes with zero known vulnerabilities.

Supabase JavaScript is pinned to 2.109.0 with SSR 0.12.0 while its next runtime-sensitive upgrade is validated separately. The project already uses Node.js 24 across local development, CI, and Vercel. PostCSS and Sharp use security-fixed overrides.

Documentation

About

A calm, personal, desktop-first workday planner.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages