06 · SYSTEM
Universe, sync & freshness
store connected · 0 runs in the ledger tail
snapshot generated 2026-08-26 11:52 ET
snapshot generated 2026-08-26 11:52 ET
Nothing has been computed yet
No job has ever completed against this store, so there are no bars, no regime fit, no volatility series and no study results to read. Add tickers to the watchlist on System and dispatch a nightly run; results land when the runner finishes, typically in minutes to tens of minutes.
WATCHLIST UNIVERSE · NIGHTLY BATTERY COVERAGE
SPY
1 tickers · per-ticker cost is not yet measured — it appears once a nightly run records stage timings. The universe is deliberately broader than the book: it drives public-data jobs and is stored in plaintext, so keeping it wider than the holdings is what stops it fingerprinting them.
MULTI-DEVICE SYNC · ALWAYS ENCRYPTED
Everything that leaves this device is encrypted before it goes. There is no unencrypted mode to choose. The passphrase is the only key: it is derived here with PBKDF2-SHA256 at 600,000 iterations, used for AES-256-GCM, and never sent. It is not stored, not recoverable and not resettable — lose it and the synced blob is unreadable forever. Local data on this device is unaffected either way.
no recovery. write it down.
this device has never synced
the server stores ciphertext, an IV, a salt, the KDF parameters and a version. It has no key and no way to obtain one — a failed decrypt here means the passphrase is wrong or the blob was altered, and nothing local is changed either way.
DATA FRESHNESS · PER DATASET
DATASET
SOURCE
AS OF
STATUS
daily OHLCV, watchlist
yfinance
—
NEVER
index strip
yfinance
—
NEVER
options chains / IV
yfinance
—
NEVER
regime model fits
nightly job
—
NEVER
volatility series
nightly job
—
NEVER
distribution fits
nightly job
—
NEVER
MVO moments
nightly job
—
NEVER
signal battery
nightly job
—
NEVER
macro series
FRED
—
NEVER
stale means the source last succeeded more than 36 hours ago. Numbers from a stale dataset carry this as-of date wherever they appear, not only here — source outages are routine rather than exceptional, and the interface treats them that way.
JOB LEDGER
idle — checking on focus and every 5 min
the ledger is empty — no run has ever been dispatched against this store
a dispatch queues a run and returns; it does not wait, and nothing on this page streams
stage timings are recorded per run, which is where the per-ticker cost figure above comes from. Per-ticker failures are recorded against the run rather than being absorbed by writing yesterday’s value under today’s date.