Chronos is a live, single-owner system for recording deliberate time investment across long-running skills while publishing only a production-safe view of selected lifetime totals.
Stack, status, evidence, and public actions are rendered from the typed project record.
Category
Product System
Type
App
Priority
Strong
Overview
What this project is
Chronos is a live, single-owner system for recording deliberate time investment across long-running skills while publishing only a production-safe view of selected lifetime totals.
Problem
Why it matters
Most timers explain a day but lose the long horizon, while publishing raw activity would expose more personal context than a public portfolio needs.
Solution
Approach
A server-led ledger that preserves durable skill totals and session decisions privately, then exposes a narrow public projection for proof of consistent investment.
Architecture
System shape and stack
Product Model
Time as durable investment
Chronos tracks lifetime allocation across skills instead of resetting the story every day. Stopped sessions remain pending until they are intentionally counted or skipped.
Trust Boundary
Public evidence, private operations
Anonymous visitors receive a filtered dashboard projection. Owner routes, raw sessions, private skills, downtime, and all mutations remain behind Supabase Auth, an allowlist, RLS, and schema-scoped functions.
Reliability
Invariants below the interface
Database constraints prevent overlapping active timers, server actions coordinate mutations, and unavailable production data renders an explicit notice instead of convincing sample totals.
Evidence
Honest about measurement strength
Structured timer sessions provide the strongest audit trail. Earlier historical baselines remain visibly disclosed as estimates rather than being presented as second-by-second observation.
- TypeScript
- Next.js App Router
- React
- Supabase Auth
- Supabase Postgres
- Vitest
- Vercel
Technical Highlights
Visible technical signal
- Real public totals with no fabricated fallback data
- Owner-only timer, session, and skill operations enforced through RLS and database RPCs
- One-active-timer invariant, count-or-skip confirmation, and automatic downtime tracking
What It Proves
Builder signal
Full-stack product ownership across an actively used interface, transactional timer logic, authentication, PostgreSQL authorization, data provenance, testing, and production operations.
Boundaries
Context that should stay visible
Chronos is intentionally single-owner. Lifetime totals may include disclosed historical estimates from before structured session tracking.