The 20-pair Liberator/kti parity test could not run because kti liberator query --dataset minute_bars consistently times out with "context deadline exceeded" on every (symbol, date) pair tried. Root cause: the user account's Liberator entitlements have dropped from 27 datasets to 10 sometime between 2026-06-05 15:00 ET and 2026-06-07 19:55 ET. The remaining 10 entitlements are fis_* (lending data), s3_partners, and wonda - no market_data datasets including minute_bars are currently accessible.
This is a real, structural blocker. The 20-pair parity test cannot complete until minute_bars entitlement is restored (probably requires re-auth with CloudQuant or a renewed token). Once Liberator is back, re-running the test takes ~5-10 minutes.
Stage B is BLOCKED on Liberator restoration. The hybrid source recommendation from Stage A cannot be locked in until parity is verified at scale.
$ kti liberator datasets Found 27 entitled dataset(s) across all environments: Name: arca_imbalance Category: market_data Name: daily_bars Category: market_data Name: daily_bars_adjusted Category: market_data Name: minute_bars Category: market_data <-- AVAILABLE Name: minute_bars_raw Category: market_data Name: trades_v2 Category: market_data Name: fis_borrower_activity_rating_b1 Category: fis ... (17 more)
$ kti liberator datasets Found 10 entitled dataset(s) across all environments: Name: fis_borrower_activity_rating_b1 Name: fis_loan_rate_dispersion_r2 Name: fis_loan_rate_eod_n2 Name: fis_loan_rates_p2 Name: fis_retail_loan_rates_p5 Name: fis_short_data Name: fis_utilization_isin_u1 Name: fis_utilization_percent_u2 Name: s3_partners Name: wonda # minute_bars NOT in list
$ kti liberator query --dataset minute_bars --date 2026-06-04 --symbols NVDA --format json Error: failed to query data: failed to read stream: context deadline exceeded (Client.Timeout or context cancellation while reading body) real 4m0.260s
Every minute_bars query times out at the 4-minute deadline. This is consistent with the server rejecting the query at the entitlement layer but the kti CLI not surfacing that as a fast error - it waits for the stream that never comes.
Only one (symbol, date) pair from the Stage A initial pilot has BOTH kti coverage AND a previously-cached Liberator response. That's NVDA 2026-06-02, which was fetched at 2026-06-05 15:32 ET before entitlement changed.
| Metric | Value |
|---|---|
| Symbol / date | NVDA / 2026-06-02 |
| kti RTH bars | 390 |
| Liberator RTH bars | 390 |
| Close max diff | $0.0000 (exact) |
| Close median diff | $0.0000 |
| OHLC spot-check (3 bars at 09:30, 10:00, 15:55) | Identical to penny |
| Volume median diff | 5,251 shares (Liberator higher by 1-6%) |
| Volume max diff | 230,456 shares (at 09:30 open burst) |
| kti VWAP at session close | compute later (not done here) |
| Liberator native VWAP at close | ~226.17 (from per-bar field) |
This single pair confirms that when Liberator IS available, OHLC matches kti exactly. But n=1 is not the 20-pair statistical baseline the user requested.
| Pair | Date | Liberator status |
|---|---|---|
| RGTI | 2026-06-04 | TIMEOUT (120s) |
| QQQ | 2026-06-04 | TIMEOUT (120s) |
| QBTS | 2026-06-04 | TIMEOUT (120s) |
| MRVI | 2026-06-04 | TIMEOUT (120s) |
| IGV | 2026-06-04 | TIMEOUT (120s) |
| IBIT | 2026-06-04 | TIMEOUT (120s) |
| ... (rest not attempted) | process killed after 6 timeouts | — |
The parity script stage_a1_parity.py is queued; it will reuse the kti cache and only fetch the Liberator side. Re-running once entitlement is restored is ~5-10 minutes for the full 20 pairs.
The script selected 20 distinct symbols from the kti cache, sorted by recency (most recent dates first), one per symbol where possible:
| # | Symbol | Date | Why selected |
|---|---|---|---|
| 1 | RGTI | 2026-06-04 | Most recent |
| 2 | QQQ | 2026-06-04 | ETF |
| 3 | QBTS | 2026-06-04 | Small-cap |
| 4 | MRVI | 2026-06-04 | Biotech |
| 5 | IGV | 2026-06-04 | Tech ETF |
| 6 | IBIT | 2026-06-04 | Crypto-adjacent (the leak-symbol) |
| 7-20 | Various | 2026-06-03 and older | Diversity across slugs and dates |
The Stage A initial pilot's tentative recommendation (hybrid source) was based on a single overlapping pair (NVDA 6/2) plus 4 Liberator-only samples. The user explicitly requested 20-pair verification before Stage B. That bar has not been cleared.
If Stage B were forced to proceed now:
Stage B is correctly BLOCKED.
| Risk | Severity | Mitigation |
|---|---|---|
| Liberator entitlement may not be restored quickly | HIGH | Contact CloudQuant; check whether re-auth or token refresh is needed |
| Even with parity verified, volume drift (~5-10%) may affect RVOL-derived signals across source boundary | MEDIUM | Characterize on 20 pairs; if uniform, adjust Stage B pipeline; if symbol-specific, may need per-symbol calibration |
| Liberator native VWAP cross-check (Stage A.1 §3) untested without live access | MEDIUM | Add to 20-pair test once Liberator returns |
| kti window may shrink further with time (today: 14d effective, was 60d earlier in the project) | LOW-MED | Monitor kti retention; document in Stage B blocker if window drops |
| Pre-market policy not yet decided (see PREMARKET_POLICY_RECOMMENDATION) | LOW | Independent decision; not gated by Liberator |
stage_a1_parity.py for re-run once Liberator returnsSpecifically:
minute_bars entitlement (CloudQuant action; re-auth or token refresh likely)stage_a1_parity.py for the 20 queued pairs (~5-10 min once Liberator works)Estimated time to clear once Liberator is back: under 30 minutes of compute. Estimated time to wait for Liberator restoration: unknown (depends on CloudQuant entitlement action).