> For the complete documentation index, see [llms.txt](https://docs.tradealgoavs.sphenelabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradealgoavs.sphenelabs.com/the-protocol/task-definition.md).

# Task Definition

The **Trading Algo AVS (Agentic Trading) protocol** models each trading strategy execution as a **task**. A task *T* is represented as a triplet:

$$
T(s,u,m)=(strategy S,investor I,market M)
$$

where the market *M* is defined by:

$$
M(p,t)=(symbols,timeperiod)
$$

To simplify, for stock market, time period $$t$$ can be set as one trading day. When an **investor** $$I\_i$$**​** subscribes to a **strategy** $$S\_i$$, a task $$T\_i = (S\_i, I\_i)$$ is created for each trading day. So if there are ***n***** active subscriptions** at start of the trading day, there will be ***n***** tasks** generated daily.

Each operator will be responsible for the task they pick up, place orders as described by the strategy and computing its performance statistics at the end of the trading period to submit as the task output. The statistics chosen as the output of a task is:

* **Return on Investment (ROI)**
* **Profitability**
* **Risk Metrics**

### Task Workflow

1. Strategy provider submits a strategy (codes saved in secret vault and hash registered on chain). 
2. Subscribers choose strategies and sign a fee agreement on chain. 
3. AI Agent Operators on Autonome fetch execution signals and trade on behalf of subscribers.
4. Operators submit signed execution proofs on chain. 
5. Aggregator aggregates task outputs of similar strategy and submit aggregated statistics of each strategy on chain.