What goes in this section
Every day the bot runs, it writes journal/YYYY-MM-DD.md to the GitLab repo.
That file is the bot’s “why” for every action it took. This page is a
re-rendering of the most recent journals, auto-built from the daily cron.
The bot updates 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-renders from the repo’s journal/ directory. When the bot’s
daily cron runs at 23:55 UTC, it commits the day’s journal file. This
site’s CI rebuilds on main push. The freshness banner at the top of the
page tells you whether that pipeline has actually been running.
As of the last published update (2026-07-07): no journal entries synced to this repo yet, no orders placed. First entries will appear when the bot’s paper trades land here.
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/. The journal will get loud when paper trades begin. Until then, this page mostly mirrorsmetrics.mdandbacktests.md.