prodbycjbeatsss/GemOS

The current reviewed card sets and their documentation are indexed in docs/dashboard/README.md. Start there for the review plan, shared design rules, group behaviour and connection research. The operating-system kit documentation below is preserved.
AIS-OS: AI Operating System starter kit for Claude Code and Codex
A free, MIT-licensed starter kit that turns Claude Code or Codex into your personal **AI Operating System (AI OS)**. Audience: anyone building automations — solopreneurs, small business operators, managers, creators, AI consultants. Pairs with a companion masterclass video.
The kit personalizes itself to you via an /onboard interview. Use /grill-me whenever you want to deepen its understanding of your business, preferences, or plans. Use /link to make new information findable, /audit to verify the system, /level-up to close one useful gap at a time, and /3d-brain to explore your saved knowledge as an interactive globe.
> **AIS-OS** stands for **AI Automation Society OS** — the way Nate designed this AI OS to be set up for members of his community, AI Automation Society. The kit is universal (it works for anyone), but the structure mirrors how AIS members run their own businesses on top of it.
---
The litmus test
> **"While you're not at your desk, your AIS-OS observes one real-world event and produces an output that's faster and more accurate than what you'd produce yourself."**
Every design decision in this kit rolls up to that test. If a layer, skill, or template doesn't contribute to it, it doesn't ship.
---
How you'll know it's working
Three felt **success indicators** tell you the AI OS is actually changing how you work. Not KPIs — there's no objective metric. These are lived experiences that show up in your week.
**1. Team-reaches-out:**
> *"A teammate messages you with a question. You realize your AI OS would answer it better, faster, and with exact sources — even if you were awake and free. So you ask your AI OS too. That's the moment you stop being a bottleneck for your own knowledge."*
**2. Context-switching reduction:**
> *"You stop opening new tabs. You stop launching the desktop app. When something new lands, your first move is to ask the AI OS, not to open six things. The default surface for thought work shifts. Silent. Compounding."*
**3. Knowledge-leaves-your-head:**
> *"You stop trying to remember business facts. You don't rehearse what you decided last quarter or what your customer said in that meeting. You trust the retrieval. The AI OS holds the truth, you hold the questions."*
**Personal foundation → company AI-readiness.** Once these indicators show up for one person, the same data architecture powers everything else. Custom dashboards on the data you already collect. Automations on top of the connections you already wired. Team rollout where everyone has theirs. *A company where every operator runs a personal AI OS is a company that's actually AI-ready.*
The kit teaches personal AI OS first. Everything scales from there.
---
Two frameworks
The kit teaches two complementary frameworks. **Three Ms first, Four Cs second.** Without the brain rewire, the architecture is just a folder structure.
The Three Ms — operator brain (how you think)
| M | One-liner |
|---|---|
| **Mindset** | Default Shift, Function Breakdown, Curiosity Rule. *To what extent can AI be leveraged here?* |
| **Method** | Find Constraint → EAD (Eliminate, Automate, Delegate) → Map Process → Pick Autonomy Level → Tie to KPI. |
| **Machine** | Lego Principle, Validation Chain, Bike Method, Intern Rule, Kill Switch. *Boring is beautiful. Workflows beat agents.* |
Full breakdown in references/3ms-framework.md. The /level-up skill walks you through all three weekly.
> *The Three Ms of AI™ is a trademark of Nate Herk. © 2026 Nate Herk.*
The Four Cs — architecture (what you build)