ONE MIND CODEX
Human + AI = One Mind. This is the operating system.
1. Executive Summary
One Mind is an AI-native life operating system. Not a note-taking method. Not a productivity hack. A complete cognitive architecture where a human and their AI agents share a single, structured knowledge base — and act on it together.
Every prior framework — GTD, PARA, CODE, Zettelkasten — was designed for humans working alone. They assume you are the only reader, the only executor, the only reviewer. That assumption died the moment AI agents became capable of reading your notes, running your tasks, and reporting back.
One Mind starts where they stop:
- Structured for AI — every document has machine-readable frontmatter, typed metadata, and progressive disclosure layers so agents can navigate without reading everything.
- Execution built in — capture and organize are table stakes. One Mind includes direction, execution, and multiplication (compounding feedback) as first-class steps.
- Entity taxonomy — 17 entity types across 5 categories (intent, knowledge, measurement, operator, capability) so the system knows WHAT something is, not just where it’s filed.
- Tool-agnostic — the vault is plain Markdown in folders. Obsidian today, whatever tomorrow. Your system outlives any app.
The result: a life OS that a human steers and AI agents execute against — together forming one mind.
2. The Vision
The Evolution of Personal Knowledge Systems
| System | Year | Philosophy | AI Role | Execution |
|---|---|---|---|---|
| GTD (David Allen) | 2001 | ”Mind like water” — capture everything, decide next actions | None | Human only |
| PARA (Tiago Forte) | 2017 | ”Second brain” — organize by actionability | None | Human only |
| CODE (Tiago Forte) | 2022 | Capture → Organize → Distill → Express | None | Human only |
| One Mind (Zeus Delacruz) | 2025 | ”Life OS” — human + AI cognitive architecture | First-class participant | Human + AI agents |
GTD gave us the capture habit. PARA gave us structure. CODE gave us a creative workflow. One Mind gives us an operating system — one that AI agents can read, navigate, and execute against alongside the human who built it.
Five Differentiators
1. AI-Native Architecture
Every document has YAML frontmatter with ai_summary, typed tags, and status fields. Agents don’t need to read 10,000 words to understand your vault — they scan summaries, check types, and drill down only when needed.
2. Unified Life Model Three life domains plus one operating layer cover your entire existence — not just work, not just projects. Your health, your foundation, your endeavor, and your infrastructure all live in one system with one schema.
3. Tool-Agnostic by Design
Plain Markdown files in folders. No proprietary database. No vendor lock-in. Move between Obsidian, VS Code, Logseq, or raw vim — the system doesn’t care. Your operating system outlives any tool.
4. Solar-Punk Philosophy Build systems that compound. Design for resilience. Think in generations, not quarters. Technology serves human flourishing — not the other way around.
5. Generational Design The LE (Legacy Evolution) domain explicitly covers family, estate, and multi-generational planning. Your system should outlive you and serve those who come after.
3. The CODEX Method
Every piece of information flows through five stages:
┌─────────┐ ┌───────────┐ ┌────────┐ ┌─────────┐ ┌──────────┐
│ CAPTURE │───▶│ ORGANIZE │───▶│ DIRECT │───▶│ EXECUTE │───▶│ × MULTI- │
│ │ │ │ │ │ │ │ │ PLY │
└─────────┘ └───────────┘ └────────┘ └─────────┘ └──────────┘
Inbox, voice, 3 domains + SO, Command: Operators Review,
quick capture 100 domains, prioritize, run the work: measure,
from anywhere entity types, assign owner, humans, agents,extract
frontmatter define done SOPs, skills lessons
│
◀─── each cycle multiplies the system ─────┘
The X in CODEX is × — the multiplication sign. Every cycle through the loop multiplies the system’s intelligence: metrics get tracked, SOPs get refined, agents get smarter, knowledge compounds.
How CODEX Compares
| Capability | GTD | PARA | CODE | CODEX |
|---|---|---|---|---|
| Capture system | ✅ | ✅ | ✅ | ✅ |
| Organization framework | ✅ | ✅ | ✅ | ✅ |
| Covers entire life | ❌ | ❌ | ❌ | ✅ |
| AI can navigate | ❌ | ❌ | ❌ | ✅ |
| AI can execute | ❌ | ❌ | ❌ | ✅ |
| Entity type system | ❌ | ❌ | ❌ | ✅ (17 types) |
| Built-in metrics | ❌ | ❌ | ❌ | ✅ |
| Compounding feedback | ❌ | ❌ | ❌ | ✅ |
| Tool-agnostic | ✅ | ❌ | ❌ | ✅ |
| Progressive activation | ❌ | ❌ | ❌ | ✅ (4 → 100) |
CODEX isn’t better at note-taking. It’s a different category — a life operating system with AI execution and built-in accountability.
4. The Architecture: 3 Domains + 1 Operating Layer
One Mind OS is NOT four equal boxes. It’s three life domains running on one operating layer — like apps running on an OS.
┌──────────────────────────────────────────────────────┐
│ SO — Sovereign Operations (00–24) │
│ The operating layer that runs everything │
├────────────────┬─────────────────┬───────────────────┤
│ 💪 HP (25–49) │ 🏡 LE (50–74) │ 👑 GE (75–99) │
│ Your Self │ Your Foundation │ Your Endeavor │
└────────────────┴─────────────────┴───────────────────┘
🧠 SO — Sovereign Operations (00–24) — The Operating Layer
The layer that runs your life. SO is NOT a life domain — it’s the platform the other three run on. Your agents, tools, protocols, automations, and system infrastructure all live here.
Think of it this way: HP, LE, and GE are the WHAT of your life. SO is the HOW. Without SO, the three domains are disconnected folders. With SO, they’re an operating system.
SO comes first in the numbering (00–24) because the foundation gets laid before the house. Every capture flows through SO’s inbox. Every automation fires from SO. Every agent lives in SO and serves HP, LE, and GE.
Contains: Framework doctrine, AI agents, protocols & SOPs, inbox queue, infrastructure, automation, development, security, research.
💪 HP — Holistic Performance (25–49) — The Self
Everything about YOU. Health, fitness, mental performance, skills, personal finance, learning.
Your body is the hardware. HP covers everything about maintaining and upgrading it — physical training, nutrition, mental health, skill acquisition, and personal wealth.
Contains: Identity, intelligence, body, mastery, life systems, finance, sovereignty, relationships, spirituality, joy.
🏡 LE — Legacy Evolution (50–74) — Your Foundation
Everything beyond yourself. The relationships, community, home, and environment you build around you.
Not everyone has a family — but everyone has a foundation. For some that’s marriage, children, and estate planning. For others it’s friendships, mentorship, community, and creative legacy. Whatever you’re building that outlasts your daily routine — that’s LE.
Contains: Home, relationships (marriage, partnerships), children, parents, heritage, community, environment, estate, legal.
👑 GE — Generational Endeavor (75–99) — Your Endeavor
How you create value and grow your impact. Career, ventures, brand, wealth, education, IP.
An endeavor is any purposeful undertaking you pour your energy into — a teacher’s career is an endeavor, an artist’s body of work is an endeavor, an entrepreneur’s business is an endeavor. GE covers your career, your craft, your brand, your income, and everything you build that creates value in the world.
Contains: Personal brand, education, IP & platforms, technology, treasury, strategy, career, partnerships, ventures.
Why This Hierarchy Matters
The distinction between SO and the three life domains is the most important structural decision in the framework:
- For beginners: “You have 3 life folders and 1 system folder.” — instantly understandable.
- For agents: SO is where agent configs, skills, and AOPs live. The agent reads SO first, then serves HP/LE/GE.
- For the book: SO is the foundation chapter. HP/LE/GE are the application chapters.
- For teaching: “Sovereign Operations is where you COMMAND. The three domains are where you LIVE.”
5. Implementation
Vault Structure
your-codex/
├── _codex/ ← System files (start here)
│ ├── INTERFACE.md ← Navigation guide for humans and AI
│ ├── CONVENTIONS.md ← Naming, tagging, and formatting rules
│ ├── system/ ← Pinned context (always-loaded by agents)
│ ├── templates/ ← Document templates for every type
│ ├── profiles/ ← Review and performance profiles
│ └── skills/ ← Agent skill definitions
├── 00-24 SO/ ← 🧠 Sovereign Operations
├── 25-49 HP/ ← 💪 Holistic Performance
├── 50-74 LE/ ← 🏡 Legacy Evolution
├── 75-99 GE/ ← 👑 Generational Endeavor
├── ONEMIND-CODEX.md ← This file (master document)
├── CODEX-FRAMEWORK.md ← Deep-dive on the CODEX method
└── AGENTS.md ← Instructions for AI agents
Key Concepts
_codex/— the system folder. Contains everything agents and humans need to understand and operate this vault._codex/system/— pinned context files that agents load first. Contains the current state of domains, active priorities, and operational rules._codex/templates/— standard templates for every document type (note, decision, SOP, project, person, review, etc.)._codex/profiles/— review cadences and performance profiles for weekly/monthly examination.- Frontmatter — every document has YAML frontmatter with
title,type,status,tags, andai_summary. This is how agents navigate without reading everything. - Progressive Disclosure — agents load context in layers: L0 (system/), L1 (ai_summary scan), L2 (full read), L3 (linked files).
6. Getting Started
For Humans
- Fork this vault — clone it, make it yours.
- Open in Obsidian — or any Markdown editor. Obsidian recommended for the best experience.
- Read
QUICK-START.md— the 30-minute onboarding guide. Four buckets, three templates, one weekly review. - Start capturing — use templates from
_codex/templates/. Start with goal, task, and note templates. - **Start with 3 domains + SO, not 100 sub-domains — drop things into the right place. Domains activate as your life expands. See CODEX-FRAMEWORK.md for the Progressive Activation guide.
- Review weekly — the × (multiply) step isn’t optional. Use the review profile in
_codex/profiles/to stay accountable. Each review cycle multiplies the system’s value.
For AI Agents
- Read
AGENTS.md— operating instructions for working in this vault. - Load
_codex/system/— pinned context files. This is your ground truth. - Scan
ai_summaryfields — don’t read everything. Scan summaries, drill down as needed. - Follow templates — when creating documents, always use the template for that document type.
- Never create top-level folders — route uncertain content to the inbox.
The Philosophy
“The goal isn’t to remember everything. It’s to build a system that remembers for you, acts for you, and gets better every week.”
One Mind isn’t about perfect notes. It’s about building a cognitive operating system that compounds — where every document, every decision, and every review makes the whole system smarter. Human intelligence sets the direction. AI intelligence handles the execution. Together: One Mind.
Built by Zeus Delacruz. Fork it. Make it yours. Build your own One Mind.

