Product Controls

This page captures the current product decision for clone controls and strategy building blocks.

Related:

• Clash Of Clones Product Spec
• Domain Language
• Backend Contract

Product Surface Map

The strategy builder is one part of the larger clone lifecycle:

Pick model/capacity -> pay Audition Fee -> public identity -> private strategy -> audition -> Arena

The product has two distinct user-facing configuration surfaces:

Surface	Purpose	Primary owner
Public identity	Name, description, image, model tier, public assets/data streams	Product/profile UI
Private strategy	Data streams, assets, trading prompt, cadence, execution behavior	Strategy builder and trading runtime

The private strategy is visible only to the creator. Public identity and selected capability signals are visible to backers on clone cards, race views, and Hall of Fame.

Clone Creation Payment Controls

Before strategy configuration, users choose model tier and asset capacity. These determine the Audition Fee.

Model tier	1-3 assets	4-6 assets	7-10 assets
Haiku	0.01 ETH	0.015 ETH	0.02 ETH
Sonnet	0.02 ETH	0.03 ETH	0.04 ETH
Opus	0.04 ETH	0.06 ETH	0.08 ETH

Creation caps:

• Data streams: max 5 per clone.
• Assets: max 10 per clone.
• Trading prompt: product cap is 1 prompt per clone in the current Clash spec, max 4,000 tokens.
• Runtime expansion: one strategy execution per selected asset per due tick.

The backend graph and power-user docs can continue supporting multiple Trading Prompt Blocks for compatibility and future expansion. The current product creation flow should expose one prompt unless the spec changes.

Public Identity Controls

Clone identity is a first-class backer-facing surface:

• Name: required, max 32 characters, unique across active Arena clones.
• Description: required, max 280 characters.
• Image: required, 512 x 512, PNG or JPG, max 1 MB.
• Model tier badge: Haiku, Sonnet, or Opus.
• Public asset selections.
• Public data stream selections.

Name, description, and image must pass moderation before audition begins. Failed moderation does not refund the Audition Fee; the creator edits rejected fields and resubmits.

During race accumulation, clone cards should visually prioritize:

1. Image and name.
2. Description.
3. Model tier badge.
4. Career 1st-place count.
5. Career top-10 rate.
6. Current streak.
7. Last-race finish.
8. Total tickets sold for this race and top backer concentration.

Current Workflow Shape

The persisted strategy graph has three block types:

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

The workflow canvas also shows a visual terminal block:

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

The Trading Clone Block is not a strategy block. It holds clone-level run controls such as model, trading on/off, and trading history. Its canvas position and visible prompt-to-clone connection are saved as layout metadata so the workflow reopens in the same shape without turning the clone block into an executable graph node.

Each Trading Prompt Block defines one strategy. At runtime, the backend expands that strategy across the connected assets:

one strategy branch -> selected assets -> one decision run per due asset

Control Granularities

All modes save to the same backend graph shape. The difference is how much of that graph the user sees.

Mode	User-facing shape
Basic	Generated graph with simple defaults
Custom	Same graph with per-asset/source presets exposed
Power User	Direct graph editing with advanced source and prompt controls

Basic - Simple Defaults

Basic users should not need to understand the graph.

• One generated Hyperliquid Data Stream Block.
• One or more generated Asset Blocks from category or symbol selection.
• One generated Trading Prompt Block.
• One Trading Clone Block for global model and trading on/off.
• Retrieval depth defaults to Balanced.
• Prompt behavior can use a short custom behavior prompt.
• No manual channel, lookback, granularity, datapoint, leverage, or risk guardrail tuning.

Custom - Per-Asset Presets

Custom users can choose assets and tune broad behavior without editing raw retrieval settings.

• Drag or select individual Asset Blocks.
• Attach one Data Stream Block per source family to an Asset Block.
• Choose retrieval depth: Fast, Balanced, or Deep.
• Choose source-level prompt inclusion: Off, Auto, Standard, or Required.
• Enable or pause each asset.
• Edit trading prompt cadence, max branch assets, custom behavior prompt, and execution behavior.
• Use the Latest Data viewer to inspect what the connected streams return for an asset.

Power User - Direct Graph Editing

Power users can edit the strategy graph directly.

• Create/delete Data Stream, Asset, and Trading Prompt Blocks.
• Connect multiple strategy branches.
• Use multiple source-family blocks, with at most one of each source family connected to the same Asset Block.
• Open advanced channel controls for channel-level switches, prompt inclusion, lookback, and granularity.
• Keep Asset Blocks limited to asset identity, enabled/paused state, latest-data review, and exchange links.
• Use global prompt behavior, global prompt with per-asset overrides, or asset-specific-only prompt coverage when the backend/UI exposes those controls.
• Configure strategy, risk, and execution behavior on Trading Prompt Blocks.

Control Organization

Data Stream Controls

Data Stream Blocks answer:

What structured market memory should this asset make available to the prompt?

Current user-facing source families:

• Hyperliquid.
• Polymarket.
• DefiLlama.

Current top-level controls:

• Retrieval depth: Fast, Balanced, or Deep.
• Prompt inclusion: Off, Auto, Standard, or Required.

Current advanced channel controls:

• Channel enabled/disabled switch.
• Channel-level prompt inclusion override.
• Lookback.
• Granularity.

Max datapoints and prompt budget are managed automatically from lookback and granularity. The UI can show the derived datapoint cap, but users should not need to tune it directly in the default flow.

Retrieval is deterministic. There is no AI prompt for data retrieval.

Asset Controls

Asset Blocks answer:

Which individual asset is this strategy branch allowed to consider?

Asset selection is individual in the workflow canvas. The palette can still be organized by Hyperliquid categories and subcategories:

• High-level categories: All, Perps, Spot, Crypto, Tradfi, Trending.
• Crypto subcategories: AI, Defi, Gaming, Layer 1, Layer 2, Meme.
• Tradfi subcategories: Stocks, Indices, Commodities, FX, Pre-IPO.
• Optional spot subcategories: USDC, USDH, USDT.

Generic HIP-3 category exposure is out of scope.

Current Asset Block content:

• Asset display name, exchange symbol, and asset kind.
• Enabled/paused switch.
• See Data viewer button.
• View on Hyperliquid link.
• Delete block action.

Asset Blocks do not expose leverage, position sizing, trade direction, or risk tuning. Those controls belong to Trading Prompt Blocks so the prompt owns trading behavior for every connected asset. Compatibility-only backend defaults can remain on asset nodes until the storage schema is migrated.

Trading Prompt Controls

Trading Prompt Blocks answer:

How should the clone decide what to do for each due asset?

Current visible controls:

• Decision cadence.
• Max branch assets.
• Custom behavior prompt.
• Strategy, risk, and execution behavior for connected assets.

The old trader archetype, market momentum sensitivity, and analysis timeframe controls are legacy migration inputs. They can still exist in compatibility data paths, but they are not the primary workflow controls in the current strategy builder.

Trading Clone Controls

The Trading Clone Block answers:

What global runtime settings apply to the clone?

Current visible controls:

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

The model is clone-level, not per Trading Prompt Block.

The prompt-to-clone connection is a visual runtime route. It should remain visible in the canvas and round-trip through pipeline layout metadata, but it is not part of the executable v1 graph that the backend compiler validates.

Data Review UX

Each individual Asset Block should expose a Latest Data action.

The viewer should be a side drawer, not a blocking modal, so users can keep the canvas visible while tuning the graph. It should show the exact structured memory reads that the decision context resolver would feed into the trading prompt:

• Source and channel.
• Lookback and granularity.
• Required flag.
• Derived max datapoints.
• Row count.
• Latest compact records.
• Warnings when the asset is not connected through a complete branch.

This keeps data review tied to the actual strategy configuration instead of creating a separate database-browser mental model.

For DefiLlama, the viewer should not imply exhaustive per-token source coverage. The resolver returns global DeFi context across the configured lookback, plus chain rows whose tokenSymbol matches the asset and stablecoin rows whose subject matches the asset symbol.