Deployments

What Deployments is for

Deployments is where you prepare and manage the exact Strategy Configuration or Portfolio version that may operate through Live. A deployment binds the source to a mode, provider environment, account, instruments, capital, position sizing, and a risk profile.

Saving a deployment does not start it. The deployment must pass its current readiness checks before Arm becomes available.

Choose the operating mode

The available modes depend on the selected provider and its current certification:

• Shadow evaluates the deployed logic and records decisions without submitting orders.
• Paper submits to an eligible Arizmic or provider Paper environment.
• Live submits to a certified real-money environment.

Local Paper and provider Paper test different boundaries. Local Paper provides a controlled Arizmic execution environment. Provider Paper also tests the provider's account, instruments, order lifecycle, streams, snapshots, and reconciliation behavior. Neither guarantees the liquidity, queue position, latency, or fills of a real market.

An unavailable mode stays disabled with its blocker. A provider appearing in the workstation does not by itself prove that its Paper or Live route is certified.

Prepare the source

Select an immutable source rather than an editable draft:

• a saved Strategy Configuration with its exact Strategy version and parameters; or
• a supported saved Portfolio version with its exact member Configurations and policy.

Strategy and Portfolio use the same deployment lifecycle. Portfolio is not a separate provider or a second Live product. When Portfolio operation is supported, the runtime retains both the coordinated account result and the member identity behind each decision, order, fill, position, and risk action.

If the selected source changes, create or explicitly update the deployment and review readiness again. Live never silently replaces the source with its newest version.

Configure Broker Connections first

Create credentials and test provider connectivity under System & Jobs -> Broker Connections. Live consumes that approved connection; it does not duplicate credential setup.

Before using a connection, confirm its exact:

• provider and environment;
• account identity and permissions;
• market-data and order capabilities;
• certification status and freshness; and
• available broker instruments.

In the deployment editor, select the connection and bind each source instrument to the exact broker instrument. Confirm venue, asset type, currency, contract, quantity units, and entitlements. A matching ticker alone is not a safe binding.

Create a deployment

Select New Deployment, then complete the editor in order.

1. Under Source, name the deployment and choose Strategy Configuration or Portfolio.
2. Select the exact saved source and version.
3. Under Mode, choose an available Shadow, Paper, or Live route.
4. Under Market & Account, select the connection and exact broker instrument.
5. Add only the warm-up events required by the deployed logic.
6. Under Position Sizing, choose the capital basis and sizing method.
7. Select an acknowledged Risk Profile.
8. Read every item under Review, then save only when the validation state is Ready.

The capital basis can use connected-account equity or isolated virtual equity where the selected mode supports it. Sizing can use fixed quantity, fixed notional, or risk per trade when the source and risk profile provide the inputs required by that method.

Understand Portfolio readiness

A Portfolio deployment adds coordinated checks before any member intent reaches the order boundary. Readiness must establish:

• the exact Portfolio version and member Configurations;
• shared capital and reservation rules;
• deterministic priority and conflict handling;
• Portfolio-level exposure, drawdown, flatten, and kill behavior;
• member and Portfolio attribution; and
• restart and reconciliation behavior that cannot duplicate submission.

An unknown member, order, fill, position, allocation, or reconciliation state closes order entry. Evidence from Arizmic Paper does not automatically certify the same Portfolio on an external provider.

Read the Deployments table

Each row identifies the deployment name, Strategy or Portfolio source, instrument, mode, account, runtime state, risk profile, and last activity. Use Open in Monitor to operate the selected deployment or Edit to review its frozen configuration.

The table may separate normal operator deployments from development drills. A development drill is not a production-ready deployment and must remain visibly labeled.

Edit or archive safely

Editing a deployment creates a new reviewed configuration revision. Revalidate the source, bindings, sizing, and risk profile before arming it again.

Archive only when the deployment is inactive and its retained history remains reachable. An active session, open order, position, unresolved mutation, or reconciliation blocker must prevent removal and explain the corrective action.

When readiness is blocked

Use the reported blocker rather than trying alternate values at random. Common causes include:

• unavailable or uncertified mode;
• stale provider certification, credentials, session, or market data;
• unresolved account or instrument identity;
• unsupported source, order, quantity, or fidelity requirement;
• missing or unacknowledged risk profile;
• incomplete Portfolio coordination semantics; or
• an earlier order or reconciliation state that still carries risk.

Fix the owning condition, refresh the deployment review, and confirm the exact source revision before trying again.