Expand description
rungbot-research — the weekly research pipeline behind rungbot research.
Research only. Nothing here can place an order or reach a venue’s private API: the crate holds no venue key and is not a dependency of the executor.
The pipeline, stage by stage, all composing through one ledger file
(opportunity-ledger.json) in a data directory:
oppscan— the technical half: CoinPaprika’s whole market in one call, kept to a tradable band and ranked by distance from the all-time high.survivor— the bear/chop screen: a DefiLlama value index (fees, TVL, category), a value-first selection, then web evidence and an LLM verdict per coin.catalyst— the bull screen: web evidence of a forward catalyst, then an LLM verdict per coin.unlocks— a token-unlock calendar from DefiLlama’s open dataset CDN.theses— which of those runs in which market regime, and how it is titled.report— reads the regime, runs the matching thesis, and writes one dated note plus a short HTML email.
Every outside call goes through a trait (Fetch, Search, Llm,
report::NoteSink, report::Mailer) so the golden tests replay recorded
responses and never touch the network. The real clients live in clients.
§The LLM command
No model provider is built in. You name a command in the config; the prompt goes to
its stdin and its stdout is the answer. The command always gets a spend cap appended
(--max-budget-usd <N> by default; both the flag and the amount are configurable,
neither can be switched off), and nothing grants it extra permissions: whatever
flags your tool needs, you write them into the command yourself.
Re-exports§
pub use py::Json;
Modules§
- catalyst
- The bull screen: is there a forward catalyst that could reprice a dislocated coin?
- cli
rungbot research <stage> ...: argument parsing and wiring of the real clients.- clients
- The real clients behind the research traits.
- date
- Calendar dates for the research pipeline.
- oppscan
- The technical half: which coins inside a tradable band are furthest off their high.
- py
- JSON and text with the semantics the ledger files were first written with.
- report
- The weekly report: read the regime, run the matching thesis, write one dated note and a short email.
- survivor
- The bear/chop screen: of the deeply dislocated coins, which have a business that survives to the next bull and gets re-rated on fundamentals?
- theses
- Which screen runs in which market regime, and how its report reads.
- unlocks
- When does a coin’s supply overhang clear? The next token-unlock cliffs from DefiLlama’s open dataset CDN, no key needed.
Structs§
- BufConsole
- Everything a stage printed, for tests.
- Ctx
- The shared pieces of a stage that reaches outside.
- Paths
- The data directory the ledger and indexes live in.
- StdConsole
- stdout and stderr, one
printper call.
Enums§
Constants§
- LEDGER
- The ledger every stage reads and writes.
- UA_
BROWSER_ SCAN - UA_SCAN
- The User-Agent the public data sources were read with.
- UNLOCK_
INDEX SYMBOL -> {slug, gecko_id}for the unlock calendar.- VALUE_
INDEX SYMBOL -> {name, tvl, category, gecko_id, fees30d, revenue30d}from DefiLlama.
Traits§
- Console
- Where a stage prints. The real one is stdout/stderr; tests capture it.
- Fetch
- A keyless JSON GET.
- Llm
- An LLM behind a command: the prompt in, raw stdout out. An
ErrisKind: message. - Search
- A web search: one JSON request body in, the parsed JSON response out.
Functions§
- by_
dislocation - Indices of
candsordered bydislocation_score, deepest first; equal scores keep their ledger order. - no_llm
- The message a synthesis stage stops with when no LLM command is configured.
- read_
json - Read and parse a JSON file.
- read_
ledger - The ledger as a list of records.
- write_
json - Write
valueas indented JSON, through a temp file and a rename so a reader never sees half a file. - write_
ledger