Four C's of an AI Operating System
The sequential framework Nate Herk uses to build and teach a personal AI Operating System (AIOS) in Claude Code. The four layers are Context, Connections, Capabilities, and Cadence — and they must be built in order.
Key points
- Context — what the AI knows about you, your business, your goals, and your constraints. Captured in CLAUDE.md, context files, and the onboarding interview [src-013]
- Connections — what data sources the AIOS can reach: calendar, email, task manager, meetings, revenue dashboards. Wired via APIs or MCPs [src-013]
- Capabilities — what the AIOS can produce: skills (reusable markdown SOPs), reference files, and task-specific sub-agents [src-013]
- Cadence — when it acts autonomously: cloud routines, /loop cron jobs, and daily planning habits [src-013]
- In the Opus 4.8 AIOS walkthrough, Nate applies the same four layers to his real second-brain operating system: business/project context, connections to recurring work surfaces, skills and templates as capabilities, and scheduled routines or usage habits as cadence [src-087].
- The framework now functions as both a build sequence and a diagnostic checklist: if an AIOS feels weak, ask whether it lacks context, useful connections, reusable capabilities, or an actual cadence of use [src-087].
The order is non-negotiable: "You can't have cadence without connections. You can't have capability without context" [src-013].
Related entities
- Claude Code — the primary harness for building an AIOS
- Nate Herk — coined this framework
Related concepts
- Three M's of AI — the mindset layer that precedes the Four C's
- AIOS Tier-One Domains — the seven data domains to connect in the C2 phase
- Six-Step Skill Building Framework — how to build capabilities in C3
- Claude Code Cloud Routines — the primary cadence mechanism
- Claude Code Memory 2.0 (AutoDream) — where context lives
- Progressive Context Loading (Skills) — how skills stay lightweight
- AI Memory Operating System — broader memory/control-plane pattern
- Agent Harness Portability — keeping AIOS context usable across Claude Code, Codex, Hermes, and future harnesses
Source references
- [src-013] Nate Herk — "Build & Sell Claude Code Operating Systems (2+ Hour Course)" (2026-05-01)
- [src-087] Nate Herk — "I Turned Claude Opus 4.8 Into My Entire AI Operating System" (2026-05-29)
Recommended next
Keep reading from this thread
From 491 indexed pages and articles.
- Wiki concept Global vs Project Skills Claude Code skills can be scoped to a single project (live in .claude/skills/) or installed globally (live in ~/.claude/skills/) and available from Related by 013
- Wiki concept Agent Harness Portability The practice of organizing project files, instructions, skills, tools, and operating context so multiple coding-agent runtimes can work in Related by nate
- Insight Recommendation Systems in Production How recommendation systems become production decisioning systems through signals, ranking, constraints, feedback loops, and experimentation Readers have engaged with this next