How samuelclark04/signaldesk-v2 works
SignalDesk is a multi-market trading terminal with paper and broker-live execution. Users inspect market opportunities and portfolio state, then approve or reject staged setups; strategies propose candidates, the risk engine sizes and gates them, and the ledger records approved trades. The server also manages exits, portfolio-pilot actions, market intelligence, and live client updates. The empty README and partial excerpts limit certainty about some subsystem wiring, so the graph shows only documented or directly evidenced connections.
Main entry points: server.js HTTP and WS hub · pipeline.js Trading pipeline · app.js Terminal shell · order-router.js Order routing
Components 21
Client experience
- Terminal shell
client/app.js - Opportunities
client/views/opportunities.js - Portfolio views
client/views/portfolio.js - Trade tickets
client/components/manual-trade-ticket.js
Market data
- Broker connectors
server/connectors/alpaca-api.js - Price and session data
server/market/latest-prices.js
Trade lifecycle
- Trading pipeline
server/execution/pipeline.js - Market strategies
server/strategies/1-equity-day.js - Risk engine
server/risk/risk-engine.js - Trade ledger
server/execution/paper-ledger.js - Order routing
server/execution/order-router.js - Client action handler
server/execution/message-handler.js - Exit management
server/execution/exit-pass.js
Portfolio and intelligence
- Portfolio Pilot
server/execution/pilot-handler.js - Market intelligence
server/intelligence/dashboard-intel.js - Notifications
server/execution/notifier.js - External holdings
server/execution/external-holdings.js
Server access
- HTTP and WS hub
server/server.js - Access control
server/security/auth-gate.js
Other components
- Trader
- Broker services
Connections 27
- Trader → Terminal shell: uses
- Terminal shell → HTTP and WS hub: requests and streams
- HTTP and WS hub → Access control: guards access
- HTTP and WS hub → Terminal shell: serves and broadcasts
- Terminal shell → Opportunities: routes views
- Terminal shell → Portfolio views: routes views
- Terminal shell → Trade tickets: routes views
- HTTP and WS hub → Trading pipeline: starts
- Trading pipeline → Broker connectors: reads feeds
- Trading pipeline → Market strategies: generates candidates
- Trading pipeline → Risk engine: gates candidates
- Trading pipeline → Trade ledger: stages trades
- Trading pipeline → Exit management: manages exits
- Trading pipeline → Notifications: notifies
- Broker connectors → Broker services: requests market and broker data
- Broker connectors → Price and session data: provides prices
- Client action handler → Order routing: routes intents
- Order routing → Trade ledger: records fills
- Order routing → Broker services: submits live orders
- Order routing → Risk engine: checks sizing basis
- HTTP and WS hub → Client action handler: routes client messages
- HTTP and WS hub → Portfolio Pilot: publishes pilot state
- Portfolio Pilot → Trade ledger: stages and syncs actions
- Portfolio Pilot → Risk engine: gates pilot trades
- HTTP and WS hub → Market intelligence: publishes snapshots
- Market intelligence → Price and session data: reads market context
- HTTP and WS hub → External holdings: serves holdings state