A new Claude model is a stress test for your second brain
If it knows your goals, customers, transcripts, tasks, calendar, revenue, and rules, it feels magic
If it can't find the right file, it burns tokens pretending
Build your AI OS with 4 Cs:
1. Context
- who you are
- what the business does
- where the rules live
- where projects, notes, wikis, and transcripts live
- one router file: CLAUDE.md, AGENTS.md, or both
2. Connections
- live data: email, calendar, Slack, Stripe, QuickBooks, ClickUp
- scoped API keys only
- read-only first
- prompts are never a permission layer
3. Capabilities
- skills for repeatable work
- agents for separate phases
- scripts for tests, screenshots, exports, reports
- every reused prompt becomes a file
4. Cadence
- manual: you ask
- event: email arrives, customer books, ticket opens
- schedule: Monday report, Sunday review, weekly cleanup
Folder shape:
.ai-os/
- 00_router.md
- 01_hot_cache.md
- 02_master_index.md
- people/
- business/
- projects/
- meetings/
- transcripts/
- skills/
- scripts/
- logs/
The gut check:
- can you find the file manually?
- can the agent find it fast?
- can it cite the source?
- can it act with read-only access?
- can you replace the model tomorrow?
If yes, you have a second brain.
When skills start running on triggers, you have an operating system.
Keep the keys scoped.
Keep the files plain.
Make the model replaceable.