1.2 KiB
2026-02-26 Session Notes
Project Scope Clarification
Brief session focused on establishing correct understanding of OpenMarketUI's core purpose. Initial description characterized it as a prediction market trading platform/engine, but user clarified the actual positioning: OpenMarketUI is fundamentally a trading strategy IDE — an interface-first product for users to build heuristic algorithms, train custom trading models, and manage the full strategy lifecycle from a user-friendly, performant UI.
Key distinction from initial framing: the web and watchtower UI layers are the actual product surface, not auxiliary dashboards. Users compose strategies and train models through the interface. Rust backend provides the heavy lifting (execution, backtesting, scoring pipeline) but is enabler, not the primary deliverable.
Architecture and pipeline remain unchanged: Source → Filter → Scorer → Selector → OrderExecutor with agricultural metaphor (specimens, beds, harvests, immune system). Kalshi in Rust; Polymarket (weather markets) in Python planned.
No code changes this session. Focus was repositioning mental model of the project as UI-first product rather than backend engine.