AuraQuant

Use whenever the task is to fetch, backfill, sync, repair, slice, inspect, or featureize AuraQuant CTA market data. Trigger on requests about OHLCV history, gap filling, data versions, data slices, feature slices, or local data storage layout.

Use whenever the task is to run CTA experiments, inspect eval reports, compare results, or turn structured backtest/evaluation output into the next research decision in AuraQuant.

Use whenever the task is to inspect archive lineage, write candidate records, request freeze transitions, resolve approvals, or advance CTA strategy lifecycle state in AuraQuant. Trigger on candidate, frozen, production, deprecated, archive, lineage, or approval requests.

Use whenever the user wants to advance CTA research in AuraQuant, asks what the next step is, wants the agent to take over the overall research loop, or needs a cross-stage decision spanning data, specs, runtime modules, experiments, evaluation, and archive governance.

Use whenever the task is to define or update CTA runtime modules or specs in AuraQuant, including baseline/filter/execution/risk code under cta_runtime, spec persistence, runtime validation, and first-run assembly with default modules.

Use for CTA research inside Aura when the task is to inspect archived runs, review evaluation artifacts, generate the next structured proposal, or advance approval-gated archive state. Do not use it for generic coding or to invent unsupported execution capability.