Skip to content
Writing

The 2-File Life OS: How I Stopped Building Systems and Started Shipping Code

2026-07-25

For a long time, I fell into the classic developer trap: spending three days configuring a productivity system instead of actually building my products.

I’ve experimented with it all—complex Notion databases, nested folder architectures, automated RAG pipelines, and local AI servers. Every time, the result was the same. The setup felt amazing for a week, but as soon as real client work, feature deadlines, and startup demands hit, the system collapsed under its own weight.

I was spending more cognitive energy asking "Where does this note go?" than actually solving the problem.

Eventually, I realized a simple equation:

System Complexity × Friction = Abandonment Rate

So, I stripped everything down to absolute bare-metal simplicity. Here is the Idea-to-Execution Life OS I use to manage my projects, client work, and personal development.

The Philosophy: "File Over App"

Instead of locking my data into proprietary cloud databases, my entire life lives in a local folder of standard, open-format Markdown .md files on my hard drive.

Influenced by Andrej Karpathy’s approach to personal knowledge management—which favors simple, append-only streams over complex hierarchies—this setup treats notes like source code. Plain text doesn't break, doesn't require a subscription, and never gets in the way of fast execution.

The Architecture: Just Two Core Files

You don't need a 20-folder hierarchy. You only need two files operating at two distinct speeds:

Life_OS/
├── 00_Stream.md           <-- High Speed (Instant Capture)
├── 01_Action.md           <-- High Focus (Execution Cockpit)
└── 02_Projects/          <-- Active Working Directories

1. 00_Stream.md (Zero-Friction Dump)

This is a single, continuous scratchpad note. Whenever an idea strikes, a client emails a new requirement, or I find a useful code snippet, I paste it right at the top with a timestamp.

The Rule: No tagging, no categorizing, no filing. Get the idea out of working memory in under 3 seconds so you can return to deep work immediately.

2. 01_Action.md (The Execution Cockpit)

This is the only file open on my screen when I am in focus mode. It contains:

  • TODAY (Max 3 Items): The non-negotiable tasks for the day. If it’s not in this list, I don't touch it.
  • ACTIVE PROJECTS: The immediate next steps for active products and client deliverables.
  • WAITING ON: Delegated tasks or external dependencies.

Bringing AI and Git into the Loop (Without the Bloat)

Keeping your core system simple doesn't mean giving up modern developer tooling. Because everything lives as local Markdown files, you get two massive superpowers for free:

  1. Git as an Immutable Engine: The vault is a Git repository. Auto-sync runs in the background. If an experimental script or bad edit messes up a note, git restore brings it back instantly.
  2. MCP (Model Context Protocol) Integration: Instead of copying and pasting notes into LLM prompts, local AI assistants (like Claude, Cursor, or Gemini) connect directly to the workspace via MCP. The AI can parse 00_Stream.md, summarize research papers, or draft project updates while strictly adhering to the file layout.

The 3 Operating Rules for Zero Maintenance

  1. Dump Fast: Write raw ideas in Stream without worrying about formatting.
  2. Pick Daily: Every morning, pull at most 3 items into Action under TODAY.
  3. Clean Weekly: Spend 5 minutes on Friday clearing out completed tasks and processing leftover notes in Stream.

Final Thoughts

The best productivity system is the one you forget exists because you're too busy shipping code, building products, and delivering results.

If your Life OS requires a manual or an hour of maintenance every week, it’s not an OS—it’s a hobby. Strip away the fluff, keep your files local, and focus on turning ideas into execution.