SentientEdge

Research letters · 30 October 2026

Research letter, 30 October 2026

This week

Two papers this week find that doing less works better: adding a regime overlay and adding return forecasts both lost to the plainer version out of sample, net of costs. The one paper reporting added signal (LLM text for healthcare stock rankings) ran its own placebo. Text shuffled in time within each company predicts about as well as the real text, so most of the "signal" looks like a persistent company fingerprint. The other two items are about clocks and plumbing, not alpha. Everything here is from arXiv. NBER had nothing on topic, and SSRN wasn't searched directly.

1. Market Regime-Based Multi-Asset Portfolio Optimization Using Nested Clustered Optimization for Tactical Asset Allocation

Supriadi, Bambang Siswoyo · v1 20 Oct 2026, v4 29 Oct · arXiv:2610.27751 · code: github.com/obo-cloud/nco-regime-taa

The short version: regime conditioning makes a clustered portfolio worse, through turnover.

Method.

What they tested and found.

Limitations.

Evidence vs speculation.

What we will do with it. Our own regime classifier uses fixed thresholds with no hysteresis or minimum dwell, on signals standardized over a short window that itself mean-reverts. This paper's failure mode is label churn, and we have never measured ours. We will count label flips per year and median run length over the full regime history, then re-label the same history with one hysteresis variant (wider exit than entry, three consecutive sessions to switch) and score both by the forward 20-session SPY return spread between risk-on and risk-off labels. Hysteresis earns a shadow slot only if it cuts flips by at least 40% and keeps at least 80% of the original spread. If the original label's spread is itself indistinguishable from a block-bootstrap null, we stop tuning thresholds: the classifier has no edge for hysteresis to protect.

2. Simple Portfolios that Deliver Consistent Decent Returns

Oskar Edén Wallberg, Alexander Karolin · 27 Oct 2026 · arXiv:2610.36491 · code: github.com/AlexEmrik/consistent-decent-returns, risk model pip install covforge

Method.

What they tested and found.

Limitations.

Evidence vs speculation.

What we will do with it. It's the same lesson as our own August review of the production scorer: the forecast layer added nothing, and composition did the work. The useful thing to borrow is a simple, un-searched benchmark. We will add a weekly-rebalanced SPY/AGG/GLD equal-weight chain, fixed in advance, as a reference column in our 2008–2026 replay under the same cost model. If our momentum candidate's net Sharpe does not exceed it, we record that the candidate is not yet beating a no-forecast diversified allocation on a risk-adjusted basis. It is a benchmark, not a signal, so no kill is attached.

3. What Language Models Add to Healthcare-Equity Rankings, and What They Could Have Known

Haotong Fu, Xiyue Zhang, Jack Rose, Ding Sun, Erich Scheller, Eric Rose · 27 Oct 2026 · arXiv:2610.38056 · AI4F workshop, ICAIF '26 · no public code

Method.

What they tested and found.

Limitations.

Evidence vs speculation.

What we will do with it. Healthcare was the worst sleeve in our own recommendation record, which makes the within-name time-shuffle a useful placebo for our scorer. It asks whether ranking skill, where there is any, comes from timely changes or from a sticky per-name level. For each name and date we will replace the score with the same name's score from a random other date at least 60 sessions away, 200 times, and recompute the 20-day rank IC against SPY-excess returns, overall and within Healthcare. If the shuffled IC is at least 80% of the real one, we record that scorer skill is a per-name level effect, and any future scorer work must beat a name-mean baseline, not zero. If the real IC isn't distinguishable from zero in the first place, we stop: there is no skill to decompose.

4. When Does "Post-Call" Begin? An Availability Contract for Earnings-Call NLP Benchmarks

Xiaoyu Ma, Kelvin J. L. Koa, Yuncong Liu, Ke-Wei Huang · 15 Oct 2026 · arXiv:2610.21659 · ICAIF '26 · no repo found

(Posted 15 days before this letter, just outside the usual 14-day window. It's included because it bears directly on our earnings research.)

Method. The authors propose an "Availability Contract" that every event study should declare: the input boundary; evidence that the input was actually available; when the outcome window starts; and which claims that evidence supports. They hold the return endpoint fixed and vary only the start clock: previous close, the call-start bar, or the call-completion bar (reconstructed audio end plus 15 minutes).

What they tested and found.

Limitations.

Evidence vs speculation.

What we will do with it. Our post-earnings-drift study already declares an event clock: before-open versus after-close timing, unknown timing treated as after-close, and a strictly prior-session regime join. The paper's extra point is to report how sensitive the result is to that clock. We will re-run the headline with every event's entry pushed back one session, and separately with unknown-timing events dropped rather than coerced. If the headline drift shrinks by more than half under the one-session shift, the effect gets labelled first-session-concentrated and timing-fragile before any further work. If its sign flips in either variant, the conclusion is marked unresolved.

5. Where Backtests and Live Trading Part Ways: Six Defects from One Intraday System

Alex Vidovich, Zivana Zerjal · 15 Oct 2026 · arXiv:2610.21846 · also SSRN, DOI 10.2139/ssrn.7517378 · no code

Method. A defect report from a live intraday US equity system, built by replaying live days through the backtest and comparing the two. It is explicitly not a profitability claim.

What they found. None of the six defects showed up in summary statistics:

  1. Wrong data feed: a data request with no explicit feed parameter returned single-exchange IEX bars instead of consolidated SIP. One stock's 9:30 bar showed about 7,900 shares vs about 3.4M consolidated, roughly 0.2%.
  2. Dividend-adjusted history: live orders never see adjusted prices.
  3. Inputs missing from the replay: data the live system downloaded was never requested by the backtest, and missing values silently defaulted.
  4. Sizing over the account limit: a later size-increasing step skipped a cap. 20 of 61 simulated fills exceeded what the account could afford, and dollar estimates were about 18% too large.
  5. UTC timestamps read as New York time: a fixed 13:30 UTC key equals 9:30 ET only in summer, which affected 11 scans in winter.
  6. Settings not reaching the order path: flags that loaded but never reached the code that places orders.

The paper closes with a 10-point checklist: pin the feed and price basis, apply size caps after every sizing step, use exchange-time helpers tested across DST, make missing inputs loud, and test the order path's behavior rather than whether a flag loaded.

Limitations.

Evidence vs speculation.

What we will do with it. Two of the six map onto questions we can ask of our own pipeline: whether every price loader pins its data feed explicitly, and whether any rolling window mixes adjusted and unadjusted prices. We will audit both. Stored daily volume for a random sample of S&P names gets compared with a consolidated source, and we will count how many names in our breadth universe have a 200-session window on a mixed price basis. A median volume ratio under 0.9, or more than 5% of names on a mixed basis, means a rebuild before any further regime research. Below both thresholds, the audit closes as clean.

Promising experiments

  1. Within-name time-shuffle placebo on the scorer (item 3). It uses only existing score history, takes about an hour, and gives a sharp answer. It also tells future scorer work which null it has to beat.
  2. Feed and price-basis audit (item 5). It's cheap and comes first, because if breadth is on a mixed basis, every regime experiment inherits the error.
  3. Regime label churn and hysteresis (item 1). Run it only after the audit comes back clean. The kill criterion is set so that we don't tune thresholds on a classifier with no forward-return separation.

Watching / not yet credible

Updates

Nothing previously covered was materially revised.


This letter is drafted with AI research assistance and reviewed and signed by Bob Katz. It is research commentary, not investment advice. No result described here is a claim net of trading costs unless stated, and the experiments listed are planned tests of our own models, not findings.