AI Operating System (AIOS)
AI Operating System (AIOS)
A single AI workspace — for Nate Herk (AI Automation), Claude Code running Opus 4.8 — that you work out of by default instead of tab-switching across chat apps, browsers, and SaaS tools. It holds all your context, can touch your real tools, and runs work on a cadence. Nate's term for his "second brain / executive assistant" once he realized he reaches for it first.
The analogy is literal: like Windows/macOS/iOS, an AIOS is "the way you interact with your systems and get work done." The substrate is just files and folders, which makes it tool-agnostic (the same OS opens in Claude Code, Codex, or OpenClaw via per-agent config folders) and fully crawlable/reorganizable by the AI itself.
What makes it an OS (vs. a chatbot)
- It knows your business — meeting transcripts, posts, threads, email, docs. Recall better and faster than the human owner.
- It's the default surface — see Default Shift. Brainstorming, writing, and planning happen here too, not just code.
- It's structured for scale — folders for decisions, audits, archives, and "other worlds" (standalone sub-projects), so context stays findable as the business evolves. By the Fable-era walkthrough (I Turned Claude Fable Into The Ultimate Second Brain (Nate Herk)) "other worlds" has matured into the load-bearing pattern: formerly separate repos pulled inside the main project so one agent
cds between them and one GitHub push syncs everything — the structural twin of this machine's~/worlds.mdhub. See Architecture Engineering for the routing-tree discipline that keeps it navigable. - It compounds — every session adds context; every skill run improves the skill. "If it slips up, you get data" — even the 150k-email incident was treated as a case study, not a firing offense.
How it's built
Two frameworks from the source:
- Three M's — Mindset, Method, Machine (the how you think about it layer).
- Four C's Framework — Context → Connections → Capabilities → Cadence (the architecture; each layer depends on the prior one).
The hard-won caution layer: as reach grows, so does risk — govern it with the Bike Method and by scoping capabilities, not just instructions.
The identity claim, sharpened in the Fable walkthrough: "You're not building a Claude Code AIOS — you're building your own personal operating system." Folders, markdown, skills, and routing logic are portable IP; Nate keeps parallel claude.md/agents.md configs and runs the same OS in Codex daily. Model/harness churn is plug-and-play, which "should remove the overwhelm about staying up to date with the latest drops."
Relation to this vault
This Second Brain is itself a proto-AIOS: an LLM Wiki Pattern store of files/folders that an agent maintains. The applied question of upgrading this machine into a full AIOS is worked through in Turning This Mac Into an AI Operating System.
Cross-links
- Four C's Framework · Default Shift · Bike Method · Capabilities vs Instructions (Agent Keys)
- Claude Code · Context Engineering · Harness (LLM Agents) · Code Is Free
- Enterprise OpenClaw Playbook (Synthesis) — the enterprise-scale cousin of the same idea