Author with Visual Composer

Build a Strategy without code

Visual Composer is Arizmic's no-code Strategy authoring surface. Use it to define supported inputs, conditions, entries, exits, position handling, and risk rules visually, then save a versioned Strategy for validation.

Open Strategies -> Composer to start a new Strategy. Select a Composer Strategy in Strategy Library and choose Edit to create an intentional update. Python plugin Strategies stay owned by their source code and are not edited in Composer.

Start with the decision

Give the Strategy a clear name and stable ID, then decide what it is allowed to do before adding conditions:

• which market fields or exact Signal outputs it reads;
• when a decision is evaluated;
• whether it may go long, short, or both;
• what opens and closes a position;
• how conflicting long and short signals are handled; and
• what risk and execution requirements the rule needs.

Composer is not a backtest form. It defines the Strategy; the Dataset, time window, estimates, and queueing are selected later in Studies.

Add inputs and conditions

Add an Input for each market field or Signal output the Strategy needs. Choose a Signal output by its exact name and version, not by a familiar display name alone. Give each input a meaningful local label so conditions stay readable.

Build conditions from those inputs and parameter values. A condition should answer one clear question, such as whether close is above a reference or a Signal state is true. Keep timing explicit: do not write a rule that relies on information unavailable at the decision point.

If Composer cannot express the rule with its supported controls, use the Strategy SDK rather than forcing an approximate visual rule.

Define entries, exits, and risk

Use the rule sections to connect conditions to outcomes:

• Entry rules state when a Long or Short position may open.
• Exit rules state when an open position should close.
• Position rules set the allowed directions and conflict behavior.
• Risk records the supported risk inputs and boundaries for the Strategy.

Write every major behavior explicitly. A Strategy with an entry but no intended exit or position policy may be structurally incomplete even if one condition looks correct.

Review and save

Composer shows validation issues near the affected part of the draft. Resolve errors before saving; warnings deserve a deliberate decision rather than being treated as decoration.

Saving creates a versioned Strategy definition. It does not run a Study, build Signal outputs, or establish that the Strategy will work with every Dataset. Use undo and redo while designing, and inspect saved versions before restoring an earlier one.

Create the next research step

Once the saved Strategy is structurally ready, choose Create Study to carry it into Study Design. There, select the Dataset and window, resolve actual Signal and Prepared Data requirements, review estimates, and queue work.

Practical checks

Before saving, ask:

1. Does every input have a clear source, type, and timing?
2. Are parameters bounded and named by their real unit?
3. Can you explain each entry and exit in one plain-English sentence?
4. Does the position and conflict policy match the intended behavior?
5. Have you written risk behavior rather than assuming it is implied?
6. Are the selected Signals and data requirements realistic for the Study you plan to create?

For no-code help shaping a rule before you enter it, use Author with AI Companion.