What Is a Personal Context Engine (Life OS)?
A personal Context Engine is the always-on layer that turns the systems you already live in into a Life Knowledge Graph. A Life OS is the product on top: AI that starts from your Work · Money · Health · Life context — not a blank chat — and helps you move from context → clarity → action.
Decimal Life (Deci) is building this as invite-only personal life-context AI. This page defines the category — not a pitch deck.
Personal Context Engine (Life OS): A personal Context Engine continuously turns the apps and signals you already use — calendar, email, health, work tools, and more — into a Life Knowledge Graph. A Life OS is the product layer on top: AI that starts from your multi-domain context so it can help you move from context to clarity to action, instead of restarting from a blank chat.
What is a personal Context Engine?
Most AI conversations start cold. You paste a prompt. Maybe the product remembers a few facts from earlier chats. Then you re-explain your calendar constraints, your goals, your project state, and why Thursday workouts never stick.
A personal Context Engine flips that default.
Instead of treating every session like a stranger interview, it continuously structures the life systems you choose to connect — so the AI can retrieve relevant context when you ask, or when a decision surfaces in a module.
The structured output of that engine is a Life Knowledge Graph: people, plans, habits, health signals, work items, and how they relate. Think of it as the difference between a pile of notes and a map you can query.
This is conceptual, not an architecture dump. The point is simple: persistence + structure across domains, not just a longer chat history.
What is a Life OS?
A Life OS is an operating layer for your life domains — Work · Money · Health · Life — not a single chat thread with a clever system prompt.
In Decimal Life, domain surfaces show up as modules (examples, not a closed catalog): Startup OS, Health OS, Developer OS, Habits OS. Each is a place where context becomes decisions and next actions — not another inbox of notes.
Life OS vs a second brain
A second brain (notes, PKM, wiki) is invaluable for capturing thinking. A Life OS aims further: it includes living systems (calendar, mail, health signals, shipping work) and tries to help you decide and act, not only store.
Notes can feed the Context Engine. They are not the whole product.
Why generic AI still feels “cold” (even with memory)
Stateless models forget. Product “memory” helps — but it is usually selective, chat-derived, and thin compared to the full texture of a real week.
The pain shows up as:
- Re-explaining goals every session
- Calendar constraints the model doesn’t know
- Health or energy signals that never enter the plan
- Project state stuck in GitHub / Linear while the chat stays generic
That is a category gap, not a roast of any one chatbot. Chat memory is useful. It is not the same as a Life Knowledge Graph built from authorized life systems.
How a Context Engine works (high level)
- You connect sources you choose — e.g. Google Calendar, Gmail, Apple/Google Health, GitHub, Linear. Nothing is connected by default.
- The Context Engine builds and updates your Life Knowledge Graph — entities, relationships, and summaries used at answer time.
- Deci retrieves relevant context when you ask, or when a module surfaces a decision.
- You get clarity and a next action grounded in your real constraints — schedule, recovery, goals, shipping work — not generic advice.
Illustrative example (not medical advice): if recovery and calendar both suggest room to move, a Health-oriented surface might help you reschedule a workout you keep skipping — after checking with you, not silently “optimizing” your life away.
Context Engine vs chatbots vs personal agents
Criteria-first — no fake scores:
| Criterion | Generic chatbot | Chatbot with memory | Personal agent / autopilot claims | Personal Context Engine / Life OS (Decimal Life direction) |
|---|---|---|---|---|
| Starts from your life systems | Usually no | Rarely; mostly chat-derived | Varies; often task-focused | Yes — connected systems you authorize |
| Persistence across domains | Session / thin | Selective chat memory | Tool-specific | Cross-domain Life Knowledge Graph |
| Structure of knowledge | Prompt + history | Saved facts / retrieved chats | Workflows / tools | Graph of entities + relationships |
| Path to action | Advice in chat | Personalized advice | May automate steps | Context → clarity → action in life modules |
| User control over sources | N/A | Memory settings | Tool permissions | Connect / disconnect; privacy controls |
| Ownership narrative | Vendor chat silo | Vendor memory | Varies | Your life context as product core (private beta) |
Open-source “context engine” and Life OS projects exist in the wild. Decimal Life’s productized angle is connected life systems + Deci + domain modules, currently in private beta — not a claim that every automation race is already won.
What Decimal Life (Deci) is — and is not
Is:
- Invite-only personal life-context AI / Life OS
- Context Engine → Life Knowledge Graph
- Positioning: Context → Clarity → Action
- Domains: Work · Money · Health · Life
Is not:
- An unrelated Decimal finance or math brand
- A doctor, therapist, or clinical product
- A financial advisor, tax tool, or investment product
- A generally available public app today (waitlist / private beta)
If you searched “Decimal” and landed here looking for finance or math software — wrong product. Decimal Life is personal life-context AI.
Privacy and control
Trust is part of the category definition.
- Nothing connected by default — you authorize each source
- Disconnect anytime
- Export / delete controls by domain (see the public privacy framing)
- Derived Context Engine data is treated with source data on deletion
- Contact: privacy@decimallife.com
Read the full policy: Privacy. This page does not replace it.
Decimal Life uses cloud infrastructure and model inference where the product requires it — do not assume “local-only.” Control lives in what you connect, what you export, and what you delete.
Who this is for
Broadly: anyone evaluating personal AI, a Life OS, or “AI that actually knows my life” — and tired of re-briefing every session.
Light examples (not a locked ICP):
- Founders and builders living in calendar + shipping tools who need what matters tonight, not a longer list
- Knowledge workers whose notes, mail, and goals never talk to each other
- Anyone building habits or health routines who wants context that checks before it assumes
If your tools don’t talk, you are still the integration layer. A personal Context Engine / Life OS is built to change that.
FAQ
- What is a personal Context Engine?
- A personal Context Engine continuously turns the apps and signals you authorize into a Life Knowledge Graph so AI can start from your real multi-domain context instead of a blank chat.
- What is a Life OS?
- A Life OS is the product layer on that graph: an operating layer across Work · Money · Health · Life that aims at clarity and action, not only chat replies.
- How is a Context Engine different from ChatGPT memory?
- Chat memory is usually selective and chat-derived. A Context Engine structures authorized life systems (calendar, mail, health, work tools, and more) into a graph used at answer time.
- What is a Life Knowledge Graph?
- A structured map of entities and relationships in your life context — people, plans, habits, health signals, work items — maintained by the Context Engine for retrieval and decisions.
- What apps can a Life OS connect to?
- In Decimal Life’s public framing, examples include Google Calendar, Gmail, Apple/Google Health, GitHub, and Linear — only with your authorization. Nothing is connected by default.
- Is Decimal Life a finance or math product?
- No. Decimal Life (Deci) is personal life-context AI / Life OS. It is not related to Decimal finance or math brands.
- Is Decimal Life available to everyone?
- Not yet. It is invite-only private beta / waitlist.
- Does connecting health or email data mean Deci gives medical or financial advice?
- No. Health and life examples are illustrative product behavior. Deci is not a doctor, therapist, or financial advisor.
- How do I control or delete my connected data?
- Use connect/disconnect controls and the export/delete options described in the Privacy Policy. Derived Context Engine data is treated with source data on deletion.
- Who is a personal Life OS for?
- People who want AI that starts from their real life context — especially if they are tired of being the human API between their tools.
Get started
If this category is what you’ve been looking for:
- Primary: Request an invite — join the private beta waitlist on the homepage
- Secondary: Read the Privacy Policy
Request an invite — Deci runs on your Context Engine.