~ [[AI Documentation Index]] # The EdOS Philosophy EdOS is a bespoke personal operating system — a set of interconnected tools, conventions, and habits designed to create a frictionless environment for thinking, deciding, and acting. --- ## Why It Exists Knowledge work generates an overwhelming volume of information: meeting notes, project files, reference material, tasks, ideas, relationships, and commitments. Without a system, these accumulate as cognitive debt — things you know you captured somewhere but can't retrieve when needed. EdOS exists to solve this. Its purpose is threefold: maximise effectiveness by putting the right information at the point of need, increase the chance of serendipitous connections between ideas, and reduce the friction and frustration that comes from disorganised systems. --- ## Core Principles **The primacy of linking.** Every artefact — a task, a note, a file, a calendar entry — should be linked to the things it relates to. Links are more durable than memory and more flexible than folders. A note can live in one folder but link to dozens of contexts. **Contextual computing.** Electronic artefacts should be available at the point of need. When working on a project, the relevant tasks, documents, meeting notes, and people should be reachable without searching from scratch. This is achieved through bidirectional linking across applications using tools like Hookmark. **Separation of knowledge.** Other people's ideas (sources, highlights, articles) are stored separately from Ed's own thinking. The Readwise library holds external knowledge; the Ideaverse holds personal notes, reflections, and synthesised understanding. This distinction preserves intellectual honesty — you always know whether an idea is yours or borrowed. **Search over recall.** The system is designed to be searched, not memorised. Consistent naming conventions, frontmatter properties, and full-text search mean that finding something is a query, not a memory test. **Keyboard-first interaction.** Speed matters. The system is optimised for keyboard shortcuts, quick capture, and minimal friction between thought and action. --- ## The Three-Layer Model EdOS operates across three layers, each with a distinct purpose: **The Ideaverse** is Ed's personal knowledge base — an Obsidian vault organised using a modified Linking Your Thinking (LYT) framework combined with Johnny Decimal numbering. It contains concepts, reflections, meeting records, project documentation, people notes, and Maps of Content (MOCs) that provide navigational structure. This is the sovereign layer — it belongs to Ed and represents his thinking. **The AI Documentation Layer** sits between the Ideaverse and AI tools. It contains structured, machine-readable notes that describe how Ed's systems work: conventions, workflows, key people, and architecture. AI tools read this layer to understand context without needing everything hardcoded into their instructions. When conventions change, they change here once. **The AI Tools Layer** includes Claude (via skills and MCPs), autonomous agents (morning briefer, meeting prep, weekly review), and semantic search (ChromaDB vectors). These tools read from the AI Documentation layer and act on the Ideaverse and connected systems. Skills are thin dispatchers — they know *how* to operate but load *what conventions to follow* from the translation layer. --- ## The Three Systems Day-to-day work flows through three interconnected systems: **OmniFocus** handles task management using a Getting Things Done (GTD) methodology. It is the authoritative source for what needs doing, when it's due, and what's waiting on someone else. **Obsidian** ("Ed's Brain") handles knowledge management. It is the authoritative source for what Ed knows, thinks, and has recorded. Notes are organised by Johnny Decimal codes that mirror the areas of Ed's life and work. **The filesystem** (Desktop and OneDrive/iCloud) handles document storage. Project folders, spreadsheets, presentations, and other working files live here, organised to mirror the JD structure. These three systems are connected by Hookmark (bidirectional links between items across all three) and by consistent JD codes that appear in OmniFocus project names, Obsidian note filenames, and Desktop folder names. --- ## Design Philosophy EdOS is opinionated about a few things: **Convention over configuration.** Consistent rules (naming conventions, frontmatter schemas, filing heuristics) mean less decision-making in the moment. When you know where things go, you spend less time deciding and more time doing. **Single source of truth.** Every piece of information has one canonical home. Tasks live in OmniFocus. Knowledge lives in Obsidian. Files live on the filesystem. Conventions live in AI Documentation. Duplication is actively eliminated. **Progressive disclosure.** Not everything needs to be visible at once. MOCs provide high-level navigation. Dataview queries surface relevant connections dynamically. Detailed conventions are loaded only when needed. **Human sovereignty.** AI augments but does not replace Ed's thinking or decision-making. AI tools read from documentation Ed maintains. Significant changes to conventions require Ed's approval. The system is designed to make Ed more effective, not to automate Ed away. --- ## Evolution EdOS is not static. It began as a collection of disconnected tools and has evolved through deliberate iteration — adopting PKM practices from Tiago Forte and Nick Milo, integrating AI capabilities through Claude, and continuously refining conventions based on what actually works in practice. The system will continue to evolve. What matters is not the specific tools but the principles: link everything, reduce friction, separate concerns, and maintain a single source of truth.