Episode 10: The Current Crew
CuteMarkets Team
Research

Scope
This episode summarizes the current state of the portfolio journey using:
PAPER_BOTS.mdroadmap.jsonbaseline_summary.jsonRUNS.md
It is the state-of-the-journey episode, not a victory lap.
Result Snapshot
Current practical picture:
| Sleeve | Current status | Why it matters |
|---|---|---|
c66 | lead_paper_bot | strongest current deployable evidence |
c36 | backup_candidate / open_paper_only | profitable but sparse backup |
c4 | roadmap says next_candidate, recent runs say park_c4 | useful branch, currently not admission-ready |
QQQ dispersion | research_only | strongest research-only sleeve, sample still thin |
| Broad ORB | no longer the main expansion path | important negative result from the last two months |
That is not a finished portfolio. But it is a much clearer map than the repo had two months earlier.
Crew Map
c66 is the anchor candidate because its logic is narrow and its evidence is the least fragile. It is a short-only opening-compression expansion model, expressed through slower 2-5 DTE options under calmer-day filters. In portfolio terms, it currently occupies the role of "first strategy that has earned operational respect."
c36 remains valuable because it represents a different market hypothesis. Instead of trading expansion out of a coil, it fades short-horizon VWAP residual extremes and tries to monetize the snapback through quote-aware single-leg options. Its bottleneck is not that the logic is incoherent. Its bottleneck is that the high-quality version remains too sparse, while the denser opportunity-biased version decays.
c4 matters because it is the repository's most instructive relative-value near-miss. It asks whether a breakout is more credible when the primary ticker is outperforming a beta-adjusted proxy rather than simply moving in isolation. That is a sophisticated and scientifically interesting framing. The reason it is currently parked is not conceptual weakness alone. It is that, after bug repair and density repair, the branch still did not clear the portfolio's overlap, feasibility, and parity standards.
The QQQ-only dispersion sleeve remains the most interesting research-only branch because it concentrates the strongest part of the c4-style logic into the symbol that actually carried the edge. It also demonstrates the value of dynamic overlay generation and data-path repair. At the same time, its thin sample is exactly why the repo has not promoted it. That tension is part of the public story, not an inconvenience to hide.
What We Know Now
The strongest conclusions from the repo are these:
- A believable simulator matters more than a flattering one.
- Broad ORB search under realistic constraints mostly did not survive.
c66is the first model with anchor-like qualities.c36andc4are useful because they show two different kinds of near-miss.QQQ-only dispersion is the most interesting unpromoted sleeve.- Negative results are saving more time than vague optimism would.
That is already a meaningful body of knowledge.
What The One Piece Analogy Actually Means Here
The wrong version of the analogy would be "we are about to discover the one perfect model."
The better version is:
- the One Piece is a working portfolio of models with believable Sharpe
- the crew matters more than a solo hero
- bad islands must be left behind quickly
- the map gets better every time a false lead is crossed off
In this repo, the treasure is not a single backtest screenshot. It is a small basket of low-overlap models that still makes sense after realism fixes, parity checks, and stress scenarios.
What Happens Next
If the repo stays disciplined, the next phase should not be "add thirty new ideas."
It should be:
- continue operating
c66under strict paper parity - decide whether
c36can gain density without losing quality - leave
c4parked unless new evidence truly reopens it - keep the
QQQdispersion sleeve in research until sample improves materially - evaluate everything in portfolio context, not just as standalone anecdotes
That is how the public story stays credible.
What We Will Publish
A build-in-public series based on this repo should repeatedly publish:
- exact result tables
- explicit gate failures
- what changed in the pipeline
- what was closed permanently
- what remains promising but unpromoted
The audience does not need us to act certain. It needs us to be legible.
Final Take
This repo has not found the One Piece of Sharpe yet.
What it has found is better than that kind of fantasy:
- a measurement system that is more honest than it was two months ago
- a smaller and more credible set of survivors
- a growing discipline around saying no
- the first outline of an actual portfolio
That is enough to keep building publicly with seriousness.
The journey is now specific. The next milestones are not abstract. The crew list is short. The standards are clearer. That is real progress.
That is also why the public series should remain scientific in tone. The real accomplishment of the last two months is not that the repo found certainty. It is that it reduced ambiguity. Some branches now have stronger causal stories and better evidence. Some branches have been killed with much more confidence than before. A few remain unresolved but legible. That is exactly the kind of state from which a real portfolio can eventually be built.
Product links
Build the workflow with CuteMarkets
This article is part of the broader CuteMarkets product and research stack. Use the landing pages below to move from the blog into the specific API workflow you want to evaluate.
Learn Options From Zero
Send newcomers to the beginner path for calls, puts, chains, Greeks, IV, and risk.
Options Data API
See the primary product page for real-time and historical options data.
Historical Options Data API
Inspect the historical contracts, quotes, trades, and aggregates workflow.
Options Chain API
Go straight to chain snapshots, expirations, and strike discovery.
Pricing
Review plans before you move from free evaluation into production usage.