Quantself
My personal operating system, with tasks, calendar, habits, inventory and budget in one workspace.
Walkthrough video coming soon
I built Quantself as a personal operating system for deciding what to do next. It brings my tasks, calendar, habits, inventory, budget and job search into one workspace. Tasks live as issues in a private GitHub repository, which stays the source of truth, and the List, Today, Plan, Board and Triage views are all derived from that one model. The calendar shows the same tasks beside a habit lane and a meetings lane. Inventory items can be captured with photos and placed in containers, and proposed details wait for my review. Budgeting keeps receipts separate from expenses and works out cash runway from a checkpoint, my spending and my plan. Jobs review drafts résumés as deterministic PDFs and gives each application its own address.
I designed everyday edits to feel immediate. A task edit updates the screen right away, and Undo and Redo keep working while the save is still queued. Each command has a stable ID and a revision check, so a failed save rolls back only that one change. The web app (Next.js and Chakra UI), the Jarvis voice interface and my integrations all use one typed API built with Bun, Hono, PostgreSQL and Prisma, and the OpenAPI document generates the web client and the API reference. Jarvis is a browser voice interface built on ElevenLabs, and for now it only handles to-dos. Three AI agents work as coworkers outside Quantself, each on its own machine with its own key. They act only on the revision they read, they leave alone anything I touched in the last three minutes, and every write is audited and can be undone.
Quantself is a single-owner application, so I built access control around one person. The dashboard signs in with WebAuthn passkeys today, and I am moving it to Tailscale identity on a private HTTPS origin that only my approved devices can reach. Passkeys stay on the rollback deployment until that cutover is verified. Agents and integrations get named API keys with permissions per area and action, so ordinary writes and permanent deletion are separate grants. Keys can expire, be revoked, or be rotated with an overlap. Visitors to this portfolio can book 30-minute calls through a booking-only key, with a 15-minute buffer enforced around each one.
The app runs as containers. Releases build the exact revision on isolated self-hosted runners instead of the VPS, which protects the server’s memory. Each release checks the candidate before applying migrations, then checks services and HTTP health. I built a storage migration that resumes after an interruption, and I rehearsed restoring the database and the original files together as a pair from encrypted backups, with a nightly restore drill that runs without network access. Moving production to my home server is still in rehearsal, so I treat it as planned rather than done. This portfolio’s analytics are moving into Quantself from Umami, and I read them privately. The repository is private for now while I prepare it for an open-source release, and a feature walkthrough video is coming.