HERMES
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.
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.
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.
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.
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.
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.
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.
| specs in repo | every system starts as a written spec I can argue with before a line is built |
| multi-agent builds | Claude agents build in parallel against those specs; I review, not babysit |
| preview-gated deploys | nothing reaches the live address until it passes on a preview URL first |
| the standard | the same rigor your financial plan gets |
The same person built the plan you'd walk away with.
← the second opinion← the second opinion