What problem does it solve?
When the default OpenXQuant component and recipe catalogs do not include the required indicator, signal, or portfolio optimizer behavior, users need a safe, reproducible way to build custom workspace-local components without modifying the core SDK, ensuring full auditability and no unintended global side effects.
Core Features & Use Cases
- Workspace-Local Component Authoring: Build custom indicators, signals, and portfolio optimizers that are isolated to your workspace, with no modifications to the installed OpenXQuant SDK bundle.
- Built-in Validation & Provenance: Includes automated protocol compliance testing, manifest hashing, and catalog refresh to ensure all components are reproducible and auditable for formal quant research workflows.
- Safety Guardrails: Blocks unsupported custom rule authoring by default and rejects ambiguous or future-looking logic to maintain the integrity of audited backtests.
Quick Start
Use the author-component skill to build a custom risk-adjusted timing signal component from the provided component_request.json file.