control-center
Summary: foogy’s personal automation — a file-based knowledge vault kept fresh by scheduled loops and mirrored to a dashboard as HTML. You feed and ask; the system remembers, cleans, and renders. Everything is plain files + git (no database), because the automation runs in a sandbox that can reach GitHub but not the Cloudflare API — see cloudflare-deploy.
The three parts
- control-center/ (
~/Documents/localhost/control-center) — automation home:.token(GitHub PAT),runs.log,desk/job-search/(daily leads),clients/(deliverables like insuladent). - brain/ — the vault (this knowledge base):
raw/(untouched ground truth) →entities/+concepts/→INDEX.md, plusCLAUDE.md(rules) andsynthesis/. Markdown, source of truth. Open in Obsidian. - dash-foogy — the Astro dashboard at dash.foogy.xyz (Cloudflare Pages, Git-connected). Renders every
.mddoc as HTML. Your readable view; behind Cloudflare Access. The vault is mirrored here under /p/brain and per-project.../knowledge.
The loops (scheduled tasks)
- After-session mining — daily ~21:07 (
daily-builder-log). Writes the day’s decisions/mistakes/patterns intobrain/raw/as dated notes. Only adds to raw/. - Compile + dash sync — nightly ~01:09 (
control-center-dispatcher). Phase 1: folds newraw/+ recent repo changes intoentities//concepts/, updates INDEX. Phase 2: runsdash-foogy/scripts/sync-brain.mjsto mirror the vault → dash as HTML, then pushes. - Weekly lint — Sun ~02:03 (
brain-weekly-lint). Dead[links](/p/brain/links), duplicate pages, contradictions, stale claims. - Weekly synthesis — Sun ~03:01 (
brain-weekly-synthesis). Reads the whole vault, writes a dated “week in review” tobrain/synthesis/. The one loop that sees everything. - Daily job scout — ~06:09 (
desk-job-search). Searches for matching roles (job-search-strategy), writes a dated shortlist todesk/job-search/and publishes it to the dash.
Data flow
foogy → me (I write vault markdown / deliverables) → loops compile + sync → dash HTML → foogy reads. Correct me and I fix the source; the loops re-render.
Constraints & lessons (why it’s built this way)
- The scheduled sandbox can run git to GitHub but cannot reach
api.cloudflare.com/ D1 — the D1-backed dash failed for exactly this reason (see cloudflare-deploy). So: keep state on plain files + git push. - The GitHub token (
control-center/.token, fine-grained) covers only mfugaj/foogy.dev + mfugaj/dash-foogy. Other-owner repos (depunks, agents4fun under damir5) are read from the local mounted copy, not cloned. - The local
foogy.devclone is stale/locked — loops must fetch origin for it (canonical = GitHub/live), see foogy-dev.
Focus & extending
Focus repos: depunks · agents4fun · foogy-dev. New project → foogy says “set up loops for X”; add its entity from brain/_templates/new-project.md and it’s in scope automatically.
Sources
- Scheduled tasks in
~/Documents/Claude/Scheduled/(daily-builder-log, control-center-dispatcher, brain-weekly-lint, brain-weekly-synthesis, desk-job-search). brain/CLAUDE.md,dash-foogy/scripts/sync-brain.mjs. Related: cloudflare-deploy, job-search-strategy.