Strategies Overview

The strategies module is a metadata registry for strategy definitions. It does not place orders, deploy bots, or run code. A separate executor process reads from the registry — the executor binding is captured by the bot_name field on each strategy.

Resource shape

Field	Type	Notes
id	integer	DB-assigned, auto-increment.
name	string	Human-readable label, unique per platform.
author	string | null	Free-form author tag.
description	string | null	Free-form description.
entry_condition	string | null	Free-form text — typically a DSL or natural-language description consumed by the executor.
exit_condition	string | null	Free-form text, same as above.
bot_name	string | null	Reference key linking this strategy to an executor instance.
created_at	string (ISO 8601)	Creation timestamp.
updated_at	string (ISO 8601)	Last modification timestamp.

Endpoints

Method	Path	Purpose
POST	/strategies	Create a new strategy
GET	/strategies	List all strategies
GET	/strategies/{strategy_id}	Get one strategy
PUT	/strategies/{strategy_id}	Update editable fields (not name)
DELETE	/strategies/{strategy_id}	Delete a strategy

All five endpoints are public (no auth header).

What this module does not do

• Deploy or pause execution. (No deploy / pause endpoints exist.)
• Stream live status. (No WebSocket exists.)
• Validate entry_condition / exit_condition content — they are stored as opaque strings.
• Paginate GET /strategies — the response is the full list ordered by created_at desc.