Before letting the system trade real paper money on Monday, we tore it apart looking for problems. Found 9. The scariest: the RSS scanner is effectively blind after its first run of the day, and the system could try to buy AND sell the same ETF simultaneously.
The RSS Cache Bug (Severity: High)
The RSS article cache deduplicates by title. Once we've seen an article, it's never counted again. First run: 211 articles, all new → detects military conflict spike. Second run: same articles still in feeds → "0 new" → no spike detected.
This means after the first scan of the day, the system is blind to developing stories. A war could escalate and we'd miss it because we already "saw" those articles.
The Signal Conflict Bug (Severity: High)
RSS says SHORT TLT (inflation fears) while GPR says LONG TLT (flight to safety). The strategy engine treats these as separate candidates. It could try to buy AND sell TLT in the same run.
Fix: after fusion, net opposing signals. If LONG TLT is 0.48 and SHORT TLT is 0.57, net is SHORT with confidence 0.09 — too low to trade. Skip both. Conflicting signals cancel each other out.
The Full List
1. RSS cache bug — blind after first daily scan [HIGH] 2. Signal conflicts — could buy AND sell same ETF [HIGH] 3. Clock check after signals — wastes 18 seconds [LOW] 4. GPR downloads 15K rows every 30 min [LOW] 5. Serial signal collection — could be parallel [MED] 6. Individual price lookups — could be batched [LOW] 7. Hardcoded price estimates go stale [MED] 8. ORALE data staleness not logged [LOW] 9. No limit orders for live trading [FUTURE]
Find the bugs before the bugs find your money.