← back to the notebook
appendix — the stack

The other half of my brain — I build my own tooling.

I'm a computer engineer first. The advisory practice runs on systems I designed and built myself — the same way I'd want a plan built: specified, inspectable, nothing you can't open up and check.

01 / hermes

HERMES

always-on home-server orchestrator

Runs on a machine at home that never sleeps. It schedules the research jobs, watches queues for work to pick up, and pings me on Telegram when something needs a human. The metronome the rest of the stack runs to.

UPTIME: ALWAYS-ONSCHEDULES: CRONSALERTS: TELEGRAM
02 / ai-radar

AI RADAR

intake → triage pipeline for the AI stack

Captures tools and articles worth a look, scores each one against how I actually work, and decides adopt or skip. It's why the tooling behind this practice stays current instead of accreting. Runs on Cloudflare with a real database behind it.

FLOW: CAPTURE → SCOREVERDICT: ADOPT/SKIPHOST: CLOUDFLARE + DB
03 / fa-command-center

FA COMMAND CENTER

self-built prospecting CRM

The system the advisory practice actually runs on — who I'm talking to, where each conversation stands, what happens next. Built it myself because the off-the-shelf options wanted me to work their way.

USE: LIVE DAILYBUILT BY: MEOFF-THE-SHELF: NO
04 / advisor-investment-algorithm

ADVISOR INVESTMENT ALGORITHM

python research engine

Reads fund and market news every day, drafts an advisor newsletter from what it finds, and publishes tokenised client briefs — a private, read-only page per client instead of a PDF in an inbox. Headless: no dashboard drama, just output.

CADENCE: DAILYOUTPUT: BRIEF + LETTERLANG: PYTHON
05 / this-site

THIS SITE

a Cloudflare Worker fronting everything

The front door — the landing, the tools you just used, and the routing that ties all of the above into one clean address. One small program at the edge, doing the traffic control.

EDGE: CLOUDFLARE WORKERSERVES: LANDING + TOOLSROUTING: ONE DOOR
how it gets built
specs in repoevery system starts as a written spec I can argue with before a line is built
multi-agent buildsClaude agents build in parallel against those specs; I review, not babysit
preview-gated deploysnothing reaches the live address until it passes on a preview URL first
the standardthe same rigor your financial plan gets

The same person built the plan you'd walk away with.

← the second opinion← the second opinion