← Blog/blog/safe-portfolio-relative-floor

The safe portfolio guarantee that still permits a 20% shortfall

A prediction can point up, point down, or deserve no directional bet at all. MohammadpourAzari, Zarei, and Fazli make those three possibilities explicit: Follow the prediction, Reverseit, or transfer the decision to a fully invested, low-turnover Safe portfolio.

The paper is unusually disciplined about what happened next. A sign chosen on 24 development stocks failed on a frozen, disjoint 82-stock universe. Flipping the sign after seeing that result also failed to beat equal weight. The adaptive controller is therefore a story about containing the cost of untrusted advice—not discovering alpha.

01

Make direction an action, not an assumption

The controller builds three implementable portfolios from the same market state. Safe ignores the prediction. Follow adds a centered long-short overlay in the prediction's direction. Reverse adds the opposite overlay. A probability vector says how much of the decision belongs to each action.

Matured rewards are log wealth relative to Safe, scaled into [−1, 1]. Because positions last five trading days, several cohorts overlap. A decision opened today cannot learn from an outcome that matures later today; the paper keeps those clocks separate.

02

Fixed-Share keeps a discarded sign recoverable

Ordinary exponential weighting can drive a losing action's probability so close to zero that a later polarity change is slow to repair. Fixed-Share first rewards the actions exponentially, then redistributes a fraction of probability uniformly. That leak is a recovery channel, not permission to trade.

Reverse probability, no shareReverse probability, 10% share
Core-computed toy polarity reversal. Follow earns +0.2 for 20 matured cohorts, then Reverse earns +0.2. Fixed-Share preserves enough Reverse mass to react sooner; this is illustrative seeded-free arithmetic, not a paper-reported return path.
03

Abstention means transferring mass to Safe

For each directional action, the implementation keeps the latest 50 matured rewards. After at least 25 observations, it accepts the action only if the sample mean minus 1.645 standard errors is positive. The paper calls this a nominal one-sided normal bound because overlapping cohorts make consecutive rewards dependent.

def gate_probabilities(raw, accept_follow, accept_reverse):
    follow = raw[1] if accept_follow else 0.0
    reverse = raw[2] if accept_reverse else 0.0
    safe = 1.0 - follow - reverse
    return [safe, follow, reverse]

The tested TypeScript function runs the chart calculations; Python and C++ are line-for-line translations. Rejected Follow or Reverse mass is moved to Safe. The learner underneath is unchanged, so later matured evidence can revive the action.

one-sided lower boundzero threshold
Core-computed lower bound for alternating illustrative rewards of 0.08 and 0.02. A positive bound is necessary but not sufficient: the paper's configured gate also waits for 25 matured observations.
A hand-verified illustrative probability vector passes through the same one-sided maps as the paper: Reverse is rejected, then the remaining Follow mass is common-scaled to available collateral. Percentages are core-computed.
04

The frozen result stays negative

CAGR is compound annual growth rate; Sharpe divides excess return by volatility; maximum drawdown is the deepest peak-to-trough loss; turnover measures how much portfolio weight is traded. On the frozen universe, the pre-specified Reverse strategies did not beat daily equal weight. The conservative anchor stayed close with much less turnover, but closeness is not alpha.

Frozen strategyCAGRSharpeMax DDAvg turn.Rel. EW
Daily Equal Weight14.38%0.813−38.58%1.070%0.00%
Safe OPMD13.95%0.811−37.28%0.077%−0.37%
Legacy Reverse13.88%0.803−38.03%0.965%−0.43%
Clean Reverse13.74%0.798−37.92%1.010%−0.55%
Paper-reported frozen 82-stock results at five basis points per unit turnover. Relative EW is annualized realized log growth versus daily equal weight.

On the 24-stock development universe, Safe matched equal weight's broad return profile while cutting average daily turnover from 1.383% to 0.104%—a core-computed reduction of 92.5%. Certified execution was identical to Safe because the directional lower bound never turned positive. The prediction layer was available, but never earned permission to trade.

05

Flipping the failed sign does not rescue the claim

After the frozen Reverse result failed, Follow was better under both stored targets. It still remained below equal weight. Selecting the better sign from the same holdout would turn diagnosis into post-hoc model selection, so the paper labels these rows exploratory and leaves the confirmatory verdict untouched.

Diagnostic signCAGRSharpeAvg turn.Rel. EW
Legacy Follow14.04%0.8100.989%−0.30%
Legacy Reverse13.88%0.8030.965%−0.43%
Clean Follow14.16%0.8141.057%−0.19%
Clean Reverse13.74%0.7981.010%−0.55%
Paper-reported post-holdout fixed-orientation diagnostics. Follow improves on Reverse, but all four remain below equal weight; none is confirmatory alpha evidence.
06

What to probe next

First, replace the nominal normal gate with a dependence-aware bound or a block-bootstrap gate and report how much active mass changes. The current rule uses overlapping five-day rewards, so “1.645 standard errors” is a configuration choice rather than a finite-sample coverage certificate.

Next, move the frozen test forward in time as well as across stocks, stress nonlinear transaction costs and liquidity capacity, and compare the signed controller with a simple probability model whose calibration can be inspected on the logistic regressionpage. A safer wrapper cannot manufacture a forecast edge; it can only ration how much damage a missing edge is allowed to cause.

References

  1. MohammadpourAzari, A., Zarei, M., and Fazli, M. (2026). Safe Portfolio Learning from Untrusted Predictions: Signed Trust, Abstention, and Cross-Universe Polarity Failure. arXiv
  2. Herbster, M. and Warmuth, M. K. (1998). Tracking the Best Expert. Machine Learning 32
  3. Bailey, D. H. et al. (2016). The Probability of Backtest Overfitting. Journal of Computational Finance 20(4)