🧠

BrainOS Audit

BrainOS and the overlapping bookkeeping systems. Enter hub password to continue.

That's not right. Try again.

🧠 Systems Audit

BrainOS and the Overlapping Bookkeeping Systems

Compiled July 4, 2026 · Why it went cold, what got rescued, and the decision to retire it down to one system

← Back to Hub
📌

The short version

Summary

BrainOS is the "second brain" folder at C:\Users\annet\BrainOS. It held ten memory files (a dashboard, promises, next actions, waiting-on, pending questions, decisions, and a few logs) that Charlie was supposed to read at the start of each session and surface open items from.

Two things turned out to be true. First, nothing in the automated startup actually reads BrainOS anymore, so it was running on a written rule that had quietly stopped being followed. Second, its files went cold in May and never came back. When we looked closely, BrainOS was one of three different systems all tracking the same handful of things, and it was the oldest copy.

The audit found only four items across all ten files that were genuinely unique and still open. All four are now preserved in the live system. So BrainOS is safe to retire, which is what we're doing.

🔁

The finding: three systems doing one job

Duplication

The same concepts (open questions, to-dos, a dashboard, decisions, session history) were being written into three separate places on their own schedules. The newest copy stayed current. The older two drifted.

What it tracks BrainOS (oldest) Desktop files + catchup indexes (middle) hot.md + active-blocks (live)
Open questions pending-questions.md (May 10) Pending-Questions.md (May 28) -
To-dos / next actions next-actions.md (May 18) Master-TODO.md (Jun 11) hot.md (Jul 3)
Dashboard dashboard.md (May 5) Portfolio-Dashboard.md (May 28) -
Decisions decisions.md (May 18) project decisions/ folders hot.md ratified block
Session history session-log.md (May 18) - project daily/ files (Stop hook)

How cold it got

Frozen since May

Ten of the eleven files were last touched between May 1 and May 22. Only relationship-priorities was touched in July, and that was a side effect of an unrelated cleanup. In other words, BrainOS was heavily used in early May, then effectively abandoned while the newer systems took over. It kept being backed up and re-read by rule, but nobody was actually writing to it.

🛟

What the audit rescued

4 unique items

Everything else was already carried forward, resolved, or empty. Four items were unique and still open. Here's where each one landed:

Item What it is Outcome
GSC reconsideration Submit a Search Console reconsideration request now that Bone Voyage has migrated, to clear the manual SEO penalty. Confirmed still needed. Moved to Master-TODO.
Bob's GBP categories Staged secondary categories on Bob's Rebuilding Google Business Profile. Support group and Mental Health Service done. Counselor next week, then Life coach. Moved to Master-TODO.
Iridium safety rail (D-012) Don't cancel the old Bone Voyage hosting until the new site is verified and the 404s are cleared. Still a live gate. Preserved in Master-TODO (see next card).
Menopause panel roster (D-017) The expert-panel composition decision (Thurlow out; Fadal, Malone, Wright in). Already implemented in experts.yaml and since grown to 16 lenses. Nothing to do.
🦴

The catch that made this worth doing

Bone Voyage / Iridium

Do not cancel Iridium yet

The new Bone Voyage site is genuinely live and its 404 handling tests clean. Old post URLs redirect correctly and penalty URLs are properly killed off. The site is in good shape.

The reason to wait is not the site. It's that the safety procedure the old decision required was never actually run: no cutover date was logged (so the 14-day safety clock never started), no final backup of the old server was taken, and the old server's leftover email and subdomain dependencies were never checked.

Cost of waiting a couple more weeks is roughly $25 to $50, which is cheap insurance against a live site going dark. Most of the remaining work is Charlie's to do; the only pieces needed from Annette are the Iridium login (for the final backup) and confirmation that Search Console is connected for Bone Voyage.

The decision

Retire to one system

Retire BrainOS. The _claude_memory folder gets moved to an archive folder (reversible, nothing deleted) and the repo gets one final push to GitHub as its permanent frozen backup.

What lives where now

  • hot.md + active-blocks + per-project status files stay as the one live layer. This is what the startup actually reads.
  • The memory folder (charlie-memory) stays live and keeps its daily GitHub backup. It's the facts-and-rules store, edited constantly.
  • Master-TODO holds the four rescued items at the top under a dated "Rescued from BrainOS" block.
  • BrainOS becomes a frozen archive. No more nightly push, no more re-reading it by rule.

Net effect: down from three overlapping bookkeeping systems to one live one, with nothing valuable lost.

Compiled July 4, 2026 · Private · ← Hub