a personal ai operating system.
three tools. one nervous system. yours.
three tools. one nervous system. yours.
chapter ii — before
There's another way.
chapter iii — the cast
Roles, not religion. I use Kiro at work and Cowork at home. Claude works on either side too — pick what fits.
"reads the room, drafts the plan."
What it is. An AI development environment from AWS. You give it a spec, it builds. Currently free during open beta.
Why it's here. It's the AI you bring into work — code, docs, specs, the deliverable side of life. It works where the deadlines live.
get kiro · free → or use Claude for work →
"the one that knows your life."
What it is. A personal AI companion that lives next to your notes. Reads what you've written, talks to you about it, helps you think.
Why it's here. It's the AI for the rest of your life — your relationships, your projects, your health, the email you keep meaning to send. The one with context.
try cowork → or use Claude for personal →
"plain text. yours forever."
What it is. A note-taking app that's secretly a folder of markdown files on your computer. Free, local, open at its core.
Why it's here. It's the memory that makes the AIs useful. Without it, every conversation starts from zero. With it, your tools know who you are.
download obsidian · free →chapter iv — the bet behind it
A SaaS chatbot starts from zero every time you log in. This system gets better at being you every week. The notes pile up. The patterns get clearer. Year three is unrecognizable from month one.
Your notes are plain text files in a folder on your computer. Not in someone's database. Not subject to a pricing change. Not deprecated next quarter. You'll be able to open them in twenty years.
The "AI app that does everything" does each thing okay. Kiro is built for the work surface. Cowork is built for the personal surface. Obsidian is built for memory. Specialists, working from the same files.
This isn't a chatbot you visit. It's a presence that reads what you wrote on Sunday and asks about it on Wednesday. It notices what's slipping. It surfaces what mattered. You stop being the only one paying attention to your own life.
Each tool is great alone. The leverage is in the loop between them.
chapter v — a day
monday · 7:42 am
three quiet things before the day picks up.
Obsidian saves these design choices automatically. Because everything's local, the dashboards update instantly.
watch it happen live · next chapter →chapter vi — watch it happen
claude reads it. obsidian remembers it. the dashboard surfaces it. no copy-paste.
chapter vii — what unlocks
Once your tools can read your notes, the moves change. Here's what becomes possible — concrete, not magical.
Send the chaos from your phone — links, screenshots, half-thoughts, voice memos. Claude tags, files, and links them in seconds. The shower thought lands in /inbox before you've toweled off.
One note that always knows what you're in the middle of. Claude updates it as you work. Tomorrow morning you pick up exactly where you left off — not where your tabs did.
Once a week, Claude reads your last fourteen days of notes and tells you what you keep almost-doing. The thing you've written about three Sundays in a row but haven't started.
Before you draft, Claude pulls every note tagged to the topic. You start with your full thinking laid out in front of you — no blank page, no archeology.
Each move trades an hour of fiddling for a single sentence. how someone else built it →
chapter viii — your turn
Most people stall on systems because they're too clever. Here's the dumb version that actually works. Do it in order.
~3 minutes · free
Make a new vault called life. That's it. No plugins yet. The point is to have a folder of markdown files you control.
~5 minutes
Inside your vault, create exactly this. Don't add more. Empty folders are fine — they fill themselves.
/inbox ← raw capture lands here
/projects ← one file per project
/people ← one file per person who matters
/journal ← daily notes, dated
/reference
/how-i-think ← prompts, frameworks, principles
/dashboards
today.md ← your morning view
~5 minutes · both have free tiers
Point it at your /projects folder so it reads what you're actually building. Either one works — Kiro is spec-driven and built for code; Claude is broader and lives anywhere.
~5 minutes
Point it at /journal and /people. Now an AI knows what you wrote last Sunday. Cowork is built for this; Claude works too if you'd rather not run two AIs.
~2 minutes
Open Cowork and paste this. It's the cheapest possible proof that something has changed.
Read my board meeting prep from the last
two weeks. Pull the three threads I keep
returning to. Draft the opening in my voice.
That's the whole setup. The rest is just showing up to your own life in writing.
chapter ix — the bet
It's local. It's yours. It compounds.
It reads your notes, not someone else's product roadmap. It remembers what mattered to you in March. It writes in your voice because it's been listening to your voice for a year.
The work tools we've been given are rented. They forget you the moment you log out.
This is the other path. Small, owned, personal. A system that knows you, kept in plain text you can carry anywhere.
Build the one only you could build.