Reading your console…
This brief is built from your own console every time you open it, so it never says more than it knows. Once the BlakeOS line is live the same brief lands as a text at 7:00 every morning and this screen is the receipt.
Not answering yet. The chat engine is the next piece to land, and it comes alive on top of what you already see on these screens: your brain, your rules, your list, your pipeline. Nothing typed here is saved until it does.
Today, in one place.
Your brief, what is on today, your own list, and anything sitting on your OK. If nothing is here, nothing needs you.
Your reminders and anything on today’s list, read live. Your phone calendar is still your calendar: this never guesses at it, and asking BlakeOS for your availability arrives with the chat engine.
One list. Only what is yours.
Everything from your shared note, your texts to BlakeOS, and the desks lands here sorted by whose move it is. You see your lane. Madi runs hers. The rest gets handled and shows up as receipts.
Nothing open in your lane. Add one above, or text BlakeOS and it files itself here.
Tap the circle to check one off. Tap the task to open it: notes, links, whatever belongs with it. Drag between Today, This week and Later.
Her lane, her checkmarks. You only see it, nothing here pings you.
Receipts, not asks. Every one shows the rule it used.
Reminders save to your BlakeOS database the second you set them. They arrive as a text once the BlakeOS line is live, and they sit here waiting until then.
Real math off your own check marks, not vibes. Weeks reset Monday. Streaks count the weeks and months you actually hit the goal.
Weeks reset Monday morning. Month-to-date rolls up from the days you tap. Hover a habit to remove it, no guilt, no history lecture.
Everything you teach.
One shelf.
Wins, frameworks, quotes, keynote ideas, research, and the brain underneath all of it. One brain, shared with the keynote builder: whatever lands here is what the builder pulls from.
Wins
Member results, in their words. Cleared ones are stage-ready, and the keynote builder pulls from this same shelf.
Frameworks
Every framework the brain has pulled out of the Scaling.com corpus so far, grouped the way you teach them. Tap one to open the steps.
Comes alive when the engine key lands. It will take a raw idea, check it against what you already teach so you are not rebuilding something you own, and shape it into a named framework with steps and a one liner. The shelf below is what it will build on. Nothing here generates anything yet.
Saved to your own database the second you hit teach. Every style you add is a shape the generator can build in once it is live.
Quote book
Your lines, filed by category. The keynote builder reads the same shelf, so a quote you add here is on a slide the next time you build one.
Comes alive when the engine key lands. It will draft new lines from a talk, a transcript or a theme, in your cadence, and hold them here until you keep or kill each one. Not generating yet.
Keynote ideas
Name a notebook, throw entries in, date them, find them forever. Everything here feeds the same brain the keynote builder pulls from. Except the locked ones. Those load for you and nobody else, not even Madi.
Keynote ideas
Locked to your sign-in. This notebook only loads for you. Madi and the team never see it, and nothing in it flows into the brain.
Research studies
The studies behind the science, sitting next to the frameworks that use them.
No research studies connected. A source-backed study will appear here after it is filed. Until then this shelf stays honestly empty.
Blake’s brain
Drawn live from the brain: every memo, episode, talk, deck and corpus document that has landed so far, grouped by where it came from. If it is on the map it is searchable, and if something is missing you can see the hole.
The ingestion worker is the one door into the brain, and it is what reads, chunks and files everything on this map. This box is not wired to it yet, so nothing typed here is saved. Until it is, the fastest way in is the share sheet on your phone, which is already running.
Three columns.
Every booking to paid.
Not signed, signed and not paid, closed. Drag a lead across as it moves, tick travel and books as they happen, and the year to date figure counts itself off the closed column.
counted live off the closed column
nothing in the column yet
nothing in the column yet
Saves straight to your own database. Madi can load the current pipeline here today, and it starts filling itself the moment the speaking form and email connect.
The pipeline is empty. Madi can load the current pipeline here today, and it fills itself when the speaking form and email connect.
Drag a lead between columns, or tap it to open the detail and move it there. Travel and books save the second you tick them.
One place for every conversation.
Four channels, one triage. Nothing here is reading your messages yet, and this screen will never show you a count it did not actually count. Each card says exactly what turns it on.
Goes live when the Meta app connects. Every DM triaged on arrival: speaking asks routed into the pipeline, real people surfaced, the rest filtered by your rules. Drafts come back in your voice for a yes or a no.
Goes live when the Mac mini connects. It reads the threads you are already in, answers what your rules already cover, and brings you only what needs a call. It never sends anything you have not approved.
Goes live when Google connects. All three inboxes in one triage. Fee shoppers get the standard note, serious asks get a date check and land in the pipeline, and anything that needs you comes with a draft already written.
Goes live when Slack connects. Logistics and scheduling answered in your channels, in your words, with the rule shown on every reply. The wins channel gets its own pipeline into the library.
Unified triage, drafts in your voice, filtered by your rules. Every channel above is one sign-in, and every one of them writes nothing without your OK. Until they connect, this screen stays honestly empty rather than showing you a number it invented.
Plugged into your tools.
Not a copy of them.
Your own connect list, every item on it, with where each one actually stands today. One sign-in each, read-only wherever the tool allows it. Unplug anything and it goes dark to BlakeOS instantly. Madi runs this page, you never have to.
Running today, proven end to end. Share any note to BlakeOS, or let the nightly sync pull your five most recent. Checked items read as done, and the travel-gigs note lands here too.
The receiver and fee rules are built. The form is not feeding it yet, so this source stays marked off until the GHL step points submissions at the receiver.
Recordings already imported remain searchable in the brain. There is no live Avoma pull yet, so new calls do not file themselves.
One Google grant covers every one of these. Drive folders flow into the brain, Slides and Docs open to the keynote builder, all three inboxes get triaged, and every date decision reads your calendar first.
A BlakeOS folder in your Drive. Anything dropped in it gets read, chunked and filed into the brain on its own. A PDF, a deck, a scan, an export from a tool that has no API: if it will not connect directly, it goes in the folder and it is searchable the same day.
When connected, recorded calls can feed the brain. No Zoom recordings are being read today.
Texts read on a machine you own, not in the cloud. It waits on the Mac mini, and it is what makes “Madi texted me it is done” check itself off your list.
Reads alongside Google so every date decision checks both. The family calendar always wins. That is a rule, and it gets enforced here.
Speaking asks routed into the pipeline, real people surfaced, the rest filtered by your rules. Drafts come back in your voice.
Logistics and scheduling answered in your channels, in your words, with the rule shown on every reply. Your back catalogue starts indexing the moment you tap.
Every keynote, call and drive-home thought transcribed and filed into the brain the day it happens. It connects while you set the device up, so there is no second step.
The BD pipeline, contracts and boards. Status questions get answered off the board instead of out of your memory, and nothing you assign gets lost.
Once it is on, every “this costs this much, okay?” arrives pre-checked against your spend line with the receipt already filed. Parked until the key comes across.
These three sit behind a deliberate gate. Photos are family, and bank and payment access is a different level of trust than reading a calendar. Nothing gets connected here until you and Brody have talked through exactly what it reads and what it can never do.
Per your instruction: a single pass to learn how you write and who everyone is, then nothing. This is never a live plug-in, it never stays connected, and it never gets triaged.
Everything retrievable by meaning, the same layer the keynote builder pulls from. In already: your rule memos, your own podcast, every guest spot, the TEDx, and the Scaling.com corpus.
OpenAI. Makes the judgment calls, writes the drafts, and cites the rule every time once the operator is connected.
ManagedTurns everything ingested into the brain you can search by meaning.
ManagedEverything on your requested list is here, including the sources that need hardware or a conversation before anything connects. Each status above is the current state. Connected sources feed one shared brain used by this console and the keynote builder. Anything that cannot connect directly can use the Drive drop folder after Google is connected.
Connected is not the
same as reading.
Signing in to a tool gives BlakeOS permission. It does not start pulling anything. Every source stays paused until it is turned on by name, so nothing is read, indexed, or billed before someone has looked at exactly what it would pull. This page is that switchboard, and it reports the real state, not the intended one.
Reading the gate…
Loading sources…
Turning a source on is a deliberate step taken outside the browser, on purpose. Before a first pull, BlakeOS shows what it found, how much of it there is, and what indexing it would cost, and waits for an explicit start. Nothing here can begin a pull by being clicked.
Every decision shows its rule.
Every rule is yours to change.
Loading active rules, loaded from your own voice memos on Aug 26. Your words, your numbers, read straight from your rule set every time you open this screen. Nothing here is a black box.
Nothing typed here is saved until rule writing is connected.
Replay from March. Madi asked: “The AV vendor for the Denver keynote came in at $2,800, okay to book?” You said yes, four minutes later.
Should that have needed you at all?
- Reply to any BlakeOS text. Plain words. “Too many of these” or “wrong call” is enough, it files the lesson.
- Edit a draft before approving it. Every correction becomes part of your voice going forward.
- Override any decision. The rule that fired sharpens itself, visibly, right here.
- Tap fix on anything it handled. Say what was off. The lesson attaches to that rule.
If it ever works differently than you want, saying so IS the fix. Nothing needs a settings menu.