Adapt a strategy to the instrument before reusing it

Reusing a strategy across instruments requires reviewing the instrument's identity, supported market scope, and execution constraints. A familiar price pattern does not make two contracts interchangeable. We would adapt the mandate and confirm supported settings before judging how the model behaves on the new instrument.

DXAP's settings reference describes core markets, HIP-3 markets, and selected HIP-3 DEX scope where available. The market selector supplies supported symbols. This is current Hyperliquid alpha documentation inspected October 3, 2026; it establishes no spot-market capability.

Porting a BTC rule to another contract

Illustrative scenario: an owner copies a BTC breakout strategy to a HIP-3 contract with a different underlying exposure. The original strategy says “trade around crypto news,” uses a familiar shorthand symbol, and assumes the same leverage choice.

Begin with economic identity. What does the new contract reference, and which events plausibly change its value? A crypto-specific catalyst clause may become irrelevant. Next establish the supported symbol and DEX scope. A name that resembles the desired asset can refer to a different instrument, or be unavailable in the selected market universe.

Then review order constraints. October 3 release notes state that opening orders require known exchange maximum leverage and reject requests above it before submission. Missing leverage metadata is reported as unavailable. That supports an operational check, rather than an assumption that a leverage number copied from another market will work.

Preserve intent while changing assumptions

Keep the original decision objective visible. If it was a completed-window trend entry, retain that criterion while adapting the evidence window and instrument-specific event research. If it was exposure to a particular economic event, verify that the new contract expresses the desired exposure at all.

Notional remains exposure in USD terms, rather than margin or maximum loss. A fixed dollar entry limit can carry different risk across instruments with different volatility and liquidity. Review whether the same bound is appropriate, and distinguish a proposed risk adjustment from a measured improvement.

Our harness transfer article explains why shared architecture still needs transfer evidence. The execution article describes the separate confirmation required after a proposed action reaches the venue.

Test the transferred rule against a failure case

Ask what the adapted strategy should do when the symbol is unsupported, required metadata is missing, or catalyst evidence concerns the wrong underlying. The expected answer should preserve the mandate's boundaries and identify the missing prerequisite.

Review the saved market permissions after approving an adaptation. They should agree with the written instrument scope. Later records should identify which version and instrument were active, so a rejected entry does not become a false story about predictive weakness.

A successful portability review produces a clear statement of the new contract, relevant evidence, and permissible exposure. Whether that transferred strategy has economic value remains an empirical question requiring an appropriate outcome record.