edge-candidate-agent

You can automate turning daily OHLCV observations into edge research tickets by running an agent that auto-detects candidates from EOD data and applies hints to generate reproducible strategy specs. This enforces Phase I constraints during detection to ensure validity.

The best way to validate edge-finder-candidate compatibility is to run interface validation against the edge-finder-candidate/v1 specification. This checks your strategy artifacts and confirms they meet the required Phase I constraints before pipeline execution.

To export Phase I artifacts, the agent generates strategy.yaml and metadata.json files from detected edge candidates. These files are exported directly to the strategies/<candidate_id> directory, ensuring format compatibility with downstream trade-strategy-pipeline phases.

Yes, you need pyyaml installed because the agent exports strategy specifications in YAML format. The dependency ensures proper serialization of the strategy.yaml artifacts required for Phase I trade-strategy-pipeline compatibility.

Yes, you can input daily EOD OHLCV data alongside market hints to auto-detect edge candidates. The agent processes these observations to identify potential trading edges and converts them into structured research tickets for quantitative analysis.

Phase I constraints limit edge candidate detection to specific interface compatibility rules defined by edge-finder-candidate/v1. The validation process ensures exported artifacts meet these strict structural requirements, rejecting any candidates that fail interface or constraint checks.