What goes in this section
Every day the bot ran, it wrote journal/YYYY-MM-DD.md to the GitLab repo.
That file is the bot’s “why” for every action it took. This page was a
re-rendering of the most recent journals, auto-built from the daily cron
while the bot ran.
The bot updated the journal files itself — every signal, every order, every gate-firing, every kill-switch state change.
How to read a journal entry
A journal entry has four event types:
| icon | type | when |
|---|---|---|
| 🔔 | signal | strategy produced a trade idea (BEFORE the order was attempted) |
| 📤 | order | an order was placed, refused, filled, partial, or cancelled |
| 🛑 | safety | a gate fired and either refused an order or auto-flattened |
| 📌 | note | free-form observation: regime change, config tweak, etc. |
Reading the journal backwards: the most recent entries are at the bottom of each day’s file. Each entry has a UTC timestamp.
What’s in journal/ (as of the last sync, 2026-07-07)
This page re-rendered from the repo’s journal/ directory. When the bot’s
daily cron ran at 23:55 UTC, it committed the day’s journal file and this
site’s CI rebuilt on main push. The freshness banner at the top of the
page tells you that pipeline is no longer running.
As of the last published update (2026-07-07): no journal entries synced to this repo, no orders placed. No further entries will be published — the bot and Herman have since been retired.
NOTE TO READERS: as of 2026-07-07 the bot was in research phase — no paper orders placed. The first strategy shipped,
mean_reversion_v1, failed its 30-day backtest; the later rounds (throughregime_mom_v2) are logged in/backtests/. Paper trades never began before the bot was retired, so this page mostly mirrorsmetrics.mdandbacktests.md.