Vritto

Vritto is a Life Operating System: a single, structured workspace for every part of life that normally lives scattered across five to fifteen apps.

The thesis is simple. People do not think in documents or databases. They think in categories of life. My subscriptions. My health. My deadlines. My finances. Every category deserves its own dedicated module with a defined schema, not a blank page that the user has to design from scratch.

Why This Project Exists

The tools people use to manage their lives fall into two categories, and both have the same failure mode.

On one side are rigid single-purpose apps. Todoist for tasks. Google Calendar for time. A niche tracker for subscriptions. A spreadsheet for warranties. Each one is clean at what it does and useless outside of that. A typical user ends up with five to fifteen of them, none aware of the others.

On the other side are flexible-but-generic platforms like Notion and Obsidian. The blank-canvas design means users spend hours building systems instead of using them. A subscription, a doctor's appointment, and a journal entry all resolve to the same generic "page." Nothing is structured, which means nothing can be automated, and AI cannot reason cleanly across it.

The result is the same in both cases. Life data is fragmented, unstructured, and silently duplicated across tools. There is no cross-domain visibility. No automation. And a constant cognitive tax on deciding where something belongs.

Vritto exists to close that gap. Structured modules with the flexibility of sub-modules and cross-module references. Opinionated where it matters, flexible where it needs to be.

Core Design Philosophy

Five principles shape every product decision.

Modules as destinations. The unit of interaction is the module, not a database. Subscriptions is a place you go, not a table you configure. There is no ambiguity about where a piece of information lives.

Structure over flexibility. Every module has a defined schema. Structure is what makes the rest of the product possible: consistent UI, reliable search, AI-assisted entry, workflow automation, and a future module marketplace.

Sub-module hierarchy. Real life is nested. A University module contains Year sub-modules, which contain Course sub-modules, which contain assignment and exam entries. Sub-modules inherit context from their parent but define their own schema, so a Course can track credits and grades without forcing that shape onto the University above it.

Direct access, not buried. Every module is directly accessible from the sidebar. Themes exist to group modules visually, not to gate access. A user looking for Subscriptions should never have to guess which theme it lives inside.

AI assists, never replaces. AI proposes and the user confirms for every write operation. Ambiguous inputs trigger clarification, not guesses. Every AI action is logged for transparency. The goal is to remove typing, not judgment.

How Vritto Is Organized

The product ships with a curated catalog of roughly thirty-five predefined modules across ten themes. A representative slice:

• Time and Scheduling — Calendar, Meetings, Deadlines, Class Schedule
• Knowledge and Capture — Notes, Journal, Ideas, Links
• Life Management — Subscriptions, Insurance, Warranty, Orders, Card Expiry
• Health — Health Tracker, Medicines, Diet, Sleep
• Personal — Files, Profile, People
• Lists and Memory — Bucket List, Travel, Places, Life Moments
• Entertainment — Movies, TV Shows, Books
• Finance and Work — Job Applications, Financial Portfolio
• Assets — Clothes, Shoes
• Sports and Misc — Sports

Each module has a structured schema, a default view optimized for its data shape (list, table, calendar, board, gallery, detail), and a set of workflow triggers it can emit. A References system lets the same logical entity appear in multiple contexts without data duplication. Editing the canonical entry updates every reference.

The Feature Stack

Four capabilities sit on top of the module system and make it feel like a product rather than a database.

AI Engine. Natural-language entry converts free text into structured entries ("Add Netflix for $15 a month" becomes a Subscription). Smart field population auto-fills fields from partial input. AI search answers questions across modules ("What subscriptions are expiring this month?"). Cross-module insights identify patterns like "your sleep quality drops after late meetings." The AI never writes silently, ambiguous inputs trigger clarification, and every AI action is logged.

Workflows. A trigger, condition, action engine automates across modules. When a subscription renewal date is three days away, create a deadline entry, schedule a reminder on push and email, and tag the entry for review. Triggers include node created, node updated, date approaching, date passed, and manual run.

Search. Three tiers. Quick module and entry matching through a global palette. Field-filtered search within a module. Natural-language AI search across every module with structured context injection for accuracy.

Notifications. Channel choice is module-aware. Medicines default to push plus SMS. Subscriptions default to email plus in-app. Users configure per-module preferences, quiet hours, and digest frequency. Every channel is live from day one, not queued for a later release.

User-Controlled AI Access via MCP

One of the more opinionated product bets in Vritto is how it exposes user data to external AI assistants. Most apps today either refuse to let third-party AI touch their data at all, or dump everything into an integration with no meaningful user control. Both extremes are wrong.

Vritto takes a third path. Every user's workspace can be exposed to the AI assistant of their choice, such as Gemini, ChatGPT, Claude, or any future MCP-compatible client, through the Model Context Protocol. The unit of access is not the whole account. It is the individual module.

A few principles shape how this works.

• Per-module grant, not blanket access. A user might grant their AI assistant access to Subscriptions, Books, and Travel because they want conversational retrieval across those. They might withhold Health, Medicines, Finances, Journal, and People by default.
• Sensitive modules are off by default. Health, Medicines, Finances, Journal, and anything labeled personal or medical ship with MCP access disabled. Opting in is a deliberate action with a clear prompt explaining what is being shared and with which client.
• Read and write are separate scopes. A user can let an external AI read their Subscriptions to summarize monthly spend without allowing it to create or modify entries. Write access is a separate, narrower grant.
• Every MCP call is logged. Which client asked, which module was accessed, what was read or written, and when. Users can revoke access per client or per module at any time, and the audit trail remains.

The effect is that Vritto becomes a governed source of personal context that the user carries with them across whichever AI assistant they prefer, rather than another closed silo competing for the user's time. The data lives in Vritto. The intelligence can live wherever the user chooses.

Platforms

Vritto ships on three clients against a shared Firebase backend.

• Web. Primary platform for rich data management. Desktop-first with responsive tablet support. Full sidebar navigation, keyboard shortcuts, and rich-text editing where it matters.
• iOS. Native patterns, APNs push, widget support for the dashboard, HealthKit integration on the roadmap. Offline-capable with sync on reconnect.
• Android. Material Design 3, FCM push, widget support, Google Fit integration on the roadmap. Same offline model.

The data model, workflow engine, and AI capabilities are shared server-side, which means the product behaves identically across clients and does not require reimplementing logic in three places.

What Shipped, What's Next

The current MVP focuses on the module system, sub-module hierarchy, references, basic workflows, AI-assisted entry, notifications across all channels, and the three-platform foundation. Deliberately out of scope for this phase: a public module marketplace, multi-user shared workspaces, deep third-party integrations, and real-time collaboration.

The near-term roadmap extends Vritto in three directions. A module marketplace where users and the community can create and share modules beyond the default catalog. Deep integrations with Google and Apple calendar, bank APIs, and wearables. A more ambitious workflow builder for users who want to move beyond the preset triggers.

The long-term vision widens further: team and family workspaces, role-based access, an API layer for third-party developers to build on top of the module system, and user-defined custom modules.

Why This Project Matters to Me

Vritto is the first product I am building as the primary decision-maker rather than as an engineer on someone else's roadmap. It is also the first product I have designed top-down from a product requirements document before writing a single line of code. The PRD exists, the TDD exists, the module catalog and schemas are specified, and the engineering work follows from that, not the other way around.

That inversion matters. It is the difference between shipping features and shipping a product, and it is the skill I am trying to sharpen across every project on this portfolio. Vritto is the largest test of that discipline so far.