bain.monster turns a private git repo of plain markdown into the interface you actually plan from. The AI's job is editorial: read everything, keep what matters, say what's next. User count: one, working as intended.
The mechanism is deliberately plain: git is the database, markdown is the schema, and four views render straight from the repo — journal, projects, decisions, inbox. Twice a day a cron condenses the week into a paragraph and a do-next list, and an Opus routine ranks the next moves through a quality gate. Around the core sits the operational exhaust: site analytics, service health, Claude Code usage down to the token. Your notes stay markdown in a repo you own; every capture and status flip lands as a plain git commit.
Those numbers are real, measured on the live instance — ESP32 boards on the desk, sites on strange TLDs, games with real players. Every project name below is invented; the brain itself stays private, behind GitHub OAuth with an allowlist of one.
The morning page: today's journal, the ranked suggestion up top, recent decisions underneath. 27 projects are active right now — too many to show at once, so it surfaces the fresh and the flagged. Captures still waiting for a home, the week's synthesis and every other project live on this page too.
the board parses a 40 KB feed on-device and misses its 90-second refresh window whenever the api is slow — the proxy returns 1.2 KB of pre-parsed rows
ship the shopping-list share link before the weekend cooks do
the share link is the most-captured ask — 4 of the last 10 captures mention it — and PR #23 has sat open five days with one review comment left
Claude, Cursor and the xAI API on one meter. Spend, how close each one is to its limit, and where the cycle lands. Last 30 days: a $200/month Claude plan did $10,931 of pay-as-you-go work.
15 custom-domain sites on one ledger: PostHog for the pageviews, an hourly probe for whether each one answers. Below it, the other things that can go down — databases, data freshness, external APIs, boards on the desk that stop reporting — so you find out before a visitor does.
Free-form questions over the entire brain — Claude searches the repo for the exact decisions and journals it needs, Gemini steps in as fallback, and every answer cites where it came from. The brain remembers why, so you don't have to.
Deliberate — you pinned partial refresh at 90 seconds on jul 1 because e-ink ghosting above that beat a stale minute, and full refresh only runs on the hour. The refresh window isn’t the bottleneck anyway: the board spends up to 4 seconds parsing the raw 40 KB feed.
The open plan is to move that parse behind the edge proxy (decision logged this morning) — after that, 30 seconds becomes feasible if you still want it.
One private repo, read through a 30-minute tagged cache that a push webhook busts within seconds. Crons synthesize into Neon; PostHog and Supabase carry the operational views. Writes go back to the repo as commits.