OPEN_SOURCE ↗
REDDIT · REDDIT// 5h agoINFRASTRUCTURE
Trading system strips LLM execution rights
The post sketches a v2 trading architecture that uses llm-nano-vm as a deterministic state machine, with Python handling structure, trigger, and risk while the LLM only interprets higher-level context. The author is asking whether that split gives the model enough authority to add value without letting it control execution.
// ANALYSIS
The division mostly makes sense: once money is on the line, deterministic rules should own trigger and sizing, and the LLM should stay in the fuzzy layer where interpretation, ranking, and exception handling matter.
- –Keeping M15/M5 trigger logic fully deterministic is the right move if the goal is reproducibility, backtestability, and fewer “almost valid” discretionary trades
- –Step 1 and 2 are probably giving the LLM enough responsibility already; it should rank or choose among precomputed candidates, not invent structure from raw price action
- –Separating HTF and Structure agents helps debugging and failure attribution, especially when you need to know whether the miss was narrative selection or POI selection
- –If token budget becomes a problem, merge only after the Python extractors are stable; premature merging usually hides errors instead of fixing them
- –The Context agent is the weakest link unless hard vetoes like news blackouts and killzones are enforced in Python, not merely suggested by the model
// TAGS
llmagentautomationinfrastructurellm-nano-vmtrading-system
DISCOVERED
5h ago
2026-04-30
PUBLISHED
7h ago
2026-04-30
RELEVANCE
7/ 10
AUTHOR
Simone_Crosta