Cloud

Week 8 — Files in a bucket

16 July 2026AmsterdamJordi Lluis

After the 5-minute Polymarket run stopped, I moved to recordings. That day a paper-only pipeline sat in Google Cloud, europe-west1: a state bucket, Cloud Run jobs, hourly and daily schedules. No broker credentials. Execution was off.

What was stored, and what Pattern Forge later ships
Venue in the filesPolymarket Perps hourly candles, not CME, not a cash index.
That day’s snapshotWTI 1,624 hourly rows in the venue table. 2,414,184 is venue trade count on the selected contract, not my fills.
Public catalog nowTen parquet series in Pattern Forge. 20,567 closed hourly bars after dropping a last bar that may still have been forming. Gaps stay empty.
WTI in the catalog2,482 closed bars, 42 missing hours, SHA-256 6733ae8ec1646133…

A row here is a closed hour: open, high, low, close, timestamp. Models on that day’s paper ledger promoted zero venue-native candidates. Candidate net return was not positive.

I can put market files in a bucket, hash them, and leave holes empty. That is not a live Hyperliquid bot, and it is not official energy statistics.

Catalog · Week 14 — WTI is not spot oil

← Blog