Journal

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:

icontypewhen
๐Ÿ””signalstrategy produced a trade idea (BEFORE the order was attempted)
๐Ÿ“คorderan order was placed, refused, filled, partial, or cancelled
๐Ÿ›‘safetya gate fired and either refused an order or auto-flattened
๐Ÿ“Œnotefree-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/ today

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.

For now (2026-07-06, day 1): no entries yet, no orders placed. First entries will appear when the bot starts paper-trading.

NOTE TO READERS: the bot is currently in research phase (no paper orders placed yet because the only strategy shipped to date, mean_reversion_v1, just failed its 30-day backtest). The journal will get loud when paper trades begin. Until then, this page will mostly mirror metrics.md and backtests.md.