Read-only market research engine. Bot-runtime agnostic.

any bot  →  rocket <workflow> --json  →  ResearchResult  →  adapter presents

Safety: READ_ONLY_RESEARCH_ONLY_HUMAN_GATED. No orders, no signing, no automatic holdings or watch changes.

Design: docs/ROCKET_PLAN.md

python3 -m venv .venv
.venv/bin/pip install -e '.[dev]'
.venv/bin/rocket status
.venv/bin/pytest -q -m 'not integration'

Secrets come from the process environment (existing names). Rocket never deletes or rewrites them. Callers pass private state paths explicitly.

Large research payloads (for example the ~1GB Solana memecoin follower-study captures) live outside git in the public dataset jhonnyisaacc/rocket, laid out under the same docs/research/... paths they were captured from. Small manifests and code stay in the repo; anything over ~1MB goes to the dataset. Fetch what you need, for example:

hf download jhonnyisaacc/rocket --repo-type=dataset \
  --include 'docs/research/memecoin/data/*'

The Research Project is a gated decision tree with WIP 3. Start with the charter, protocol, and trial ledger. Minimal machine gates and the official scoring contract live in research/governance. Repository workflow is LIGHTWEIGHT; scientific research is STRICT / MACHINE-GATED. Ordinary engineering is outside research WIP/admission; independent scientific review is recorded in artifacts and may be published by the same GitHub actor. MOM-002 remains Draft/unapproved/unscored. Rocket remains READ_ONLY_RESEARCH_ONLY_HUMAN_GATED; these controls authorize no execution.