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
Bifrost AI Gateway: Open-Source Tool Addresses AI Infrastructure Gaps
Bifrost is an open-source Go-based LLM gateway that provides automatic failover between providers, budget caps that reject requests, audit logging, and hooks for evaluation. Benchmarks show it's ~50x faster than LiteLLM at high throughput.
Agent-Xray: Open-source tool for debugging AI agent failures from trace logs
Agent-Xray is an MIT-licensed open-source tool that analyzes AI agent trace logs to classify failures into categories like spin, tool_bug, and early_abort, and includes an enforcement mode to test fixes against adversarial challenges.
Introducing OneTool MCP: An Open Source Multi-Tool for Developers
OneTool MCP, built using Claude AI, offers developers over 100 tools for tasks like web searches, library updates, and file management without tool tax or context rot.
ClaudeOrb: Chrome Extension Monitors Claude API Usage in Real-Time
A developer built ClaudeOrb, a free Chrome extension that displays Claude session percentage, weekly limits, countdown timers, Claude Code costs, and 7-day spending trends. The tool was created using Claude Code after hitting rate limits without warning.