Dump it in. It gets filed.
Sorting is the system's job, not yours. Every afternoon a scheduled task reads the map, files what it is sure about, and asks about the rest rather than guessing.
AI Impact HubAI Impact HubFor anyone tired of re-introducing themselves to a chat window every morning.
Try it right here ↓Free to read. The try-it part runs on a free account.
Chat is what happens in one conversation. A second brain is the system that remembers how you work: plain files and folders on your own computer that any AI can be pointed at: your context, your projects, your knowledge, compounding over time and owned by you rather than by whichever tool you happen to be renting this year.
As the models get more powerful and everyone gets access to the same ones, what is left that is yours is the context you can give them. The game becomes building the system that lets any AI reach it in the most effective way possible.
The build feels backwards. Everything has spent a decade moving into the cloud, and this asks you to make files and folders on your own computer. That is precisely the point: plain files are the one format every AI can read, so your context walks from tool to tool untouched.
The working heart of it is an inbox folder you dump everything into: a report you found, a meeting transcript, a page you saved. A scheduled task sweeps it every afternoon and files what it finds under rules you approved, flagging anything it is unsure about.
Sorting is the system's job, not yours. Every afternoon a scheduled task reads the map, files what it is sure about, and asks about the rest rather than guessing.
A tool's memory knows you inside that tool. Plain files on your own computer still work with whatever you are using next year.
The first folder worth building, then the two habits that keep the rest of it honest.
The files a second brain starts with, and the prompt that drafts them from what your AI already knows about you.
These are the files worth making first. Start with three; the rest can wait until you miss them.
The bootstrap prompt: first draft from what it already knows
Using the memory and chat history available to you, draft my personal context files: who I am, my role, how I communicate, my goals, and my current projects. Write them one file at a time, in plain markdown. Do not invent anything: where you are not sure, ask me instead.
The afternoon sweep and the weekly audit. Run them by hand first, then schedule them once you trust the rules.
Both assume 000-START-HERE.md exists and holds your filing rules. That file is what makes them safe to schedule.
Inspect the 1-inbox folder. Read 000-START-HERE.md first and use its filing rules to decide where each item belongs. Move only what you are confident about, rename files to match the convention, and leave anything you are unsure about where it is with a one line note saying why. Then tell me what you moved and what you left.
The one that keeps the inbox from becoming another pile. Daily, or whenever it fills.
The guide is free to read. This part is a working exercise, and a free account opens it and keeps your progress across the Hub.
The personal context portfolio inside this (identity, role, projects, relationships, tools, one page each) came from the AI Daily Brief podcast.
Paste the link into Teams, Slack or LinkedIn and this card appears. Or send it from here.