1. Prepare the universe
Use Tickers, Watchlists, Market Data, and Charts to define what the system is allowed to observe.
Operator manual
How to use Alpha Wing
A practical guide for setting up the workspace, routing signals, validating strategies in paper mode, monitoring operations, and reviewing what happened.
Overview
What Alpha Wing is for
Alpha Wing is an account-aware automated trading workspace. It brings signal intake, market data, strategy design, paper and live account monitoring, risk controls, reporting, notifications, and audit history into one operating surface.
Every trading view identifies the selected account and environment. Use it to answer the important questions: what signal arrived, which account received it, what rule accepted it, what order was attempted, what exposure changed, and what record proves it.
Quick start
Recommended first setup
1
Create a workspace and sign in.
2
Add or import ticker symbols, then group them into watchlists.
3
Sync or review market data coverage for the symbols you care about.
4
Connect paper or live account records and store provider credentials in the encrypted vault.
5
Build a strategy or trade plan, preview the behavior, and submit it for approval when needed.
6
Select an account, monitor its orders, fills, and positions, then review account-scoped reports and notifications.
Core workflow
The operating loop
2. Design the decision logic
Use Strategy Builder and Trade Plans to describe entry rules, exits, allocation, schedule, and risk behavior.
3. Route signals safely
Use Webhooks or internal previews to capture alert payloads, inspect them, replay them, and keep the signal history visible.
4. Monitor execution
Use Trading, Orders, and Positions to see account-specific order intents, fills, exposure, P&L, and reconciliation events.
5. Review and report
Use Notifications, Queue Monitor, Reports, P&L Log, and Audit to understand what happened and who changed what.
Module guide
What each page does
Page
Purpose
How to use it
Dashboard
Account performance, workspace status, and operational readiness.
Start here to choose a paper or live account and review its balances, positions, and activity.
Market Data
Historical bars, provider readiness, sync status, and coverage.
Check whether symbols have usable data before relying on a strategy preview or deployment.
Tickers
Symbol records, aliases, imports, and watchlists.
Create the tradable universe and map provider-specific ticker aliases.
Accounts
Paper and live account state, connection health, and provider readiness.
Review broker or data-provider connection status before routing signals.
Credential Manager
Encrypted API keys, tokens, and service credentials.
Store secrets once, reveal only when necessary, and revoke credentials that should no longer be trusted.
Trading
Paper and live account balances, order records, fills, positions, and snapshots.
Switch accounts explicitly and keep paper and live broker credentials isolated.
Orders
Order intents, fills, broker state, rejects, and reconciliation events.
Investigate what the system attempted, what filled, what failed, and why.
Positions
Open exposure, unrealized P&L, allocation, snapshots, and flatten controls.
Monitor concentration per account and use only the controls supported by that account provider.
Strategy Builder
Versioned strategy rules, allocation controls, previews, signals, and approvals.
Create or update automation logic and inspect expected behavior before deployment.
Trade Plans
Reusable automation templates with rules, schedules, risk, and strategy combinations.
Package strategy logic into a repeatable plan that can be reviewed and reused.
Deployments
Environment-specific deployment controls, pause/resume, flatten, stop, evaluation, and event logs.
Bind approved strategies to the matching paper or live account and review runtime events.
Webhooks
Inbound external alerts, endpoint secrets, subscriptions, message replay, and signal capture.
Connect TradingView-style alerts or other JSON senders to Alpha Wing.
Notifications
Delivery channels, open alerts, notification history, and test dispatch.
Control how operators are informed about important system events.
Reports
Workspace reporting and CSV or JSON export history.
Create audit-ready snapshots for paper performance, system activity, and review.
Queue Monitor
Jobs, workers, durable tasks, schedules, failed jobs, and trading operations.
Inspect background work and run due tasks when monitoring automation behavior.
Settings
Risk limits, paper execution limits, symbol lists, and automation locks.
Set workspace-level boundaries before any strategy or deployment is trusted.
Team Management
Members, invites, and roles.
Control who can access the workspace and what responsibilities they hold.
Audit
Security, settings, automation, and trading-decision history.
Review account changes and trading-ops events when you need accountability.
Webhook signals
Connecting external alerts
Webhooks are the bridge between an external alert platform and Alpha Wing. Treat each webhook message as evidence first, then replay or route it only when you understand the payload and the risk context.
Create or reveal an endpoint secret in Webhooks.
Configure the external alert sender to POST JSON to the Alpha Wing webhook endpoint.
Include a clear symbol, side, intent, strategy name, and any sizing or risk context your plan expects.
Send a test alert and confirm the message appears in Webhooks before trying to replay or route it.
Use replay only when you intentionally want to test the same payload again.
Rotate or revoke endpoint credentials if a secret is exposed.
Daily operations
A simple operating rhythm
Morning check: review Dashboard, Queue Monitor health, Notifications, and Market Data coverage.
Pre-trade check: confirm Settings limits, paper mode, account state, and strategy approval status.
During simulation: watch Webhooks, Orders, Positions, and Deployments for rejects or unusual exposure.
End-of-day review: export Reports, update the P&L Log if needed, and inspect Audit for operator changes.
Safety model
Paper mode is the default trust boundary
The system is built to make automation inspectable before it becomes powerful. Use paper execution, risk settings, audit records, and reports as gates before expanding any operational responsibility.
Paper and live accounts are selected explicitly and their figures are never combined.
Live execution depends on connected-broker support and workspace safety approval.
Credentials are handled through the vault instead of scattered through page forms.
Risk guardrails live at the workspace level so strategies inherit common boundaries.
Audit and reporting records should be used before promoting any automation process.
Troubleshooting
Common issues and first checks
A webhook alert does not show up.
Check the endpoint URL, secret, HTTP method, JSON payload shape, and whether the endpoint was revoked.
A strategy preview looks empty.
Confirm symbols exist, aliases are mapped, market data coverage is available, and the rule window has enough historical bars.
A paper order is rejected.
Review Orders for reject details, then check Settings, account buying power, symbol status, and deployment risk limits.
Notifications are missing.
Check channel status, test the channel, review open alerts, and inspect delivery history for errors.
Background tasks appear stale.
Open Queue Monitor, check failed jobs and worker health, then run due tasks or review process logs.