You’ve spent years learning how to do your job.This is where you write it down so it runs.
You already know how to do this work. What’s missing is somewhere for that knowledge to live and keep working — even after you’ve moved on. That’s what you build here, one gate at a time.
Pick a gate to see what you add, what you can do once it's in, and what you walk away holding.
Your folder at this gate
Three files. Everything after this reuses them, which is why Gate 1 changes the most for the least work.
Gate 1
Remember
Say it once, and every answer after arrives in your shape.
Build your Context files — free →- What you add
Context/— agents.md, memory.md, role_profile.md- Proof you're through
- Ask for a deliverable without saying how you want it. It comes back right.
- What you walk away with
- A Context folder that reads like you, not like the template.
- Time to add
- About 20 minutes, once.
Do it
Open a step for the detailIn OneDrive, create _My_AI_OS with three folders inside it. The underscore keeps it at the top of your file list, which matters more than it sounds like it does — you will open this every day.
_My_AI_OS/ ├── Context/ ← who you are, how you work ├── Skills/ ← what you do, step by step └── Active/ ← where finished work lands
You now have somewhere Copilot can always find. Everything after this is filling it in.
You get this file pre-written. You change three things: your team, your two non-negotiables, and the format you want things to arrive in by default.
## Persona - Organization: [your team] - Stance: concise, structured, data-backed, no filler ## Non-negotiables 1. Never assume — if something is missing, ask or state the assumption 2. Nothing gets sent or changed without my approval
Every output from here on inherits these rules. You stop re-typing them.
Also pre-written, seeded with five common preferences. Read them and overwrite the ones that aren't you. This file is meant to be edited constantly — it is the one that gets sharper every week.
## Communication - Tone: direct, action-oriented - Tables for comparisons, bullets for steps - Email: summary first, one clear ask, no fluff sign-off
This is the file that makes it sound like you instead of like software. Edit one line and you'll hear the difference in the next answer.
Half a page: what you're accountable for, who you report to and who reports to you, the five things that land on your desk every week. Written badly, it still works. Written honestly, it works much better.
Context stops being generic. Copilot now knows what "the weekly update" means to you specifically.
Reference the folder in Copilot, then ask for something without telling it how you want it. No format instructions, no tone notes, no length. If it comes back in your shape, you are through Gate 1.
Using the files in _My_AI_OS/Context, draft an update on the reporting migration for my manager.
This is the demonstration you bring to the ritual. It takes about forty seconds to show.
What "it comes back right" looks like in your role
Senior Data / Systems AnalystYou ask for a write-up on a DAX fix. It arrives in your structure — problem, root cause, change, validation — without you naming those headings.
One problem, felt two different ways
If you’re the leader
Your expertise only exists in real time — if you’re not in the room, it isn’t available. Write it down once and it starts answering for you while you’re doing something else.
If you’re the company
That expertise is undocumented, so every reorg and every departure charges you for it twice. Written down in a shared format, it stays on your side of the door.
Three layers, three owners
Personal
Yours — leaves with you
Your voice, your defaults, your standards — written once in Context/ and yours to take to every job you ever have.
Team
The function’s — survives reorgs
The recurring deliverables you’ve proven. They live in the team repo with your name on them, still running after you’ve moved.
Org
The enterprise’s — already governed
Governed skills and connectors, under the controls you already work inside — so nothing you build here needs a new approval to be legitimate.
Your unique craft and personal edge are the magic that happens when you turn your methodology into repeatable processes for your biggest distractions and challenges. That work becomes a permanent upgrade for the organization — a lasting gift to the culture and capability of the team that endures. In return, you receive hours, days and weeks of your time and focus on what matters most to you. Period.
Everybody comes back and shows what they built
There’s no fifth training session. There’s a standing gathering where you show what you’ve built since the last one — three minutes, whatever you’ve got. That’s how badges are earned: you show, you don’t attend.
- The floor is low, and we say so out loudBring one thing you changed. A single edited line in memory.md is enough to take the floor.
- Three minutes, hard stopNobody prepares a production. Open the file, show the thing, sit down — the format is what protects the person who almost didn’t share.
- “What I tried that didn’t work” is a real shareBring the dead end. It’s usually the most useful thing in the room, and it saves the person next to you from repeating it.
- Peers in the room, not gradersNo evaluative reporting line in the room — so you can show something half-finished without it following you into a review.
The ladder
Five stops, in order. Each one is something you do in front of people — and the last one is teaching it to someone else.
It grows sideways on its own
Start with your folder. When the person next to you keeps theirs the same way, the two line up — not because anyone built an integration, but because they’re the same shape. You write down how you work, someone else does the same, and the department ends up holding something it has never had: its actual process, in writing.
Nobody approves a rollout. Nobody waits for a platform. You can start today.
Where that leads is worth thinking about, and we will. Nothing about your first file depends on it.
The one thing to keep
There’s no wrong place to start and no wrong order to do it in. Start with the file that’s easiest for you, skip the ones that aren’t useful yet, come back later.
The file names and the headings stay the same. Everything inside them is yours.
That’s the entire portability story. Two folders built independently, months apart, line up because they’re the same shape. Keep the names and the headings, and anything you write is readable by anyone else who kept them too — no infrastructure, no platform, no plan agreed in advance.
Three ways in, same folder
Community Service
Free
- Timeframe
- 10 minutes, today
- What’s included
- Every gate, free to build yourself — Context Builder, Skills Builder, Actions Builder, Gate Console, and the Team Repo Starter are all real tools, no paywalls and I don't want your junk burner email.
- Outcome
- A complete Work Brain, built by you — plus Model Citizen's how-tos and community whenever you want a second opinion.
AI Coaching
$1,000/month
- Timeframe
- Weekly, ongoing
- What’s included
- A live 90-minute coaching session every week with a Work Brainiac — build, refine, and troubleshoot your Work Brain together, for as long as you keep coming.
- Outcome
- A standing weekly session, not a one-off — your process keeps getting sharper instead of stalling out after week one.
Fractional CTO
$2,500/month
- Timeframe
- Weekly, ongoing
- What’s included
- A live 90-minute session every week with you, plus the same AI Coaching extended to your whole team — Work Brain built into how your org actually runs.
- Outcome
- A team running on Work Brain, with a standing weekly seat at the table for whoever's steering it.
Work Brain™ by Model Citizen — Microsoft 365 edition. The framework, the instruments, and the method are Model Citizen’s. Everything you write in your own folder is yours. See what a guided build includes →