Old question (Phase 4, falsified): “Was the trade in TREND_UP / EXPANSION_CONFIRMED at entry?” — Phase 4a showed it was not: PI→Trend winners clustered in ROTATION at entry, and the single biggest Pull-In loss (IBIT 6/3, −$216) entered in EXPANSION_CONFIRMED. The state label at one instant does not separate winners from losers.
New question (this plan): “Can VCET v1.1 + CBO identify the mechanism of the trade?” The conversion to trend happens after entry, so the signal is in the trajectory and the channel-break geometry, not the entry snapshot. The job of v1.1/CBO is to classify which of four mechanisms a trade actually was — so that management (not the go/no-go) can be matched to mechanism.
Primary filter stays the Quality Gate (RVOL + gap). VCET v1.1/CBO is tested here as a secondary confirmation / mechanism-labelling layer, never as the entry trigger. See §7.
Phase 4a (VCET Pull-In At-Entry Pilot) ran v1.0 at slope_trend_thresh=2.0 over the 55 trades with bars in the kti window. The original four hypotheses (converters live in expansion; leakers live in indecision) did not hold:
| Phase 4 expected | Phase 4a actual |
|---|---|
≥70% of PI→Trend wins in EARLY_EXPANSION / EXPANSION_CONFIRMED / TREND_* at entry | 5 of 9 PI→Trend wins entered in ROTATION; the two biggest (DAL +$68, +$22) both ROTATION_FLAT_BANDS |
| Plain-PI losses concentrate in indecision states | Every state bucket lost money; the −$216 IBIT loss was the lone EXPANSION_CONFIRMED row — an opposite-side break taken long |
| State label is the discriminator | State label is a lagging snapshot. The signal that survives is numeric geometry (slope sign, band width, score) and state change after entry |
t=0 structurally cannot see it. (Pilot §9.4 explicitly calls for testing state trajectory, not state-at-entry.)EXPANSION_CONFIRMED and might have caught the IBIT −$216 as a wrong-side trade.”The Mechanism Audit (v1.0 + hand-coded rules A/B/C/D) found the vwap-pull-in -> trend bucket is a MIXED bucket: 1 true conversion, 3 rotation scalps, 2 wrong-side escapes, plus a 4th mechanism the rule set could not model (3 trades that entered already TREND_*). These are the four classes v1.1/CBO must separate.
| Mechanism | State at entry | Post-entry trajectory | CBO signature (v1.1) | Reference trade | Management |
|---|---|---|---|---|---|
| true_pull_in_to_trend | ROTATION / COMPRESSION / EARLY_EXPANSION | Band width expands ≥1.5× in 5 min; slope accelerates ≥+5° in trade dir; expansion_score crosses ≥50; state → TREND_* within 15 min |
Break in trade direction, AFTER entry (offset +5..+15) | JOBY 5/28 +$12.45 | Trend-hold; trail wide; let the runner run |
| vwap_rotation_scalp | ROTATION (often ROTATION_FLAT_BANDS) |
Stays ROTATION through +25; |slope|<2°; band width flat (≤1.2×); expansion_score<50 throughout |
No break in any direction through +25 (price stays inside channel) | DAL 5/26 +$68.25 | Target the opposite band; take the rotation; don’t extend stops |
| wrong_side_escape | Any (often ROTATION or sticky TREND) | State / slope move AGAINST trade dir; profit is tiny size, fast scratch, or lucky bounce | Break OPPOSITE trade direction within +15 | JOBY 5/29 +$0.70 · IBIT 6/3 −$216 | “Do not let outcome validate the setup.” Exit / reduce fast |
| trend_continuation_entry 4th — new | Already TREND_* matching trade dir |
No fresh expansion; trend often decelerating; band width flat/established | Break in trade direction occurred BEFORE entry (t≤0); none fresh after |
LUNR 5/26 (−$11.76, the bucket’s only loser) · BB 5/28 · INTC 6/2 | Not a Pull-In at all; continuation rules — don’t expect a fresh leg |
| insufficient_data | No bars in kti window / engine error / session boundary / too few bars to form the CBO channel | — | No mechanism inferred | ||
In the audit, trend_continuation_entry fell into insufficient_data because v1.0 saw only “already TREND_UP at entry” with no way to date the break. Giving it a real label is the single clearest demonstration of CBO’s added value (§6, V-Q2).
CBO (Channel-Breakout Operator, Pardo Ch. 28) tracks whether price has broken its recent N-bar high/low channel, which way, and when. Per the v1.1 config it runs as a confirmation layer, not a hard gate: enable_cbo=true, require_cbo_for_expansion_confirmed=false. Those two facts turn the four mechanisms — which overlap badly on a single state label — into a clean decision surface.
| CBO break direction | CBO break timing vs entry | → Mechanism |
|---|---|---|
| Same as trade dir | AFTER entry (+5..+15) | true_pull_in_to_trend — the break IS the conversion; geometry confirms it |
| Same as trade dir | BEFORE entry (t≤0) | trend_continuation_entry — entered into an already-confirmed break |
| Opposite trade dir | Any (within +15) | wrong_side_escape — the channel broke against you (IBIT) |
| None | No break through +25 | vwap_rotation_scalp — price never left the channel |
This is why the reframe matters. Phase 4a tried to separate four mechanisms with one categorical field (state_at_entry) and they collapsed onto each other in ROTATION. Break-direction × break-timing is a two-axis surface; the four mechanisms occupy four distinct cells. State trajectory and band/slope geometry then confirm the cell rather than carry the whole decision.
Apply in priority order. The order is the audit’s C > A > B > D, with trend_continuation_entry inserted as a CBO-enabled class above the conversion test (a pre-entry break must be ruled out before a post-entry break can be called a conversion).
given trade with direction D in {LONG, SHORT}, entry t0,
snaps at offsets {-5, 0, +5, +10, +15, +25} min,
CBO fields per bar: cbo_break_dir in {NONE, UP, DOWN}, cbo_channel_pos
# 1. wrong_side_escape (safety first)
if cbo_break_dir opposite D within +15
OR state -> TREND_* opposite D within +15
OR slope accelerates >=15 deg against D within +5:
-> wrong_side_escape
(HIGH if CBO opposite-break confirmed; MED if only slope/state)
# 2. trend_continuation_entry (NEW - requires CBO timing)
elif cbo_break_dir == D at some offset t <= 0 # break predates entry
AND state already TREND_D at entry
AND no fresh expansion after entry (bw not >=1.5x; expansion_score stays < 50):
-> trend_continuation_entry
(HIGH if pre-entry break + already TREND + decelerating slope)
# 3. true_pull_in_to_trend (conversion)
elif entry state in {ROTATION, COMPRESSION, EARLY_EXPANSION}
AND cbo_break_dir == D first confirmed in +5..+15 # fresh break after entry
AND band_width(+5) >= band_width(0) * 1.5
AND slope(+5) - slope(0) >= +5 deg (D-signed)
AND expansion_score crosses >= 50
AND state transitions toward EXPANSION_CONFIRMED / TREND_D within 15 min:
-> true_pull_in_to_trend
(HIGH if CBO break + >=3 of 4 geometry sub-checks align)
# 4. vwap_rotation_scalp
elif cbo_break_dir == NONE through +25
AND state stays ROTATION at +15 and +25
AND |slope| < 2 deg at 0,+5,+10,+15
AND band_width(+25) <= band_width(0) * 1.2
AND expansion_score < 50 at all snaps:
-> vwap_rotation_scalp
(HIGH if all hold cleanly)
# 5. insufficient_data
else: -> insufficient_data # no bars / engine error / session boundary / channel not formed
| Class | v1.0 rule (audit) | What CBO adds in v1.1 |
|---|---|---|
| wrong_side_escape | Slope accel ≥15° opposite, or opposite-dir TREND within 15 min | A crisp binary — the channel broke the other way — catches IBIT-type losses earlier and cleaner than waiting for a 15° slope swing |
| trend_continuation_entry | None — dumped into insufficient_data | Pre-entry break timing makes it classifiable for the first time; pulls LUNR/BB/INTC out of the unknown bucket |
| true_pull_in_to_trend | ≥3 of 5 fuzzy geometry sub-checks | The CBO break-in-direction becomes the spine; geometry confirms rather than carries. Pins the conversion instant |
| vwap_rotation_scalp | Infer rotation from flat slope + flat bands | “CBO never fired” is a positive signal for rotation, not an inference from absence |
| Element | Specification |
|---|---|
| Population | All canonical_strategy_slug = 'vwap-pull-in -> trend' (n=15) as the target; plain vwap-pull-in (n=127) and chase-extended (n=56) as contrast / control. Read-only on main.trade_context. Same population as Phase 4a. |
| Bars | kti five_min, 14-day window. NO_BAR risk is the headline limitation — in the audit 6 of 15 PI→Trend trades (64% of the bucket’s $) predate the window and cannot be classified. The bar-source decision (extend window / external feed / accept pilot scope) stays a James decision, carried over from Phase 4 §2.2. Default: classify what has bars; grow the sample over time. |
| Engine | VCET v1.1, verified (13 acceptance checks pass + CBO present — §9 gate). enable_cbo=true, require_cbo_for_expansion_confirmed=false. In-memory only — do NOT build main.vcet_bars until v1.1 proves discriminating power (Phase 4a recommendation). |
| Thresholds | Per-liquidity-tier slope_trend_thresh rather than a single global value (the 2.0 confound named in Phase 4a): large-cap individuals ~2.5, broad ETFs ~1.5–2.0, small-caps ~4–5 (06/01 calibration). CBO channel length per the shipped v1.1 config (Pardo default, confirmed from the package — not assumed), tuned alongside per tier. Overrides build a non-default VCETConfig at the call site; engine code untouched, Pine parity preserved for default runs. |
| Features per trade | Trajectory snap at {−5, 0, +5, +10, +15, +25}: state, vwap_slope_deg, vwap_band_width_pct, expansion_score, range_compression_score, vcet_score, price_distance_from_vwap_sd, PLUS the new CBO fields cbo_break_dir, cbo_break_offset, cbo_pre_entry_break (bool), cbo_channel_pos. |
| Classifier | The §4 CBO-augmented decision logic, priority C > continuation > A > B > D. Emits mechanism + confidence in memory only. |
A validation plan must say what would count as success and what would kill the idea. These six questions test whether v1.1/CBO genuinely classifies mechanism — not merely whether it emits labels.
Do the four mechanism classes occupy distinct, non-contradictory CBO + geometry cells?
PASS: no trade lands in a contradictory cell — e.g. no “rotation” trade that actually threw a CBO break, no “conversion” whose break was pre-entry. Each class’s defining features hold at the trade level.
Does CBO reclassify trades that v1.0 could not? Specifically, does pre-entry-break detection pull the three known trend_continuation_entry trades (LUNR 5/26, BB 5/28, INTC 6/2) out of insufficient_data into a real class?
PASS: ≥ the 3 known continuation trades correctly relabelled via pre-entry break; the audit’s 6 classifiable trades keep their labels under the CBO logic (no regressions).
Does an opposite-direction CBO break flag the known wrong-side trades (JOBY 5/29, HL 6/3) and the IBIT 6/3 −$216 plain-PI loss — earlier or cleaner than v1.0’s 15° slope-accel rule?
PASS: CBO direction at the break bar is opposite trade direction for these trades, confirmed at an offset ≤ where v1.0’s slope rule would have fired.
For the one known true conversion (JOBY 5/28), does CBO fire an in-direction break at ~+10/+15 coincident with the band expansion and TREND_UP transition?
PASS: CBO break offset aligns within ±5 min of the state→TREND transition. (n=1 today — a sanity check, not a base rate.)
Used as a layer on top of the RVOL+gap Quality Gate, does the mechanism label add management-relevant discrimination without contradicting the gate?
PASS: mechanism classes correlate with management outcome (conversion trades hold to +2 SD; rotation trades mean-revert at the band), AND the gate’s GREEN/RED zones remain the first filter unchanged. VCET v1.1/CBO informs how to manage, not whether to enter.
State the null and what would kill the idea: if CBO break direction/timing does not separate the mechanisms — rotation trades also throw breaks, or continuation trades show no pre-entry break, or conversions show no aligned break — then v1.1/CBO does not add mechanism-classification power.
KILL CRITERION: if ≥2 classes are indistinguishable on the CBO surface across the classifiable sample, stop — retain RVOL+gap + the v1.0 trajectory heuristics, do not propose mechanism_slug, and reconsider only if a later v1.x changes the operator.
This plan does not move VCET ahead of the gate. The VWAP Pull-In Quality Gate — RVOL + gap — remains the go/no-go first filter:
| Zone | Condition | Action |
|---|---|---|
| GREEN | RVOL 1.0–1.5 AND gap < 0.5% AND MTF grand > 25 | Take; hold for conversion if price closes above +2 SD |
| YELLOW | RVOL 1.5–2.5 OR gap 0.5–1.5% | Reduced size only; must articulate thesis before entry |
| RED | RVOL > 2.5 OR gap > 1.5% OR symbol in {IBIT, AMD, ETHU, RGTI} | Stop / reclassify |
mechanism_slug + companion VCET-context fields — additive, NULLable, non-breaking.canonical_strategy_slug rename, no taxonomy edit. The slug keeps its current outcome-based meaning with the documented mechanism caveat.On 2026-05-25 the on-disk package was v1.0 and blocked the whole plan. v1.0 has no CBO and only 7 automated checks — running this validation on it would write meaningless “CBO” columns. Before step 1, confirm the package is genuinely v1.1:
CBO / enable_cbo / Pardo — entirely absent in v1.0python/tests/test_synthetic.py exercises 13 acceptance checks (v1.0 automates only #1–#7)enable_cbo=true and require_cbo_for_expansion_confirmed=false exist; CBO fields / reason codes / backtest buckets presentPYTHONUTF8=1 PYTHONIOENCODING=utf-8 — the Windows cp1252 console crashes on the diagnostic arrow glyphsOne read-only CSV + one static HTML evidence table — same shape as the Mechanism Audit, one row per classifiable trade:
| Column group | Fields |
|---|---|
| Trade | symbol, date/time, side, net P&L |
| Quality Gate | RVOL, gap%, zone (GREEN/YELLOW/RED) |
| CBO (v1.1) | cbo_break_dir, cbo_break_offset, cbo_pre_entry_break |
| Trajectory | state & slope & band_width & expansion_score at each of the 6 offsets |
| Verdict | mechanism, confidence (HIGH/MED/LOW), and a “CBO vs v1.0 Δ” column showing what CBO changed vs the audit’s v1.0 call |
No DB writes. No engine edits. No Scorecards refresh. New file at vcet/python/… + one HTML at /system/VCET_V1_1_MECHANISM_VALIDATION_REPORT.html.
main.vcet_bars build · no mechanism_slug columncanonical_strategy_slug rename · no gen_scorecard.py Priority-3 editIf yes → VCET v1.1/CBO becomes the secondary management layer behind the RVOL+gap gate, and (after the §8 commit gate) mechanism_slug earns its schema. If no (V-Q6 kill) → RVOL+gap + v1.0 trajectory heuristics stand, and nothing in the taxonomy moves.