Posts tagged #safety
6 posts tagged 'safety'.
- Re-Investigating the Flip-Flop Alert - The Cause Was a Change in Stock Count, Not Band OscillationAn alert fired again because the trading system bought a stock and sold part of it right back the next round - a "flip-flop." The design had blamed price jitter at the rounding edge, but re-tallying two months of execution logs read-only showed the real cause was the number of target holdings growing, which shrinks each stock's target amount. Here is how I decided to keep observing instead of flipping the switch off.
- The Morning Round Misfired on a Late-Open Day - Gating It on the Real Open TimeOn a day the market opens an hour late, restarting a stopped schedule timer instantly fired its already-elapsed trigger, so the morning round sent orders into a closed market. Every order was rejected, and because that round had claimed the execution slot, the later rounds were blocked too. This is how I tracked it down and made the system read the actual open time from the calendar so a pre-open round holds itself back.
- The First Live Order Cancel - A Broker Rejection and an Order-Number Type MismatchThe path that cancels an unfilled sell order mid-session and re-plans fired on a real account for the first time, and the broker's cancel API rejected it over an order-number type mismatch — with the rejection reason missing from the log. This is how I tracked that down, normalized the order number to an integer, and made the rejection reason print — plus how an external AI advisory checked the safety brake that blocked every buy on a rebound morning.
- First Live Trading Day - Most of the Safety Machinery Never FiredThe first time I ran the live-order code on a real trading session, orders filled cleanly and none of the safety paths — margin retry, order cancellation — ever triggered. This is about how I decide to trust safety code that has never fired, and how I blocked a calendar edge case the code didn't know about (a special late-open exam day).
- Kill-Switch Postmortem - the Root Cause Was Still ThereYesterday I patched the symptom of a false kill-switch trip in a hurry. Today's postmortem found the root cause was still live and could have blocked Monday's real trading again.
- A False Kill-Switch Trip From a Missing Account TagAn information-only simulation tick shared the same kill-switch namespace as the live account, and a fake loss computed from an unrelated account's balance nearly froze Monday's live trading.