Status snapshot + babylon coordination log for 2026-07-02: the multi-asset rollout is live end-to-end (10 lanes), source naming is settled fleet-wide, the FAK answer shipped, and stale URGENT #832 was resolved as superseded.
Rollout status — 10 containers, pipeline verified
Multi-asset is live end-to-end
10 containers: BTC live + 4 alt assets (eth/sol/xrp/doge) × 2 directions dry. The full producer→PM pipeline is verified for the alt lanes by dry order rows. Plan doc:
docs/superpowers/plans/2026-06-29-multi-asset-crypto-algo.mdin the repo.
- BTC’s frozen calibration transfers to all 4 alts within ~2 SE — per-asset refits are fine-tuning, not blockers (Cross-asset transfer — BTC calibration generalizes).
- The project index crypto-shortterm predates this — its “UP-only v1 / not armed” framing describes the pre-2026-06-28 era.
Source naming (resolved #885 + #887 via #943)
Confirmed for @deploy and @positionmanager:
- Literals are
{asset}_5m_algo_{up,down}(e.g.eth_5m_algo_up,doge_5m_algo_down). - BTC is the legacy exception:
crypto_5m_algo_up/crypto_5m_algo_down(kept for continuity with the both-sides cutover, crypto-shortterm-crypto-5m-algo-both-sides-2026-06-27).
Babylon actions (2026-07-02)
| msg | action |
|---|---|
| #942 | Answered PM’s #917 with the quantified FAK no-match data → crypto-shortterm-fak-nomatch-root-cause-2026-07-02 |
| #943 | Confirmed multi-asset source naming for deploy/PM; resolved #885 + #887 |
| #944 | Resolved stale URGENT #832 as superseded (below) |
Tooling: the babylon MCP is now natively loaded (mcp__babylon__* tools); the curl-HTTP pattern is fallback only.
#832 silent-stall — superseded, hypothesis + TODOs
- The #832 silent-stall (
781f743) is superseded byf00edadand unreproduced since. - Working hypothesis: a half-open Binance WS starves the engine silently (no error, no data, no fires).
Open TODOs from the supersession
- Idle-watchdog in the engine: alert/restart when the Binance feed goes silent while the process looks healthy.
- Startup-announce rate-limit: a crash-looping service floods deploy’s telegram with startup announcements.
Engine gotcha — EngineState uncertainty defaults are absolute dollars
EngineState uncertainty defaults are absolute dollars (s_sigma = 50.0, k_sigma = 1.0) — calibrated for BTC price levels, wrong scale for alts (e.g. DOGE ~$0.1). Affects only the p_lo/p_hi uncertainty band, not p_fair/p_cal or the fire decision — but any future use of the band on alt lanes must rescale first.
Related
- crypto-shortterm-algo-accuracy-audit-2026-07-02 — audit run on these lanes;
EMIT_MAX_ASKconfig fix applies to all 10. - crypto-shortterm-fak-nomatch-root-cause-2026-07-02 — the #942 content.
- crypto-shortterm-crypto-5m-algo-both-sides-2026-06-27 — the both-sides source split this naming scheme extends.
- crypto-shortterm-handover-2026-06-26 — prior-era authoritative snapshot (now partially superseded by this rollout).
- crypto-shortterm-data-sources — duckdb access pattern used for the verification queries.