Episode 5: From Frontier Search To Portfolio Thinking

Scope

This episode covers the strategic pivot that became explicit in early April.

The key evidence lives in:

• RUNS.md, especially the April 6 audit entries
• roadmap.json
• PAPER_BOTS.md

Result Snapshot

The decisive phrase from the repo is not a model name. It is the audit verdict:

• framework_sound_strategy_mismatch

And the recommended next action:

• move_to_new_strategy_ideation

That is the point where the project stopped treating the problem as "optimize ORB harder" and started treating it as "assemble a diversified set of strategies that actually survive the deployability bar."

The roadmap then made the portfolio goal explicit:

• build a small diversified paper-bot portfolio
• stop broad standalone ORB frontier search as the main path

Scientifically, this is a change in objective function. The project stopped optimizing for the best-looking isolated branch and started optimizing for a candidate set that could plausibly coexist under overlap, robustness, and deployability constraints. That is a much harder problem, but it is also a much more realistic one. A live portfolio does not care whether one backtest looked beautiful if that sleeve adds no diversification or fails under operational scrutiny.

Why The Pivot Happened

The repo had accumulated enough evidence by this point to justify a strategic change:

• March realism fixes made results harsher
• ORB audit narrowed what was still defensible
• complement branches were beginning to fail quickly
• the remaining interesting lanes did not all look like ORB

That creates a classic systematic trading choice:

• keep optimizing the incumbent family because it is familiar
• or switch from single-family frontier search to portfolio assembly

This repo chose the second path.

What Worked

What worked was the willingness to name the problem correctly.

The portfolio roadmap did not say "best ORB." It said:

• c66 lead paper bot
• c4 next candidate
• c36 backup candidate
• QQQ dispersion remains research-only

That is already a portfolio mindset. These models are not clones. They are being evaluated partly on their ability to coexist.

The distinction matters because the repo's later gates use overlap days, correlation context, sample density, quote realism, and operational parity as part of the promotion logic. Once those dimensions matter, a branch can be economically interesting and still not deserve a slot. The public series should keep returning to that point because it is central to the research philosophy the repository eventually converged on.

This is one of the strongest scientific signals in the repo because real trading systems do not get paid for having one beautiful backtest. They get paid for having a basket whose members are credible together.

What Did Not Work

What did not work was the implicit earlier hope that the project would discover one dominant ORB configuration and then merely scale it.

The audit and roadmap jointly reject that.

The practical negative result is:

• strategy families were failing under a legitimate deployment bar
• more sweeps inside the same family were no longer the highest-value use of time

That is a hard decision to make in research because it often feels like giving up on sunk effort. In fact, it is the opposite. It is refusing to protect sunk effort from evidence.

Why This Week Matters

This was the week the repo got a portfolio objective, not just a model objective.

In restrained One Piece language, this is where the journey stops being about the strongest fighter and starts being about the crew.

One strong but highly correlated or fragile strategy is not the One Piece of Sharpe. A low-overlap basket of believable models is much closer.

Public Build Takeaway

The public lesson from Episode 5 is worth stating directly:

• when the evidence says the family is mismatched to the bar, pivot
• define the portfolio before you define the victory speech
• treat negative model evidence as a budgeting signal

This repo did not just change direction. It changed the question. That is often the highest-leverage move in systematic research.