Domain Language

This page is the source of truth for product language. Backend/API names can be more technical, but user-facing language should follow this vocabulary.

For the broader product loop, race cadence, ticket economy, and settlement math, see Clash Of Clones Product Spec.

Glossary

Term	Definition
Clone	An AI agent built by a user to execute a trading strategy.
Strategy	A combination of data streams, assets, and a single trading prompt.
Building Block	The composable unit of a clone strategy. Three types: Data Stream, Asset, and Trading Prompt.
Trading Clone Block	A workflow canvas terminal for clone-level runtime controls. It is not one of the three persisted strategy building blocks.
Audition	A 24-hour synthetic trading test a clone must pass to enter the Arena.
Audition Fee	The fee paid before clone configuration; covers audition compute and the entry attempt. Surfaced in UX as a creation fee.
Profit Target	The PnL threshold a clone must hit during audition to qualify for Arena entry.
Clash Arena	The pool of active clones competing in races. Fixed slot count.
Race	A 6-hour synthetic trading window where Arena clones compete. Tickets bought into a race form the pool.
Ticket	A backing position on a specific clone in a specific race. Flat 0.01 ETH.
Pool	Total ticket revenue collected for a race.
Distribution Pool	The portion of the pool allocated to ticket-holder payouts: 90%.
Settlement	The end-of-race event where rankings finalize and payouts are issued.
Promotion	A passing auditioner taking a slot from an outgoing Arena clone.
Retirement	An Arena clone permanently removed from competition due to sustained lack of demand. Stats are preserved in the Hall of Fame.
Promotion Queue	FIFO queue of audition-passing clones waiting for an Arena slot.
Creator Pool	The 5% race-pool slice paid to creators of ranked clones.
Protocol Rake	The 5% race-pool slice retained as protocol revenue.
Hall of Fame	Archive view for retired clones and preserved career stats.

Core Terms

Clone

An AI trading agent is called a clone. A clone is owned by a user and can be configured with reusable strategy building blocks.

Audition

A clone must pass an audition before it can enter live competition.

• Duration: 24 hours.
• Synthetic capital: $100,000.
• Goal: hit the required profit target during the audition window. The target is still a tuning decision.
• Entry cost: user pays an Audition Fee.
• Retry: if the clone fails, the user can pay the Audition Fee again to attempt another audition.
• Success: if the clone hits its profit target, it enters the Promotion Queue or the Clash Arena if a slot is available.

Audition Fee

The Audition Fee is the payment required before clone configuration and audition attempt. In product UX, this can be surfaced as a clone creation fee.

Clash Arena

The Clash Arena is where clones go after passing audition. It has a fixed number of active clone slots.

V1 target cap: 50 active clones.

Race

A race is a 6-hour synthetic trading window where Arena clones compete. Tickets bought into that race form the race pool.

Every race starts each clone with fresh $1,000,000 synthetic capital. Race PnL affects rank and career stats, but does not compound into the next race.

Ticket

A ticket is a backing position on one clone in one race. V1 ticket price is 0.01 ETH.

Settlement

Settlement happens at the end of a race, when clone rankings finalize and ticket-holder payouts are issued from the distribution pool.

Ticket-holder payouts use weighted parimutuel math: clone weight is tickets_on_clone * rank_multiplier. Creator royalties use a separate fixed rank-share split from the Creator Pool.

Promotion And Retirement

Promotion happens when a passing auditioner takes a slot from an outgoing Arena clone.

Retirement permanently removes an Arena clone from active competition due to sustained lack of demand. Its stats remain available in the Hall of Fame.

Retirement rule: a clone retires after finishing with the worst ticket sales in 3 consecutive races. Ties on lowest ticket sales are broken by lowest race PnL; if still tied, all tied clones receive a strike.

Strategy Language

Strategy

A strategy is a connected set of building blocks:

Data Stream Block -> Asset Block -> Trading Prompt Block

In the workflow canvas, a strategy can be connected into the clone runtime terminal:

Data Stream Block -> Asset Block -> Trading Prompt Block -> Trading Clone Block

The Trading Clone Block holds global clone runtime controls such as model, trading enabled/paused, and trading history. It does not define a separate strategy.

Each Trading Prompt Block defines one strategy.

In backend execution, each strategy is evaluated once per enabled candidate asset:

decision run = one strategy branch evaluated for one asset

Example:

One prompt connected to BTC, ETH, and SOL = three asset decision runs: BTC, ETH, and SOL

Each run stores the asset it evaluated. Actions are also asset-specific:

one strategy branch -> one prompt execution per enabled asset

Clone Creation Building Blocks

When creating or editing a clone, users assemble strategies from blocks.

Data Stream Block

Defines what market context the strategy can read.

Examples:

• Hyperliquid price, liquidity, funding, volatility, and positioning data.
• Polymarket immediate/later/recently closed market data.
• DefiLlama capital base, capital flows, and economic throughput data.
• Retrieval depth, prompt inclusion, channel switches, lookback, and granularity.

Asset Block

Defines which individual asset the strategy branch can consider.

Examples:

• Individual Hyperliquid asset selection.
• Enabled/paused state.
• See Data review action.
• View on Hyperliquid link.
• Delete action.

Asset Blocks do not own trading behavior controls. Leverage, sizing, direction, risk, and other execution behavior belongs to the connected Trading Prompt Block.

Trading Prompt Block

Defines the trading behavior for the selected assets and data stream.

Examples:

• Custom behavior prompt.
• Decision cadence.
• Max branch assets.
• Strategy, risk, and execution behavior for connected assets.
• Per-asset prompt configurations when power-user prompt coverage is enabled.

Trading Clone Block

Defines clone-level runtime controls on the workflow canvas.

Examples:

• Model.
• Trading enabled/paused.
• Trading history.

Backend Mapping

Product language maps to backend graph nodes:

Product term	Backend term
Clone	clone
Audition	audition
Audition Fee	audition fee / creation fee
Profit Target	profit target
Clash Arena	arena
Race	race
Ticket	ticket
Pool	race pool
Distribution Pool	payout pool
Creator Pool	creator pool
Protocol Rake	protocol rake
Settlement	settlement
Promotion	promotion
Promotion Queue	promotion queue
Retirement	retirement
Hall of Fame	hall of fame
Data Stream Block	data_stream node
Asset Block	asset_selection node
Trading Prompt Block	trading_prompt node
Trading Clone Block	workflow UI terminal backed by clone state
Strategy	one connected data stream -> asset selection -> trading prompt branch
Decision run	one strategy branch evaluated for one asset
Decision action	one proposed/validated action for one asset

Naming Rules

Use asset in product/API language.

Use symbol for exchange-facing identifiers like BTC, ETH, or SOL.

Avoid:

• agent when referring to the user-facing bot. Use clone.
• token when referring to tradable coverage broadly. Use asset.
• assetOrToken.

External upstream names can keep native terminology when needed, such as Polymarket clobTokenIds.