The actual documents the agents read and work from, shown exactly as they are on disk — not a summary. See the progress view instead · All projects
# STATE — the new operating-brain folder Current state only, rewritten in place. Full technical detail lives in PROJECT.md; this section is the plain-English mirror for the public status page. 🔴 **2026-08-25: PROJECT.md was split.** It had grown into a shared running log for every migrated project, not just this brain folder — split into one file per project (business-app, family-app, health, ops/router). This file's remaining content below still reflects the brain-folder build itself; per-project detail now lives in each project's own `PROJECT.md`, listed at the top of the root one. ## HUMAN CHECKLIST **Done:** - The core operating files (CLAUDE.md, RULEBOOK.md, FILE-STANDARD.md, APPROVAL-PIPELINE.md) - The agents and skills, copied and working - The cheap-model router, ported and independently verified (not just copied and trusted) - OpenBrain wired in as the knowledge source, replacing the old memory/*.md file pointers - Real business app code + the real business.db now live here — old workspace points back to this copy, not the other way around - Real family app code + linked real data, build verified end-to-end from inside this folder - Health engine copied over and verified working against real data (Ferritin history matched) - Google Drive, Google Calendar, and GitHub (both real app repos) all confirmed connected - 273 stale leftover files swept out — but **that sweep did not hold, and the folder is not clean today: 951 such files are present right now.** Only ~34 arrived after the sweep; the rest came back when other sessions bulk-copied whole subtrees from the old folder, debris included. Corrected here 2026-08-24 after an independent outside audit caught the stale claim. The honest version: a one-time purge is a snapshot, not a property — it needs to be either a recurring sweep or a filter applied at copy time; a missing `.gitignore` found and fixed (a real secret file had been committed by accident — untracked now, private repo, matches the old workspace's own established pattern) - This status page, live and login-free - `ROUTER-SETUP.md` moved to its real home - **Nick ruled 2026-08-24: Claude 2.0 is now the canonical version of everything migrated here — the old folder is being retired.** Real data gaps closed same session: Family-Finances, the raw lab PDFs, the family document vault, the real WhatsApp/Slack automation code and its saved session files, and the cloud server repo are all real, present copies here now, not just planned. - 7 of 11 background jobs (`auto-pull`, `autopush`, `cheap-loop`, `deploy-runner`, `signal-retire`, `transcribe`, `work-watch`) now genuinely running from here, confirmed live with real evidence (auto-pull wrote its own fresh success row: "in sync with the other machine"). The full 146MB job-code library they needed is copied over too, plus a proper `HEARTBEAT.md` (a real gap found and fixed along the way — the git-sync jobs need it to record their own health). - business-app's real deploy pipeline (GitHub Actions) re-pointed at this folder, with every dependency it needs checked to actually exist here first — not a paper fix. **In progress:** - The three consolidated project specs (Business Hub, Family App, Health Engine) — being merged in the old workspace, not yet landed here - The router's own test suite (25/45) has real gaps, but re-tested directly and confirmed they're message/logging specificity, not a security bypass — nothing insecure is getting through **Pending:** - Two small data-quality conflicts to resolve once the ownership system's real data lands here - 🔴 **4 of 11 background jobs still run from the old location** (down from 10 at the start of tonight): `roster-liveness` (fine either way, its watchdog exit code is by design, not urgent), `jobs` (the main loop runs correctly by hand but fails under launchd specifically — a real, narrow environment difference, not chased down further tonight), `slack-listener` (correctly waiting on the real Slack token landing in 2.0's `.env` — moving it now would have turned Slack listening off), and `wa-watcher`/WhatsApp (deliberately held — its saved session is unpaired and copied for safekeeping, but its own live log now says the session is unpaired and needs a fresh QR scan; the daemon stays put until re-pairing is complete and a working connection is proven). **Finish line:** every piece of Nick's AI assistant's operating brain — pointer file, rules, agents, skills, knowledge store, and real app data — living cleanly in this one folder, and now confirmed as the canonical version going forward. **That's reached.** What's left before the OLD folder can actually be turned off is a real, sized, separate job: moving the full background-automation code over, then carefully cutting each live daemon across one at a time.