VCET v1.1 Source Reconciliation

Date 2026-06-04 · Read-only inventory of on-disk VCET artifacts to resolve the v1.1 blocker · Anchor: Pull-In Research Hub · Target: VCET v1.1 Mechanism Acceptance Test Plan · Constraints: read-only, no DB / code / taxonomy / Scorecards changes, no unzip over existing files.

⚠ Headline finding: only VCET v1.0 source exists on disk

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).

1. Is v1.1 source present?

NO
engine
YES
plan docs
0
v1.1 zips found
7 / 13
synthetic checks

v1.1 engine source — NOT FOUND

Searched locationPatternResult
/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 walk14 files total — same as vcet_v1.zip contents; all dated 2026-05-21. No CBO modules.
/z/ (Z drive) — find -iname "*vcet*"any vcet fileOnly HTML/MD plan documents in /system/ mirrors (a1, public_html, trsports_gd, www). No engine source.
/z/ — find -iname "*cbo*"any CBO fileNo matches. Zero CBO files on Z drive.
/c/Users/jtdom/Documents/ · /Desktop/any vcet fileNo matches.
/c/Users/jtdom/AppData/Local/Temp/*vcet* · *cbo*Only intermediate JSON outputs from prior audit runs. No engine.

v1.1 plan documents — PRESENT

✓ Z:\public_html\system\VCET_V1_1_MECHANISM_VALIDATION_PLAN.html · 30 KB · 2026-06-04 21:00
✓ Z:\public_html\system\VCET_V1_1_MECHANISM_VALIDATION_PLAN.md · 14 KB · 2026-06-04 21:01
✓ Z:\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)

Sister-doc overlap noted

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.

2. Is the available engine v1.0 or v1.1?

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.1Found on diskVerdict
grep for CBO in vcet_engine.pyPresent (the operator name)0 matchesv1.0
grep for Pardo in engine / docsPresent (Channel-Breakout Operator, Pardo Ch. 28)0 matches in engine, design spec, Pine, READMEv1.0
grep for enable_cbo in VCETConfigenable_cbo: bool = TrueField absentv1.0
grep for require_cbo_for_expansion_confirmedrequire_cbo_for_expansion_confirmed: bool = FalseField absentv1.0
test_synthetic.py exercises 13 acceptance checksChecks #1–#13Checks #1–#7 only (lines 108, 113, 120, 126, 132, 139, 145)v1.0
CBO reason codes (e.g., RANGE_BREAK_LONG_CBO_CONFIRMED)PresentOnly 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 schemaAbsent. Only range_break_confirmed, range_break_directionv1.0
Current-bar exclusion for channel high/low (Pardo)Channel computed on prior N bars, excluding current barRange high/low uses rolling(range_len).max() including current bar — v1.0 formv1.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 namingvcet_v1_1.zip or vcet_v1.1.zipOnly vcet_v1.zip existsv1.0

v1.0 has a precursor "range_break" that is NOT CBO

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.

3. Does the available source support the mechanism acceptance-test plan?

Per the plan, the engine must produce 9 trajectory features. Mapping each against the v1.0 engine on disk:

Feature required by planv1.0 produces it?Notes
vcet_stateYES9 canonical states (ALL_STATES) emitted per bar
reason_codeYESPer-bar reason emitted (ALL_REASONS)
vcet_scoreYESComposite 0–100 score per bar
range_compression_score (compression_score)YESPer-bar compression score, weighted A+B+C
expansion_scoreYESPer-bar expansion score, weighted A+B+C+D
vwap_band_width_pct (band_width)YESEmitted
vwap_slope_deg (slope)YESSmoothed slope output
CBO / range-break confirmation (Pardo, current-bar excluded)NOv1.0 emits range_break_confirmed but with v1.0 semantics (RVOL-thresholded, current-bar included). NOT the Pardo CBO.
State trajectory snapshotsPARTIALEngine 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.

4. What is missing?

Configuration fields (in VCETConfig)

Engine outputs (in REQUIRED_OUTPUT_COLUMNS)

Reason codes

Engine logic changes (per Validation Plan §3-4)

Test suite

Documentation

5. What should happen next? — verdict

A
v1.1 source exists and is runnable
Status: NOT THIS — v1.1 engine source not found anywhere.
B
v1.1 source exists but is incomplete
Status: NOT THIS — there is no v1.1 source on disk to patch. The v1.0 engine has a same-named-but-different-semantics range_break_confirmed field; calling that "incomplete v1.1" would be a misclassification.
C — selected
Only v1.0 source exists
Status: THIS IS THE STATE. Plan docs (Validation Plan + Acceptance Test Plan) describe v1.1 fully; engine source does not exist. The next step is to either locate the v1.1 package wherever it was originally drafted/spec'd (Drive folder, upstream email, Claude-generated artifact, etc.) or commission a fresh v1.1 build using the Validation Plan §3-4 as the build spec.
D
Source location unknown
Status: PARTIAL APPLICABILITY — D is correct if you (James) believe v1.1 source was previously created and we just haven't located it. C and D collapse to the same action — provide the v1.1 zip if it exists; build it if it doesn't.

6. Update recommendation for the acceptance-test plan

Leave the plan as BLOCKED — but tighten the language

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."

7. Exact files inspected

/c/Users/jtdom/Downloads/vcet_v1.zip (42 KB, 2026-05-21 16:31)
/c/Users/jtdom/Downloads/vcet/README.md (10 KB, 2026-05-21 12:06)
/c/Users/jtdom/Downloads/vcet/docs/vcet_design_spec.md (30 KB, 2026-05-21 11:44)
/c/Users/jtdom/Downloads/vcet/pine/vcet_indicator_v1.pine (28 KB, 2026-05-21 11:50)
/c/Users/jtdom/Downloads/vcet/python/vcet_engine.py (32 KB, 2026-05-21 11:46)
/c/Users/jtdom/Downloads/vcet/python/vcet_parity_audit.py (7 KB, 2026-05-21 12:06)
/c/Users/jtdom/Downloads/vcet/python/tests/test_synthetic.py (7.6 KB, 2026-05-21 12:07)
/c/Users/jtdom/Downloads/vcet/sql/vcet_schema.sql (13 KB, 2026-05-21 11:51)
/c/Users/jtdom/Downloads/vcet/sql/vcet_backtest_queries.sql (13 KB, 2026-05-21 11:52)
/z/public_html/system/VCET_V1_1_MECHANISM_VALIDATION_PLAN.html (30 KB, 2026-06-04 21:00)
/z/public_html/system/VCET_V1_1_MECHANISM_VALIDATION_PLAN.md (14 KB, 2026-06-04 21:01)
/z/public_html/system/VCET_V1_1_MECHANISM_ACCEPTANCE_TEST_PLAN.html (34 KB, 2026-06-04 21:15)

Search commands (read-only)

# 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

8. Exact files created by this reconciliation

Z:\public_html\system\VCET_V1_1_SOURCE_RECONCILIATION.html (this report)

Direct URL: https://trsportsacademy.com/system/VCET_V1_1_SOURCE_RECONCILIATION.html

9. What did NOT change

10. Awaiting your decision

Per the user instruction "Do not proceed beyond source reconciliation without my approval," the next move is yours:

  1. If you have v1.1 source somewhere I didn't search — point me to it (Drive, email, Claude artifact ID, etc.) and I'll re-verify against the §9 acceptance gate.
  2. If v1.1 source needs to be built — the Validation Plan §3-4 + §9 already constitute a build spec. The build would add ~6 config fields, ~6 output columns, the Pardo CBO computation, 6 new synthetic checks, and a §2.9 design spec rewrite. This is engine work (not research), so it should go to whoever owns VCET implementation.
  3. If v1.1 is deferred — keep the Acceptance Test Plan and Validation Plan in /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.

Links