Docs / requirements
Check your setup.
These are evaluation notes, not installation instructions. Customer setup guides and a tested compatibility matrix will accompany the release details.
Core
The local operating layer for an agent-driven trading system.
A Mac, an agent environment such as Codex, Claude Code, or OpenClaw, an Alpaca account with permission to connect, and your own strategy, risk rules, and activation decisions.
No supplied trading advice, agent/model service, broker account, or guaranteed returns. Relay is optional.
Read Core requirements →Studio
The human-readable workspace for inspecting Core strategies, tests, and execution.
Your own computer and agent. Customer installation steps and the tested agent, operating-system, broker, and data-provider matrix have not been published.
No managed execution, supplied trading strategy, or guarantee of returns. The preview does not grant paper or live trading access.
Read Studio requirements →Relay
The optional paid companion to TradeAssembly Core: monitor, retain, and reach.
A compatible local TradeAssembly Core installation. Exact supported versions and customer connection steps have not been published.
No hosted trading runtime. Relay cannot keep a sleeping computer running or confirm an action that the runner has not acknowledged.
Read Relay requirements →NeedleMap
Inspect the mechanics of Pine Script source.
Pine source you possess and have the right to analyze. Customer access and supported-browser details will be published with the offer.
No backtesting, broker connection, TradingView integration, fill verification, or profitability assessment. It is a separate product, not a required Studio step.
Read NeedleMap requirements →Start with Core
You bring a Mac, an agent environment such as Codex, Claude Code, or OpenClaw, an Alpaca account and permission to connect it, and your own strategy and risk rules. Relay is optional. The public installation package, license, and tested compatibility guide are being prepared.
Core setup and release status →Inspect an example
Core in Studio: draft, evaluate, and inspect paper settings. The data and activity are simulated; nothing is submitted to a broker.
Relay: last report, missing heartbeat, and request acknowledgment. The companion screen is a design preview.
NeedleMap: source-linked conditions, state, and timing. Read the analysis methodology.
Before you run anything
A saved draft is not an activation. A historical evaluation is not a live result. A paper record is not a real fill. Review the exact strategy version, execution settings, permissions, and connection state before authorizing your own system.
Review costs and availability →