Episode 4: ORB After The Audit

Scope

This episode is anchored in orb_framework_audit_20260310.md.

The question was simple: after the March realism fixes, what actually remained of the ORB family?

Result Snapshot

The short answer is that broad ORB did not survive well. A narrow ORB pocket did.

The audit's strongest surviving pocket was:

• directional ORB
• 5-7DTE
• 5 minute opening range
• range stop
• reg_off
• breakout-open-inside-range disabled

What failed broadly:

• classic close-breakout matrix
• broad touch/open-any matrix
• 0DTE, 1DTE, and 2-3DTE broad lanes
• 10, 15, and 20 minute ORB as generic fixes

That is a sharp conclusion. It means the ORB engine was not worthless, but the broad frontier was.

Strategy Context

The audit is especially helpful because it describes what ORB means in this repository in code-faithful terms. The engine builds an opening range from the underlying's first regular-session minute bars, measures range width and early context, scans for a breakout or reversal setup after the range completes, and only then selects an option contract if the strategy is being monetized with options. Entries occur on the next bar after the signal, not on the signal bar itself. That structure matters because it means most of the model family is really an underlying-bar signal generator with an option-expression layer added later.

Once ORB is defined that way, the failure of broad ORB search becomes easier to interpret. The search space was not just testing direction. It was testing combinations of opening-range duration, stop geometry, breakout gating, DTE buckets, relative-volume filters, and context overlays. A family that broad will often generate apparent winners under permissive assumptions. After the March audit, the repo learned that only a narrow region of that space remained defensible.

What The Audit Clarified

The audit is useful because it separates framework and strategy questions.

Framework-side improvements were real:

• causal option fills improved
• base option costs were threaded more consistently into research windows
• parity was materially better than before

But the audit also says clearly that several ORB weaknesses are strategy-design problems, not framework bugs:

• default stop geometry is often unusually wide
• require_breakout_open_inside_range is a major trade suppressor
• mixed DTE lanes make interpretation muddy

That distinction matters. If you blame everything on the framework, you keep rerunning a weak idea. If you blame everything on the strategy, you miss real infrastructure flaws. This audit did the harder thing and tried to separate the two.

What Worked

What worked was narrowness.

The surviving ORB branch was not a broad family win. It was a constrained pocket with specific geometry and DTE assumptions. That is scientifically healthy. Robust strategy research often ends with a narrower thesis than the one it started with.

The audit also reported parity improvements:

• bar_open: 13/18 exact matches
• live_poll_c30_l10: 15/18 exact matches

That does not mean live and backtest were identical. It means the remaining differences were increasingly about timing and calibration, not about phantom setups or missing contracts.

What Did Not Work

What did not work was the hope that ORB could be saved by one more broad matrix.

The audit is almost an anti-hype document:

• framework not dead
• search space mostly weak or sparse
• surviving branch narrow and specific

That is the correct tone. If you publish ORB work honestly, this is what readers need to see: not just the one cluster that looked okay, but the larger space that failed.

Why This Week Matters

This is the episode where the project learned that "ORB" was too broad a noun.

There is no single ORB result in this repo worth discussing as if it generalizes across windows, DTE buckets, stops, and filters. There is a much smaller claim:

• under realistic constraints, one constrained ORB pocket still had life
• the broad family did not

That is still useful. In One Piece terms, the crew did not find the treasure island. It found one narrow current that did not sink the ship.

Public Build Takeaway

The lesson from Episode 4 is that narrowing is progress.

Publicly, the best framing is:

• broad ORB did not survive honest testing
• one constrained branch survived better than the rest
• this changed how the repo allocated research time

That is not a retreat. It is what disciplined exploration looks like.

It is also a useful correction to how ORB is usually discussed online. ORB is often treated as though it were a single strategy with minor parameter variations. The evidence here suggests the opposite. ORB is a strategy family whose members can have very different statistical behavior once one enforces causal entries, realistic option monetization, and explicit deployment gates.