01 / PROBLEM STATEMENT
Why this work exists
Goals, projects, tasks, calendar blocks, habits, focus sessions, and reflection lose context when they live in disconnected tools.
Data and source material
- Owner-scoped life areas, goals, projects, and tasks
- Timezone-aware calendar events and explicit task scheduling
- Habit logs, focus sessions, manual work entries, and planned-versus-actual summaries
02 / SOLUTION OVERVIEW
From input to usable output
A relational model connects life areas, goals, projects, tasks, calendar blocks, habits and recorded work.
- 01
Plan work through linked life areas, goals, projects, and tasks
- 02
Schedule tasks and calendar blocks in Africa/Casablanca wall time
- 03
Record habits and server-authoritative focus sessions
- 04
Review planned-versus-actual summaries
03 / TECHNICAL ARCHITECTURE
Implemented components
Next.js → Drizzle ORM → Neon PostgreSQL with migrations and owner scoping
04 / METHODOLOGY & IMPLEMENTATION
Decisions that shape the system
- Next.js and Drizzle use a reviewed migration workflow over Neon PostgreSQL.
- The data model documents ownership, hierarchy, timestamps, deletion, and history decisions.
- Focus timer state persists in PostgreSQL and survives navigation or refresh.
- Health checks distinguish an unconfigured database, an unreachable database, and a successful query.
Implemented capabilities
- Goal planning
- Calendar
- Habit logging
- Persistent focus sessions
- Planned vs actual
05 / RESULTS & EVIDENCE
What the source supports
- The repository documents foundations through planning, calendar, habit, and focus phases.
- Type checks, lint, tests, builds, migrations, and isolated Neon constraint checks form the quality workflow.
Results preserve the repository’s units, evaluation framing, and stated limitations. Missing evidence is not converted into a claim.
06 / CHALLENGES & LIMITATIONS
Where the evidence stops
- Authentication has not yet replaced the temporary server-only owner boundary.
- The repository explicitly states that the application must not be publicly deployed in its current state.
07 / WHAT THIS DEMONSTRATES
Engineering signal
Relational domain design, durable workflow state, migration discipline, health semantics, and explicit production-readiness gates.
08 / SOURCE & RELATED WORK
Trace the evidence
dc84674a393c059caaed258ff4605473f58e0d20 ↗README.md · docs/data-model.md · db/schema.ts · drizzle/