Products that capture what you do and hand back the time admin takes
Personal Assistant, DayScribe and Cockpit are products — offline-first, local-first systems built and used daily, presented here with the same honest labels as everything else on this site.
The problem
Professionals and founders working across many projects at once lose notes, ideas and time to scattered apps with no purpose-built way to capture, search and act on them without a constant network connection.
What the portfolio proves
Local-first and offline-first product engineering: capture pipelines, offline full-text search and link graphs, installable PWAs with device sync, scheduled automation, and privacy-preserving summarisation designed in from the start.
How the projects fit together
Personal Assistant (In use) is one product across two carded projects. It captures notes and files into an inbox and promotes reviewed material into a knowledge base. Its reading, search and graph layer — named "Personal Assistant — reading layer" (In use) — renders that knowledge base as a fast, offline, installable site with its own search index (44 passing checks). DayScribe (In use) is likewise one product, in two editions: a whole-day life-logging app against a personal values taxonomy. The second edition, named inside the same entry — "DayScribe — local-first edition" (In use) — syncs across a person's own devices with no network required. Cockpit (In use) is a founder's task-dispatch and status dashboard across local projects, presented here as a product of this vertical with its own honest label. Triage (In design) and Guruji (In design) are two further designs: a privacy-scrubbing personal-inbox digest, and a curriculum-aware AI tutor — both specified in writing, neither built yet. Content Creator (In use) and FilmyGyan (Prototype) sit here as secondary evidence of the same knowledge-engineering discipline, already introduced under Video, Media and Content AI.
What I can do here
This vertical is the clearest evidence for a buyer asking how this practice actually builds: local-first architecture, offline search, and privacy-preserving design applied consistently across several products.
How mature this is
Presented as products with honest labels, on exactly the same terms as every other entry on this site. The two In design entries are written as designs, not software. Every screen here can hold personal data, so no real screenshot ships without a redaction check — a placeholder is the default.
Mapped projects
Cockpit
In use
Running today and in regular use; it is not an open public service you can sign up for.
A task-dispatch and status dashboard across local project repositories.
Coordinating work across many local project repositories and tracking AI-assisted development hours otherwise needs manual bookkeeping.
Assigns tasks to local project repositories, drains them into each repository's own task list, and reports project status and AI coding-session hours from one dashboard.
The dispatch loop is built as a request/response contract across projects (assign, pick, fan-out, release), designed to run without a central always-on service holding state.
Python (standard library) behind a single-page HTML/JS UI
scheduled background jobs
No public artefact yet.
Content Creator
In use
Running today and in regular use; it is not an open public service you can sign up for.
Turns one idea into publish-ready content packages for ten platforms, with a human approval gate.
Producing consistent, on-brand content across many social platforms from a single idea is slow and error-prone.
A git-versioned pipeline that carries an idea through qualification, scripting and drafting, then packages it per platform (YouTube, Shorts, Instagram, TikTok, X, LinkedIn and more), gated by human review before anything ships.
Ten platform adapters, each with its own spec and prompt.
The human-approval gate sits before anything ships, not after, so nothing is published automatically.
Python
Claude Code skills and a platform-writer subagent
optional local media tooling
DayScribe
In use
Running today and in regular use; it is not an open public service you can sign up for.
An offline-first life-logging app that tracks all 24 hours of the day against a personal values tree, in a hosted-ready edition and a local-first edition.
People who want to understand how their time actually aligns with what they value lack a low-friction, always-available way to log it.
Logs whole-day time against a category tree, tracks habits and counts, and keeps notes, tasks and a journal. It syncs across a person's own devices with full offline support. The local-first edition does the same over the local network, with no hosted backend required.
The two editions are a real engineering claim about offline-first design, not a restatement: one runs hosted behind an API, the other runs local-only with network sync, from the same taxonomy and interface.
vanilla JavaScript PWA (hosted edition) with a Python API and Postgres
vanilla JavaScript PWA (local-first edition) with a lightweight local sync gateway
No public artefact yet.
DayScribe — local-first editionIn use
FilmyGyan
Prototype
The core works end to end and can be demonstrated; it is not production-hardened or generally available.
Turns Indian-cinema dialogue into a searchable, always-attributed knowledge base and persona chat.
Finding "the scene where a character says the thing that fits this situation" is otherwise a manual, memory-dependent search through films.
Ingests film captions into a tagged dialogue knowledge base, powers situation-based search, and runs a persona chat that always attributes its quotes back to the source film.
The always-attribute-the-source behaviour is the point, given the dialogue is third-party copyrighted material.
The production tier caps quote length rather than storing full text, so the site describes the search and attribution capability and reproduces no quoted dialogue.
Python
SQLite
TF-IDF retrieval
optional AI-assisted tagging
Guruji
In design
Designed and specified in writing; no working software exists yet.
A plan for a personal AI tutor that keeps pace with what a student's own school is actually teaching that week. It combines a daily practice loop, spaced repetition and a Socratic tutor chat that never gives away answers on assessed items. It is a design only, with no working software behind it.
Personal Assistant
In use
Running today and in regular use; it is not an open public service you can sign up for.
A personal capture-to-knowledge pipeline, plus the reading layer that makes the result searchable.
Notes, ideas and progress captured throughout the day get lost between different apps and never make it into a durable, organised knowledge base.
Captures notes and files from multiple sources into one inbox, automatically drains them into a daily journal, and promotes reviewed material into a knowledge base. The reading layer then renders that knowledge base as a browsable, installable site with offline full-text search, backlinks and a link graph.
The reading layer builds the whole knowledge base into a static site with its own search index and link graph, backed by 44 automated checks. That offline index and the installable PWA around it are its own engineering, not a wrapper over a hosted search service.
Python (standard library) with scheduled automation and a knowledge-base vault for the capture side
Astro static-site generation with an offline search index for the reading layer
Personal Assistant — reading layerIn use
Triage
In design
Designed and specified in writing; no working software exists yet.
A planned digest that turns a personal inbox and phone notifications into short, privacy-scrubbed summaries. Sensitive details such as one-time codes and card numbers are removed before a digest is produced. Every module is a stub today, so nothing runs yet.
