Episode 6: c66, The First Real Anchor
CuteMarkets Team
Research

Scope
This episode focuses on the compression lane that became the current portfolio leader:
baseline_summary.jsonPAPER_BOTS.mdroadmap.jsonRUNS.md, especially the April 10, April 13, and April 18 paper-bot entries
Result Snapshot
The strongest baseline artifact in the repo is c66_opening_compression_option_native_short_balance_dte35_v1.
Recorded baseline summary:
- base OOS return:
0.19181584812500027 - stress-medium OOS return:
0.1669711988 - stress-harsh OOS return:
0.155609875 - OOS trades:
76in all three scenarios - gate decision:
promote - gate reason:
feasible_profile_selected
This is why c66 is first in the paper-bot order and explicitly marked lead_paper_bot.
Strategy Context
c66 is not an isolated invention. It is a modified descendant of the opening-compression family defined around c9_opening_compression_balance_v1. The base idea is to identify a short intraday coil after the open, quantified through a small rolling range over the last few bars, and then trade the first clean expansion out of that coil. The base compression profile already uses range stops, explicit take-profit and break-even logic, early-failure checks, relative-volume filters, and a bounded holding period. In other words, it is a structured post-open release model, not a vague "trade breakouts" heuristic.
c66 then makes several decisive changes to that family. It becomes short-only, pushes the option expression out to 2-5 DTE instead of same-day exposure, shortens the maximum hold, demands a slightly cleaner compression pattern, raises the minimum expansion-volume requirement, and adds calmer-day filters through volatility and prior-day range constraints. The profile therefore narrows both the market regime and the instrument choice. That narrowing is probably a large part of why it survives better than the broader compression relatives.
Why c66 Matters
The repo did not promote c66 because it had the biggest isolated PnL anecdote. It promoted c66 because it combined several things that rarely coexist:
- positive OOS result
- stable stress behavior
- meaningful trade count
- operational progress into paper-bot deployment
That combination makes c66 qualitatively different from many attractive research-only lanes. It is not just a positive branch. It is a branch that the repo was willing to operationalize.
What Worked
Two things stand out.
First, the slower DTE compression structure held up better than more speculative or more fragile variants. The repo repeatedly converged on the idea that the strongest compression expression was not the flashiest one.
More precisely, the lane appears to benefit from separating signal timing from gamma sensitivity. A short-only compression release can be directionally correct without needing the explosive convexity of 0DTE or 1DTE contracts. By moving to 2-5 DTE and keeping the signal logic narrow, the branch gives itself more room to survive imperfect intraday timing, while still preserving a tactical options expression. That is a scientifically stronger structure than a same-day lottery framing.
Second, c66 moved beyond research artifacts:
- strict-parity paper-bot validation on
server3 - in-session dry-run smoke
- first live paper deployment on April 13
- restart and cutover after the server reboot on April 18
That progression matters. Research results become much more informative once the branch has to survive operational reality.
What Did Not Work
The negative result around c66 is easy to miss because the branch itself looks strong. The repo also learned that not all compression-related ideas deserve to be grouped together.
For example, the shared feasibility calibration around c52_opening_compression_option_native_balance_v1 still ended infeasible:
- failed
pbo_ok - local failed check
dsr_ok
That is useful because it stops us from telling a lazy story like "compression works." The better story is:
- one specific slower-DTE short-balance compression lane currently works best
- adjacent compression variants often do not clear the same bar
That distinction should be kept explicit in the public series. The evidence does not justify a family-level victory claim. It justifies a narrower statement: one compression descendant, with short-only directional bias, calmer-day filters, and slower-DTE option expression, currently functions as the best anchor candidate in the repo.
Why This Week Matters
This is the first point in the repo where a strategy starts to look like a portfolio anchor rather than a promising experiment.
In One Piece language, c66 is not the treasure. It is the first ship that has earned the right to stay in the fleet.
That distinction matters because public trading research often celebrates every green branch the same way. This repo did not do that. It promoted one branch, kept others behind it, and wired kill-switch logic around the live path.
Public Build Takeaway
If this episode is published well, the audience should come away with a sober but meaningful conclusion:
c66is the best current evidence of a deployable edge in the repo- its value is stability under stress, not just a headline number
- it became important because it survived both research and operational gates
That is what a real anchor looks like in a build-in-public research process.
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.