Skip to main content
Personal Tool Open Source Pre-production / v0.1.10 Client-only

Kieran's LifeTrkr

Rituals. Habits. Today. A little bit of magic.

A quiet, mobile-first life OS built for Kieran. LifeTrkr brings routines, habits, local tasks, calendar events, and a daily oracle into one low-noise interface. It keeps personal records in the browser, treats Google Calendar and Google Tasks as read-only sources, and leaves the day in the user's hands.

One day, too many places to look

Routines get scattered

Recurring work should be visible in the rhythm of the day, not buried in separate notes and reminders.

Small progress needs a home

Habits are easier to return to when completion is light, local, and visible without turning life into a dashboard.

Today is not the same as someday

Committed tasks and deferred ideas need different places, so the backlog does not compete with the present.

Reflection belongs beside action

A daily oracle adds a moment of meaning without pretending to schedule, diagnose, or decide the user's life.

Live App · okhp3.github.io

External app: LifeTrkr is served from GitHub Pages, outside this site's trust boundary. Open it full screen for the intended mobile experience.

A quiet answer to “What does today require?”

Home

See today's ritual, upcoming events, celestial context, habits, tasks, and the daily oracle in one morning-glance view.

Rituals and habits

Track day-based routines and repeating habits with local completion history, categories, tags, and gentle streaks.

Calendar and Today

Keep manual events and committed local tasks close, with optional read-only Google Calendar and Google Tasks views.

Someday and the oracle

Move uncommitted work out of today's line of sight, then make room for a cached daily card, moon, season, and optional oracle message.

Personal by design

Browser-owned records

Local routines, habits, tasks, and manual events stay in namespaced browser storage. The publisher does not own a copy.

Read, do not write

Google Calendar and Google Tasks are optional read-only sources. LifeTrkr does not modify the user's Google data.

Fallbacks are part of the product

The daily oracle remains useful when the worker, tarot endpoint, horoscope endpoint, or network is unavailable.

Low noise wins

The interface is designed as a calm nighttime companion, not a productivity contest or a public social feed.

An infrastructure for the next generation

LifeTrkr began as a father-to-daughter project for Kieran, also named Rylee Hill in the generational story of the Hill. The intention is not to hand down pressure or a work ethic alone, but to leave behind a useful piece of infrastructure: a tool that helps a person notice the day, keep promises to herself, and make room for what matters.

The wider family context is documented in The Manifesto's generational origin section, which names Rylee Hill as the next generation and frames the inheritance as infrastructure rather than pressure.

The application itself remains deliberately modest: client-only, browser-owned, open source, and still honestly marked pre-production while its external integrations and handoff gates are verified.

A life OS. Not a life manager.

This project is not:

  • --a multi-tenant productivity service
  • --a replacement for Google Calendar or Google Tasks
  • --a social feed, accountability system, or public profile
  • --a medical, therapeutic, or spiritual authority
  • --a backend that stores the user's life

It is a small, personal interface for noticing what today requires and choosing what to do with it.