Multi-LLM Paper-Trading Bot with Claude Opus as Lead Engineer and Gemini as Strategist: Architecture Breakdown
A developer has shared an autonomous paper-trading bot running on Alpaca that uses a multi-LLM architecture with bounded roles and a documented veto process. The project spans ~4,900 LOC across five Python modules and is fully open-source on GitHub.
Architecture: Three Roles, Bounded Scope
- Commander (human): Capital authority and thesis sign-off. Anything touching money requires human approval.
- Strategist (Gemini Pro): Scope-limited to thesis adjudication only. Not allowed to make implementation choices, pick the broker SDK, or decide architecture.
- Lead Engineer (Claude Opus 4): Writes all code. Audits Strategist directives and has veto power over directives that don't survive contact with engineering reality. Vetoes are logged on the record.
No party can deploy autonomously. Every disagreement is logged in a "Strategist Codex" document that now has 270+ entries. The codex never hides reversals — if a principle gets superseded later, both versions remain with dates.
Why Multi-LLM Works Here
The creator argues that a single LLM has no incentive to disagree with itself. Two LLMs from different vendors with bounded scopes and a documented veto path produce something closer to a real engineering review process. The friction forces disagreement into the design phase instead of the post-mortem.
Real Example: Broker SDK Field Disagreement
Strategist directive: anchor a 14-day position-decay clock to Position.created_at from the broker SDK. Claude (Engineer) checked dir(Position) against the live Alpaca SDK and found the field doesn't exist. Implemented a state-side ledger instead and logged the doctrine update with rationale: "broker did not in fact provide the field the original adjudication assumed." During architect review, Claude further refactored because the first pass held a state lock across N broker calls. Both passes are recorded in the Codex.
Who This Is For
Developers building multi-LLM agent workflows, especially for financial automation or any domain where audit trails and adversarial review are critical. Also relevant for anyone exploring coordinated multi-agent systems with explicit veto logging.
Repo and full 9-page architecture paper: https://github.com/ALGEM-hub/Whitepaper
📖 Read the full source: r/ClaudeAI
👀 See Also
Super Claude browser extension makes Claude.ai UI fully customizable
A developer built a browser extension that lets users customize every aspect of Claude.ai's interface — colors, fonts, layout, plus usage tracking and token counting. The extension works on Chrome and Firefox and was developed using Claude itself.
Bend: A Proof-Checked Language That Blocks AI Mistakes on CPU and GPU
Bend compiles to native code and runs in parallel across CPU cores or GPU. Its LAWS.bend files let agents prove rules hold, blocking bug merges before they happen.
Paper Lantern MCP Server Connects Claude Code to Research Papers
Paper Lantern is an MCP server built with Claude Code that connects coding agents to over 2 million CS and 43 million biomedical research papers, enabling them to find benchmarked methods instead of defaulting to training data.
Claude Code gains TLA+ model checking via tla-mcp MCP server
tla-mcp is a new MCP server that lets Claude Code call the TLA+ model checker tla-rs as a first-class tool — validate specs, run bounded checks with counterexample traces, and replay scenarios from the chat.