@tradejs/strategy-relative-rotation
v3.0.5
Published
BTC-relative rotation strategy using alpha, ratio trend, benchmark regime, correlation, volatility, and volume filters for TradeJS.
Maintainers
Readme
@tradejs/strategy-relative-rotation
TradeJS strategy plugin providing RelativeRotation.
Strategy overview
RelativeRotation trades an asset's rotation against BTC rather than its
absolute trend alone. It combines 24-hour alpha and ratio returns,
short-horizon relative strength, ratio trend, benchmark regime, ADX,
correlation, volume, and volatility filters before sizing ATR-based risk.
Logic at a glance
Signal on an example chart
The cyan asset series separates from normalized BTC as excess return, price ratio, and short-horizon relative strength align into a positive rotation.
The illustration is schematic, not market data. Exact thresholds, confirmation rules, and risk parameters come from the active TradeJS strategy config.
Install
yarn add @tradejs/strategy-relative-rotationRegister the package in tradejs.config.ts:
import { defineConfig } from "@tradejs/core/config";
export default defineConfig({
strategies: ["@tradejs/strategy-relative-rotation"],
});The package exports strategyEntries for the TradeJS plugin loader together
with its strategy definitions, manifests, default configs, and public AI/ML
adapters. Strategy implementation changes are released from this repository,
independently of the TradeJS engine.
Development
yarn install --immutable
yarn checksPublishing is beta-first and delegated to the pinned
TradeJS-Workflows@v1 reusable workflow. A relevant push publishes a unique
prerelease and moves the npm beta tag only after the repository checks pass
and the published tarball imports successfully in a clean npm consumer. The
current verified beta is promoted to one stable latest
release by the weekly automation; production never consumes prereleases.
Keywords: ai, claude, codex.
Runtime host contract
All @tradejs/* runtime packages are peer dependencies. The consuming TradeJS Project owns their exact installed versions and package manifest, so this package never loads a hidden nested engine, types package, indicator package, or Strategy Kit. Repository builds use matching dev dependencies only.
