Documentation

Architecture

How It Works

LifeOS uses Notion as its canonical data store. The Notion MCP (Model Context Protocol) server acts as the bridge between your Notion workspace and the LifeOS agent ecosystem. Data flows bidirectionally — agents read context from Notion pages and write observations, scores, and decisions back as structured database entries.

The 5 Layers

Each layer corresponds to a top-level Notion database. Together they form a complete model of your life system.

Identity Core values, purpose, life narrative, and personal sovereignty
Relationships Family, partnerships, friendships, community, and social capital
Work Career, projects, skills, and professional development
Health Physical fitness, nutrition, sleep, and mental well-being
Finances Income, expenses, investments, and capital allocation

The 9 Currencies

Currencies are tracked across layers and updated by agents during their reflection cycles. Each currency has a dedicated tracker database.

Time How you allocate your most finite resource
Energy Physical, emotional, and cognitive capacity
Attention Focal awareness and presence
Health Vitality and biological capital
Relationships Social bonds and network depth
Knowledge Information, wisdom, and skill acquisition
Money Financial resources and purchasing power
Meaning Purpose alignment and fulfillment
Freedom Autonomy and optionality
Pipeline

MCP Data Flow

1. Read Agent queries Notion for current layer/currency state
2. Process Agent runs analysis against its role prompt and goals
3. Write Agent writes observations, scores, and decisions back to Notion
Security

Data Privacy

The Notion MCP integration uses scoped API tokens provided from your LifeOS dashboard. Tokens are stored encrypted at rest and can be revoked at any time. Agent data access is restricted to the databases you explicitly authorize.

All data remains in your Notion workspace. LifeOS never stores a copy of your raw Notion content.