← back to chart · Sanitized, point-in-time capture
of the VPS automation state (paths under /home/allofthesewords/eqpos_pipeline/).
This evidences the schedule and recent runs; it is a snapshot, refreshed by the pipeline.
30 6 * * * .../pipeline/publish.sh --check # daily freshness check 0 7 * * 6 .../pipeline/publish.sh --full # weekly rebuild (after Fri CFTC + NAAIM)
| Check | Status |
|---|---|
| cron daemon (systemctl is-active cron) | active |
| two crontab entries installed | present (shown above) |
| credentials / interactive login required | none (user-level cron) |
[2026-07-18 03:27:35] PUBLISH: latest=2026-07-17 value=0.1851 pct=55.4% n=736 (full rebuild) [2026-07-18 03:30:20] CHECK: no new weekly observation (latest still 2026-07-17); keeping previous output. [2026-07-18 03:30:22] no new weekly observation; web output unchanged (daily check -> preserved)
| Test | Evidence |
|---|---|
| Last successful full rebuild | 2026-07-18 03:27 UTC (PUBLISH line above) |
| Last daily freshness check | 2026-07-18 03:30 UTC; correctly kept previous output when no new weekly observation existed |
| Stale/failed-source handling | logs show "refetch ... failed validation; using existing cached file" — a failed source refetch does not corrupt the build; the previous valid cached file is used |
| Atomic publication | publisher copies to .tmp then mv over the target; a failed run leaves the previous web files intact ("previous valid output preserved (atomic publish aborted)") |
| Rollback | timestamped source snapshots kept in data/archive/ (50 at capture); restoring a prior equity_positioning_data.json + components.csv into the web root rolls the chart back |
assert composite length > 400 and monotonically increasing assert |composite| < 4 (Z bounds) assert latest observation age <= 10 days (stale guard) assert composite == equal-weight mean of component Z-scores (max dev < 1e-9)
This page is a sanitized self-report from the pipeline host. It evidences the schedule and recent behaviour but is not an independent attestation. The strongest public guarantees are the machine-readable artifacts — data, components, source manifest, run manifest and SHA-256 checksums — which can be recomputed independently of this page.