Episode 6: c66, The First Real Anchor

Read this article with Options Backtesting API, Backtesting Framework, Backtesting Data Quality Checklist, Backtesting Execution Realism, Quote-Aware Options Backtests, and Backtest to Paper Trading Parity Checklist.

Scope

This episode focuses on the compression lane that became the current portfolio leader:

• baseline_summary.json
• PAPER_BOTS.md
• roadmap.json
• RUNS.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: 76 in 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. 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 more than 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 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 cannot support a family-level victory claim. It supports a narrower statement: one compression descendant, with short-side 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.

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:

• c66 is the best current evidence of a deployable edge in the repo
• its value is stability under stress, more than 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.

Related workflow

For the Episode 6: c66, The First Real Anchor workflow, continue through Options Backtesting API, Backtesting Framework, Backtesting Execution Realism, Backtesting Data Quality Checklist, Quote-Aware Options Backtests, and Backtest to Paper Trading Parity Checklist.

How the terminology applies

For Episode 6: c66, The First Real Anchor, the backtesting workflow should treat Point-in-time contracts, Quote-aware fills, Reject reasons, Replay artifact, Cache key, and Signal timestamp as operational state rather than glossary decoration. That framing keeps the research claim causal: the strategy can only select instruments, prices, and labels that existed at the decision time.

A developer implementing this research idea should persist Look-ahead leakage, Walk-forward test, Slippage model, Same-bar fill, Promotion gate, and Options data API beside the result, instead of leaving those words in a term card. It also turns attractive performance into an auditable record where fills, skips, thresholds, and replay inputs can be challenged independently.

The review artifact for Episode 6: c66, The First Real Anchor becomes more useful when OPRA-originating data, OCC option symbol, Bid/ask spread, Midpoint, Quote/trade condition, and Quote vs trade semantics appear in the same body of evidence as the selected rows. When a result is promoted, these fields should appear in the run manifest, rather than a prose summary or final equity curve.

In production notes for this backtesting workflow, REST snapshot, WebSocket stream, Entitlement gate, Quote freshness, Timestamp semantics, and Pagination cursor define the checks that decide whether the workflow is reproducible. The result is a backtest that can be rerun, compared across threshold families, and rejected when the evidence is not strong enough.

For Episode 6: c66, The First Real Anchor, the practical acceptance test is simple: another developer should be able to read the body, identify the exact inputs, reproduce the request sequence, and explain the accepted and rejected rows without relying on the bottom terminology grid. If a phrase appears in the page vocabulary, it should correspond to a stored field, a validation check, a replay step, or an implementation decision in the backtesting workflow.

This is also the reason the article should not measure success only by the final chart, table, or headline metric. The better standard is whether the data path, timing model, entitlement state, and evidence trail survive review. When those pieces are written directly into the body, the terminology becomes part of the workflow readers can implement.