From 5146f37accc968061e165e6368d001db21ff8f3d Mon Sep 17 00:00:00 2001 From: mindesbunister Date: Tue, 18 Nov 2025 20:39:08 +0100 Subject: [PATCH] docs: Add multi-timeframe data collection documentation - Updated copilot instructions with data collection system overview - Documents 5min execute vs 15min/1H/4H/Daily collect pattern - Explains zero-risk parallel data collection approach - Notes SQL analysis capability for timeframe optimization - References implementation location in execute endpoint - Part of v8 indicator testing and optimization strategy --- .github/copilot-instructions.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 5239f74..5b1717f 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -2627,6 +2627,15 @@ See `POSITION_SCALING_ROADMAP.md` for planned position management optimizations: **Blocked Signals Tracking (Nov 11, 2025):** System now automatically saves all blocked signals to database for data-driven optimization. See `BLOCKED_SIGNALS_TRACKING.md` for SQL queries and analysis workflows. +**Multi-Timeframe Data Collection (Nov 18, 2025):** Execute endpoint now supports parallel data collection across timeframes: +- **5min signals:** Execute trades (production) +- **15min/1H/4H/Daily signals:** Save to BlockedSignal table with `blockReason='DATA_COLLECTION_ONLY'` +- Enables cross-timeframe performance comparison (which timeframe has best win rate?) +- Zero financial risk - non-5min signals just collect data for future analysis +- TradingView alerts on multiple timeframes → n8n passes `timeframe` field → bot routes accordingly +- After 50+ trades: SQL analysis to determine optimal timeframe for live trading +- Implementation: `app/api/trading/execute/route.ts` lines 106-145 + **Data-driven approach:** Each phase requires validation through SQL analysis before implementation. No premature optimization. **Signal Quality Version Tracking:** Database tracks `signalQualityVersion` field to compare algorithm performance: