Skip to content
← Projects

Own project · in use since October 2026

My agent-run second brain

The system I work with: I capture from my phone, agents file, propose and execute, and I approve and review.

Figures counted in the system’s own files on 27 Oct 2026.

The problem

A one-person consultancy has to capture, organise, decide and execute at the same time. What isn’t organised gets lost, and what isn’t reviewed can’t be delegated.

How it’s built

A Markdown vault in git is the memory. Notion is the task list. An orchestrator hands work to specialised agents, and a reviewer checks every result before it reaches me.

Second brain architectureCaptures(phone and laptop)Markdown vault+ gitCloud routinesMon–Fri and Sun 07:30/brainorchestratorFile(triage-clerk)Research(researcher)Code(builder)Reviewer(PASS or FIX)Notion: tasksInbox → Next → WaitingMe: approve and reviewLessons +weekly curator

What the agents do and what I decide

Process, from capture to reviewCodeAIPerson1I capture ideas, plans and tasks2File into the vault, with a source forevery fact3Propose tasks in Notion (Inbox)4Approve what an agent does5Execute: research, or code on a branch6Reviewer: check against the definitionof done7Review the result and decide8Log lessons; every week, proposeimprovements
Improvements the system proposes only apply if I accept them.

One real run

Phase 4 of the system itself, on 26 October 2026: the reviewer sent the work back once before it reached me.

Sequence diagram of a run on 26 Oct 2026Me/brainbuilderreviewerI approve phase 4task + definition of done+ relevant lessonsplaybook, reflection hook,weekly curatorresultFIX: list of fixesfixedbrief: done+ ≤ 3 decisions
Source: _system/logs/briefs/2026-10-26.md (16:20) and the git history.

Rules it follows on its own

  • Three autonomy levels: green (read, file, propose), amber (approved tasks only) and red (send, publish, spend, delete): for red it always asks me.
  • No agent approves itself: either I approve, or the task belongs to a class I agreed in writing, and the task is marked accordingly.
  • Private stays private: it lives in a folder outside git, and a check before every commit blocks lines marked private.
  • Every fact about me carries its source and a marker: said by me or inferred. Inferred facts are confirmed before use.
  • Every week it proposes changes to its own rules; they only apply if I accept them, and git keeps every version.

Stack: Claude Code: 5 skills, 5 subagents, 3 hooks · Markdown + git · Notion · Scheduled cloud routines

Why it matters to you

It’s the same pattern I build for a small business: AI prepares and executes, a person approves at the points that matter, and everything is logged and can be undone.

Tell me about a process that eats your time.

In 30 minutes we’ll see whether AI can help. No commitment.