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.
Answers from your own material, with every source named. Telling it to go do something lands with the chat engine.
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. Kate 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, keynotes, ideas, research and images, with the brain underneath all of it. The keynote builder reads this same library, so whatever lands here is what the builder pulls from.
Wins
Member results from the wins channel. Each one leads with the member, their company and the strategist who posted it, with the lines worth putting on a slide in bold. 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.
It checks the idea against the frameworks you already teach and uses the styles you taught it. Drafts only. Nothing is filed until you tap Keep.
Saved to your own database the second you hit teach. Every style you add is a shape the framework generator builds in.
Quotes
Lines worth keeping, yours and the ones you quote, filed by topic. Flip between what you said and what others said. The keynote builder reads the same shelf, so a quote you add here is on a slide the next time you build one.
Written off the lines already in your book, so they sound like you. Drafts only. A line you keep is filed as drafted by BlakeOS, never as something you said.
Keynotes
The talks and decks already in the brain: the decks Madi collected and everything in your Keynote Content folder on Drive. Drop a deck into that folder and it lands here on the next read.
Ideas
Your notebooks. Name one, 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 Kate.
Ideas
Locked to your sign-in. This notebook only loads for you. Kate and the team never see it, and nothing in it flows into the brain.
Research
Scaling.com’s own research next to the studies BlakeOS finds for you. Every paper links back to its source, and every summary says it is BlakeOS reading the abstract, never the paper’s own words.
Steer it
Reading the shelf…
Images
Every image made for a deck, here or in the keynote builder, newest first. They stay private to you: each link works for an hour and then quietly expires.
Blake’s brain
Drawn live from the brain: every memo, episode, talk, deck and corpus document that has landed, clustered around where it came from, and linked to the people, companies, topics and frameworks it is about. Tap any dot to see what it is. 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, once the shortcut is installed.
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. Kate can load the current pipeline here today, and it starts filling itself the moment the speaking form and email connect.
The pipeline is empty. Kate 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. Some of these are already connected for other jobs, but nothing here triages your messages yet, and this screen will never show you a count it did not actually count. Each card says exactly where it stands.
Brody sent a tester invite to @theblakeerickson. Accept it on your phone in Instagram, under Apps and websites, then Tester invites. Reading your DMs is not built yet. Once it is, every DM is triaged on arrival: speaking asks routed into the pipeline, real people surfaced, the rest filtered by your rules.
The Mac mini has arrived. It reads your texts once it is set up with your Apple ID and Messages in iCloud turned on. Then it can check off a task the moment Kate texts that it is done, and bring you only what needs a call. It never sends anything you have not approved.
Google is connected for blake@scaling.com and is read every hour for the brain. Inbox triage is the next piece and is not built yet. It needs one session with you on what becomes an action, what gets flagged, and what gets ignored. Your other two inboxes are not connected.
Slack is connected and the wins channel is read every hour, which is where the Wins shelf in your Library comes from. Answering logistics in your channels, in your words, is not built yet.
Unified triage, drafts in your voice, filtered by your rules. None of it writes anything without your OK. Until triage is built, 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. Kate runs this page, you never have to.
Built, and the share sheet is proven end to end on Brody’s phone. It is not running on yours until you install it, so it is not called live here. Once it is on: share any note to BlakeOS and it files instantly, and at 9 each night your five most recent notes come across on their own. Checked items read as done, and the travel-gigs note lands here too.
Install it, about three minutes
- Add the two shortcuts. Brody texts you Send to BlakeOS and BlakeOS Notes Sync. Tap each file, then Add Shortcut.
- Try the share sheet. Open any note, tap Share, choose Send to BlakeOS. You should get back “Got it. Filed to the brain.”
- Turn on the nightly run. Shortcuts app, Automation tab, +, Time of Day, 9:00 PM daily, Run Immediately, then pick BlakeOS Notes Sync and Done.
Step three is the one that cannot be sent as a file. Apple only lets an automation be built on the phone itself, which is why it is on your list and not Brody’s. Tell him when it is done and this card goes live.
The receiver and your fee rules are built and running. An inquiry that reaches it lands on the speaking desk qualified against your floor, with a draft reply waiting. Nothing reaches it today, because the form still posts nowhere.
The ask, one step, once. Whoever runs your GoHighLevel points the speaking form at blakeos-ingest.dreambigfast.workers.dev/webhook/ghl as a webhook. If it is easier, add brody@dreambigfast.com to the GoHighLevel account and he wires it in ten minutes.
Checking the key…
Checking the connection…
Checking the connection…
The ask. Avoma connects with an API key, not a sign-in, so there is no button to tap. Whoever administers your Avoma account creates a key under Settings, then API, and pastes it here with Replace key. After that you pick which calls it may read.
Checking the connection…
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.
Make the folder, about one minute
- Connect Google first. Use the Connect button on the Google card. The folder cannot be read before the account is.
- Make the folder. In Drive, New, then Folder, at the top level of My Drive. Name it BlakeOS. The name is how it gets found.
- Pick it. Open Sources and Sync, choose your Google source, tick the BlakeOS folder. Then anything you drop in gets read on the next pass.
Zoom cloud recordings can feed the brain the same way Avoma calls do. Nothing from Zoom is being read today. If Avoma already captures the calls that matter, skipping this is the right answer rather than wiring the same rooms twice.
Only if Avoma is not covering it. If it is not, your Zoom admin creates a Server-to-Server OAuth app in the Zoom admin console and sends Brody three values: the Account ID, the Client ID and the Client Secret. Nothing starts before you say it is worth the step.
Texts read on a machine you own, not in the cloud. It is what makes “Kate texted me it is done” check itself off your list.
The first five minutes are yours. The Mac mini arrived September 24. Plug it into a TV or monitor, sign in with the Apple ID your texts go to, and turn on Messages in iCloud. Brody does the rest and tells you when it is reading.
Reads alongside Google so every date decision checks both. The family calendar always wins. That is a rule, and it gets enforced here.
Same setup as iMessage. The Mac mini arrived September 24. One machine covers both, so it is one setup for you, not two, and Brody does the rest.
Speaking asks routed into the pipeline, real people surfaced, the rest filtered by your rules. Drafts come back in your voice. Nothing is being read from Instagram today.
What has to be true first, and who does it
- Business account, confirmed by you on Sept 7. Nothing to do here.
- It has to be connected to a Facebook Page. Same menu, then link the Page. Meta only allows DM access through a Page, so this one is not optional.
- Tell Brody it is done. He connects the Meta app from there. You never touch that part.
Checking the connection…
Checking the connection…
The BD pipeline, contracts and boards. Nothing is being read from Monday, and nothing will be. Your work still reaches you through the shared note with Kate and the morning brief, which is the path you actually use.
Not connecting it. Decided Sept 8. You named Monday on your connect list, and the call was made to leave it out rather than read a board you do not open. Nothing is needed from you. The card stays here so the reason is on the record and nobody quietly re-opens it, and if that ever changes it is a reader and a week.
You do not use WhatsApp, so nothing is being built for it. You told Brody on Sept 7. The card stays here so the reason is on the record rather than the connector quietly vanishing, and the moment that changes it is a phone number and a week.
Nothing is needed from you. If it ever does matter, the constraint is worth knowing: the business connection needs a phone number of its own, and a number registered that way can never be used in the normal WhatsApp app again.
Divvy is now BILL Spend and Expense, so this is one connection and not two. Once it is on, every “this costs this much, okay?” arrives pre-checked against your spend line with the receipt already filed.
Two things out of your BILL account. Whoever administers it sends Brody the organizationId, and creates a dedicated API user for BlakeOS rather than sharing a person’s login. Brody supplies the developer key himself. Not urgent, and it is one ask, not two.
Nothing in this category is on your list and nothing here is planned. It stays on the page as a standing rule rather than a queue: photos are family, and account access is a different level of trust than reading a calendar.
Nothing to do, and nothing pending. If one of these ever earns its place, you raise it, and it starts as a conversation with Brody about exactly what it would read and what it could never do. It never starts with a connect button.
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.
Your call, once. Say the word and Brody runs that single read, then closes it. Nothing to install, nothing stays connected, and it does not appear on this page again.
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, on your own key. Checking whether it is running…
ReadingTurns everything ingested into the brain you can search by meaning. Same key, same account, so there is one bill and it is yours.
ManagedEverything on your requested list is here. Each card either hands you the step or names exactly what is needed and who produces it, so nothing on this page is a status you can only look at. 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 once 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…
When a recording or a document names someone the brain does not know, it asks once instead of guessing. Answer here and every item that person appears in gets linked to them. Nothing is attributed to anyone until a person says so.
Reading the queue…
Some folders are yours alone. Nothing in them reaches anyone else unless you release it here.
Reading…
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 words on Aug 26 and 27. 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.
Nothing to replay yet. Replay starts once the desks have history to replay.
- 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.