crypto-shortterm’s GitHub repo was renamed and the code relocated as part of the pmv2 re-architecture into one self-contained git repo per component. This note records the new canonical names/paths and the producer/executor split that governs how crypto-shortterm places orders.

For Agents

Canonical from 2026-06-22 onward:

  • GitHub repo: wowjeeez/pmv2-crypto-algo (was wowjeeez/crypto-fetch). GitHub redirects old→new. origin/main = 7bfe3a0.
  • Local path: /Users/levander/coding/pmv2/crypto_algo (was /Users/levander/coding/crypto_fetch, now empty).
  • The old repo name and old path are stale everywhere — use the new ones.

What Changed

ItemOldNew
GitHub repowowjeeez/crypto-fetchwowjeeez/pmv2-crypto-algo
Local workspace/Users/levander/coding/crypto_fetch/Users/levander/coding/pmv2/crypto_algo
Babylon handlecryptocrypto (unchanged)

Git history, .env, and .mcp.json all moved with the code. The local remote was updated and verified; the project builds clean from the new path. GitHub’s old→new redirect means stale clone URLs still resolve, but new references should use the new name.

pmv2 Re-Architecture: One Repo Per Component

The pmv2 system is realized as one self-contained git repo per component, split into producers, a shared executor, and a notification service:

ComponentRole
crypto_algo (this project)Producer — emits Directives
cohort_algoProducer
us_weather_algo / as_weather_algoProducers
position_managerShared executor — consumes Directives, places orders via CLOB
telegram_connectorNotification service

For Agents — crypto-shortterm does NOT build its own order path

crypto-shortterm is a producer only. It does not own a wallet, key, or CLOB order path. It publishes a Directive envelope to NATS subject cohort.signals; pmv2’s position_manager executor consumes by source and places the order via CLOB. No new wallet/key/service is built on the crypto-shortterm side. See crypto-shortterm-phase1-execution-decision.