The on-disk engine is v1.0 (7 synthetic checks, RVOL-thresholded range_break, no CBO / Pardo / enable_cbo terms). The only zip on disk is vcet_v1.zip (dated 2026-05-21); there is no vcet_v1_1.zip anywhere in Downloads, Z drive, Documents, Desktop, or AppData/Temp.
Two v1.1 plan documents already exist in /system/ — but they describe the v1.1 engine, they don't contain it. The plan-vs-engine gap is exactly the B1 blocker noted in the Acceptance Test Plan §7.
Verdict: Option C — only v1.0 source exists. Next step is to rebuild or restore the v1.1/CBO package from a prior handoff (Drive, email, upstream chat, or whatever channel originally delivered the v1.1 spec).
| Searched location | Pattern | Result |
|---|---|---|
/c/Users/jtdom/Downloads/ | vcet_v1_1.zip · vcet_v1.1* · *CBO* | Only vcet_v1.zip (2026-05-21, 42 KB). No v1.1 zip. Only unrelated hit: FashionablyLate_V2_Bands-v1.1.txt. |
/c/Users/jtdom/Downloads/vcet/ (unpacked tree) | full directory walk | 14 files total — same as vcet_v1.zip contents; all dated 2026-05-21. No CBO modules. |
/z/ (Z drive) — find -iname "*vcet*" | any vcet file | Only HTML/MD plan documents in /system/ mirrors (a1, public_html, trsports_gd, www). No engine source. |
/z/ — find -iname "*cbo*" | any CBO file | No matches. Zero CBO files on Z drive. |
/c/Users/jtdom/Documents/ · /Desktop/ | any vcet file | No matches. |
/c/Users/jtdom/AppData/Local/Temp/ | *vcet* · *cbo* | Only intermediate JSON outputs from prior audit runs. No engine. |
Z:\public_html\system\VCET_V1_1_MECHANISM_VALIDATION_PLAN.html · 30 KB · 2026-06-04 21:00Z:\public_html\system\VCET_V1_1_MECHANISM_VALIDATION_PLAN.md · 14 KB · 2026-06-04 21:01Z:\public_html\system\VCET_V1_1_MECHANISM_ACCEPTANCE_TEST_PLAN.html · 34 KB · 2026-06-04 21:15 (my newer doc)Z:\public_html\system\VCET_AT_ENTRY_VALIDATION_PLAN.md · Phase 4 plan (now superseded by post-entry trajectory approach)The pre-existing VCET_V1_1_MECHANISM_VALIDATION_PLAN.html (dated 2026-06-04 21:00) and my newer VCET_V1_1_MECHANISM_ACCEPTANCE_TEST_PLAN.html (2026-06-04 21:15) cover overlapping ground. The pre-existing plan uses correct CBO / Pardo / Channel-Breakout Operator terminology (which my plan called "CBO" generically without naming the source). Both plans agree on §9 acceptance gate: CBO + enable_cbo + Pardo grep + 13-check synthetic test. Recommendation: keep both for now; the Validation Plan is the authoritative spec, the Acceptance Test Plan is a more granular test-execution variant. Consolidate later if desired.
Direct grep against the v1.1 acceptance gate criteria (per Validation Plan §9). All checks point to v1.0:
| Check (from §9 acceptance gate) | Expected for v1.1 | Found on disk | Verdict |
|---|---|---|---|
grep for CBO in vcet_engine.py | Present (the operator name) | 0 matches | v1.0 |
grep for Pardo in engine / docs | Present (Channel-Breakout Operator, Pardo Ch. 28) | 0 matches in engine, design spec, Pine, README | v1.0 |
grep for enable_cbo in VCETConfig | enable_cbo: bool = True | Field absent | v1.0 |
grep for require_cbo_for_expansion_confirmed | require_cbo_for_expansion_confirmed: bool = False | Field absent | v1.0 |
test_synthetic.py exercises 13 acceptance checks | Checks #1–#13 | Checks #1–#7 only (lines 108, 113, 120, 126, 132, 139, 145) | v1.0 |
CBO reason codes (e.g., RANGE_BREAK_LONG_CBO_CONFIRMED) | Present | Only REASON_RANGE_BREAK_LONG / REASON_RANGE_BREAK_SHORT (v1.0 RVOL-thresholded form) | v1.0 |
CBO output columns (cbo_break_dir, cbo_break_offset, cbo_pre_entry_break, cbo_channel_pos) | Present in output schema | Absent. Only range_break_confirmed, range_break_direction | v1.0 |
| Current-bar exclusion for channel high/low (Pardo) | Channel computed on prior N bars, excluding current bar | Range high/low uses rolling(range_len).max() including current bar — v1.0 form | v1.0 |
| Self-identification in design spec / Pine | "VCET v1.1" header | # VCET v1 — Design Spec and // VCET v1 — VWAP Compression / Expansion / Trend Engine (Pine) | v1.0 |
| Zip naming | vcet_v1_1.zip or vcet_v1.1.zip | Only vcet_v1.zip exists | v1.0 |
The on-disk engine emits range_break_confirmed and range_break_direction (see §2.9 of the design spec), but the v1.0 form is an RVOL-thresholded high/low breach over range_len=10 bars with no current-bar exclusion. The v1.1 CBO is structurally different: Pardo Channel-Breakout Operator, current-bar excluded, with break-timing-relative-to-entry semantics that the v1.0 form cannot compute. Same output column name, different semantics, different acceptance behavior. The Validation Plan §3-4 logic depends on the v1.1 CBO form (cbo_break_dir × pre_entry vs post_entry) — the v1.0 range_break_confirmed cannot serve as a substitute.
Per the plan, the engine must produce 9 trajectory features. Mapping each against the v1.0 engine on disk:
| Feature required by plan | v1.0 produces it? | Notes |
|---|---|---|
vcet_state | YES | 9 canonical states (ALL_STATES) emitted per bar |
reason_code | YES | Per-bar reason emitted (ALL_REASONS) |
vcet_score | YES | Composite 0–100 score per bar |
range_compression_score (compression_score) | YES | Per-bar compression score, weighted A+B+C |
expansion_score | YES | Per-bar expansion score, weighted A+B+C+D |
vwap_band_width_pct (band_width) | YES | Emitted |
vwap_slope_deg (slope) | YES | Smoothed slope output |
| CBO / range-break confirmation (Pardo, current-bar excluded) | NO | v1.0 emits range_break_confirmed but with v1.0 semantics (RVOL-thresholded, current-bar included). NOT the Pardo CBO. |
| State trajectory snapshots | Engine emits per-bar rows; the snapper (snap_at(target_utc, window_min=5) in pi_trend_mechanism_audit.py) is already written for v1.0. The mechanic of snapping is portable; the data flowing through it just lacks CBO fields. |
Bottom line: v1.0 supplies 8 of 9 features needed by the acceptance plan. The missing one (CBO) is the central new operator that the entire v1.1 mechanism-classification logic (§4 of the Validation Plan) hinges on. Without CBO, four of the seven mechanism classes (true_pull_in_to_trend, trend_continuation_entry, wrong_side_escape, range_break_hitchhiker) lose their primary decision axis.
VCETConfig)enable_cbo: bool = Truerequire_cbo_for_expansion_confirmed: bool = Falsecbo_lookback: int = 20) — exact name/default per Pardo Ch. 28 / shipped v1.1 configREQUIRED_OUTPUT_COLUMNS)cbo_break_dir (NONE / UP / DOWN per bar)cbo_break_offset (bars since last CBO break)cbo_pre_entry_break (boolean, set per trade at snap time)cbo_channel_pos (position within channel)cbo_channel_high / cbo_channel_low (the Pardo channel, current-bar excluded)REASON_RANGE_BREAK_LONG_CBO_CONFIRMEDREASON_RANGE_BREAK_SHORT_CBO_CONFIRMEDREASON_RANGE_BREAK_LONG/SHORT would coexist or be renamed)cbo_lookback bars excluding current bar (v1.0 includes current bar)require_cbo_for_expansion_confirmed tightens EXPANSION_CONFIRMED state when setrange_break_confirmed field; calling that "incomplete v1.1" would be a misclassification.vcet_v1_1.zip.The Acceptance Test Plan §7 currently lists B1 (v1.1 engine missing) as a HIGH blocker. This reconciliation confirms B1 is real. No status downgrade is warranted.
Suggested edit (proposed only, not applied here): change Plan §10 step 1 from "Now (this plan): document the test design, blockers, acceptance criteria" to "Now: blocked on v1.1 source delivery (see VCET_V1_1_SOURCE_RECONCILIATION)." No plan content changes; just a pointer to this reconciliation so anyone reading the plan knows the blocker has been verified, not just asserted.
Status word for the hub card: "Blocked on v1.1 engine source (reconciled 2026-06-04)." Not "ready for synthetic verification."
# Engine grep for v1.1 markers
grep -iE "cbo|pardo|enable_cbo|require_cbo|channel.?break" \
/c/Users/jtdom/Downloads/vcet/python/vcet_engine.py
# Result: 0 matches for CBO / Pardo / enable_cbo / require_cbo
# (range_break_* IS present, but v1.0 form)
# Synthetic acceptance check count
grep -nE "^ # --- Acceptance check" \
/c/Users/jtdom/Downloads/vcet/python/tests/test_synthetic.py
# Result: 7 matches (#1 through #7); v1.1 requires 13
# Filesystem-wide v1.1 zip search
find /c/Users/jtdom/Downloads /z /c/Users/jtdom/Documents \
/c/Users/jtdom/Desktop -iname "*vcet*" -type f
# Result: vcet_v1.zip (v1.0) + plan-only HTML/MD docs; no v1.1 engine zip
# Filesystem-wide CBO search
find /z -maxdepth 5 -iname "*cbo*"
# Result: 0 matches
Direct URL: https://trsportsacademy.com/system/VCET_V1_1_SOURCE_RECONCILIATION.html
vcet_engine.py edits · no VCETConfig changesgen_scorecard.py or other classifier code editsmain.user_strategies changesvcet_v1.zip NOT unzipped over existing files (already-unpacked tree is identical to zip contents — verified by file size/date comparison)/system/VCET_V1_1_SOURCE_RECONCILIATION.html (this file)Per the user instruction "Do not proceed beyond source reconciliation without my approval," the next move is yours:
/system/ as inert specs, mark the hub card "Blocked on v1.1 engine source (reconciled 2026-06-04)", and continue with Quality Gate as primary + v1.0 trajectory heuristics as the working secondary layer. Mechanism research stays where it is.