[Tool: session_search]
{"success": true, "mode": "discover", "query": "daily charts VIDYA", "results": [{"session_id": "20260602_122212_eede3e", "when": "June 02, 2026 at 12:23 PM", "source": "cli", "model": "glm-5.1", "title": null, "matched_role": "user", "match_message_id": 38924, "snippet": "can you check - i use >>>daily<<< timef on renko >>>charts<<< - the >>>VIDYA<<< 20 has value on chart as 1244.49 and the >>>DAILY<<< >>>VIDYA<<< in yellow has 1162 - that should not be the case - can you tell me why ", "bookend_start": [{"id": 38790, "role": "user", "content": "can you check https://chart.openalgo.theworkpc.com/ the daily VIDYA is not getting calculated correctly - in INFY30JUN26FUT the Daily VIDYA is at 4067 and pice is 1244", "timestamp": 1780383529.7600474}, {"id": 38791, "role": "assistant", "content": "Let me load the chart app skill and investigate the VIDYA calculation issue.", "timestamp": 1780383529.7635303, "tool_calls": [{"id": "call_o0jofux9", "call_id": "call_o0jofux9", "response_item_id": "fc_o0jofux9", "type": "function", "function": {"name": "skill_view", "arguments": "{\"name\":\"openalgo-chart-app\"}"}}]}, {"id": 38793, "role": "assistant", "content": "Now let me look at the VIDYA calculation code in the chart app:", "timestamp": 1780383529.7684667, "tool_calls": [{"id": "call_elqc83cr", "call_id": "call_elqc83cr", "response_item_id": "fc_elqc83cr", "type": "function", "function": {"name": "search_files", "arguments": "{\"path\":\"/var/www/openalgo-chart\",\"pattern\":\"VIDYA|calculateVIDYA|vidya\",\"output_mode\":\"content\",\"context\":5}"}}]}], "messages": [{"id": 38919, "role": "assistant", "content": "The iteration budget (`agent.max_turns`) defaults to 90, but you're hitting 30 — that must be a custom or lower override. Let me check:", "timestamp": 1780383945.4516382, "tool_calls": [{"id": "call_6qun2ooy", "call_id": "call_6qun2ooy", "response_item_id": "fc_6qun2ooy", "type": "function", "function": {"name": "terminal", "arguments": "{\"command\":\"grep -i 'max_turns\\\\|max_iterations\\\\|iteration' ~/.hermes/config.yaml 2\\u003e/dev/null\"}"}}]}, {"id": 38921, "role": "assistant", "content": "There it is. Your `config.yaml` has `max_turns: 30` (under `agent`). That limits each response to 30 tool-call iterations. For complex multi-step tasks like deploying code changes (file reads, patches, service restarts, verifications), 30 gets burned through fast.\n\nTo increase it:", "timestamp": 1780383945.4551117, "tool_calls": [{"id": "call_17dbugvb", "call_id": "call_17dbugvb", "response_item_id": "fc_17dbugvb", "type": "function", "function": {"name": "terminal", "arguments": "{\"command\":\"hermes config set agent.max_turns 90\"}"}}]}, {"id": 38923, "role": "assistant", "content": "Now set to 90 (the Hermes default). This takes effect on the **next session** (`/new` or restart). You won't hit the 30-iteration wall anymore for complex tasks.\n\n**Why it happened:** Your config had `max_turns: 30`, and my last response
... [50000 chars total, truncated]
2026-07-19 23:54
TOOL (hermes, glm-5.1)
[Tool: session_search]
{"success": true, "mode": "discover", "query": "daily chart trading", "results": [{"session_id": "20260602_122212_eede3e", "when": "June 02, 2026 at 12:23 PM", "source": "cli", "model": "glm-5.1", "title": null, "matched_role": "assistant", "match_message_id": 38941, "snippet": "...This is correct for the bot's >>>trading<<< strategy, but misleading on a >>>chart<<< that labels it \">>>Daily<<< VIDYA.\"\n\n2. **For >>>chart<<<-computed DBs (like INFY):** We compute VIDYA from actual >>>daily<<< closes, so it updates >>>daily<<< — this is a...", "bookend_start": [{"id": 38790, "role": "user", "content": "can you check https://chart.openalgo.theworkpc.com/ the daily VIDYA is not getting calculated correctly - in INFY30JUN26FUT the Daily VIDYA is at 4067 and pice is 1244", "timestamp": 1780383529.7600474}, {"id": 38791, "role": "assistant", "content": "Let me load the chart app skill and investigate the VIDYA calculation issue.", "timestamp": 1780383529.7635303, "tool_calls": [{"id": "call_o0jofux9", "call_id": "call_o0jofux9", "response_item_id": "fc_o0jofux9", "type": "function", "function": {"name": "skill_view", "arguments": "{\"name\":\"openalgo-chart-app\"}"}}]}, {"id": 38793, "role": "assistant", "content": "Now let me look at the VIDYA calculation code in the chart app:", "timestamp": 1780383529.7684667, "tool_calls": [{"id": "call_elqc83cr", "call_id": "call_elqc83cr", "response_item_id": "fc_elqc83cr", "type": "function", "function": {"name": "search_files", "arguments": "{\"path\":\"/var/www/openalgo-chart\",\"pattern\":\"VIDYA|calculateVIDYA|vidya\",\"output_mode\":\"content\",\"context\":5}"}}]}], "messages": [{"id": 38936, "role": "user", "content": "i think there are some more issues - if i see LT chart - the yellow daily line has startaight line for 5 days continuously - how", "timestamp": 1780384857.2579935}, {"id": 38937, "role": "assistant", "content": "Let me check the LT daily_anchors data — that will explain the flat line immediately.", "timestamp": 1780384857.2614381, "tool_calls": [{"id": "call_dnvjmle6", "call_id": "call_dnvjmle6", "response_item_id": "fc_dnvjmle6", "type": "function", "function": {"name": "terminal", "arguments": "{\"command\":\"sqlite3 /home/ubuntu/bots/three_candle_bot/lt_3candle.db \\\"SELECT * FROM daily_anchors ORDER BY date DESC LIMIT 15\\\"\"}"}}]}, {"id": 38939, "role": "assistant", "content": "There it is. Look at the `computed_on` column — it tells the whole story:\n\n| date | fixed_vidya | computed_on |\n|------|------------|-------------|\n| 2026-05-26 | 4049.85 | 2026-05-25 (Sunday!) |\n| 2026-05-27 | 4049.85 | 2026-05-26 |\n| 2026-05-28 | 4049.85 | 2026-05-27 |\n| 2026-06-01 | 4067.12 | 2026-05-29 |\n| 2026-06-02 | 4067.12 | 2026-06-01 |\n| 2026-06-03 | 4067.12 | 2026-06-02 |\n\nThe **3-candle bot** only writes `fixed_vidya` to the DB when it actually **computes/trades** — and by design, the \"daily anchor\" is a fixed value that doesn't change intraday. But the problem
... [50000 chars total, truncated]
2026-07-19 23:54
ASSISTANT (hermes, glm-5.1)
Found the relevant session. Let me pull up the specific conversation about daily charts.
2026-07-19 23:54
TOOL (hermes, glm-5.1)
[Tool: session_search]
{"success": true, "mode": "scroll", "session_id": "20260717_172315_68f7e4", "around_message_id": 53294, "session_meta": {"when": "July 17, 2026 at 05:25 PM", "source": "cli", "model": "glm-5.1", "title": "Fixing Kotak Unknown Status on Dashboard"}, "window": 10, "messages": [{"id": 53280, "role": "tool", "content": "{\"status\": \"success\", \"output\": \"Response length: 0\\nFirst 500 chars: \\n\", \"exit_code\": 0, \"tool_calls_made\": 1, \"duration_seconds\": 20.33, \"stdout_truncated\": false, \"stdout_bytes_captured\": 37, \"stdout_bytes_total\": 37, \"stdout_bytes_omitted\": 0}", "timestamp": 1784289911.8194861, "tool_name": "execute_code", "tool_call_id": "call_m29c3vbq"}, {"id": 53281, "role": "assistant", "content": "", "timestamp": 1784289915.9730256, "tool_calls": [{"id": "call_9up9e923", "call_id": "call_9up9e923", "response_item_id": "fc_9up9e923", "type": "function", "function": {"name": "execute_code", "arguments": "{\"code\":\"from hermes_tools import terminal\\n\\n# API might not support that much history at once. Try shorter range\\nresult = terminal(\\\"\\\"\\\"curl -v -s -m 15 -X POST 'https://shoonya.openalgo.theworkpc.com/api/v1/history' \\\\\\n -H 'Content-Type: application/json' \\\\\\n -d '{\\\"apikey\\\":\\\"8a5a9e0e309675e37cd0024381e212cad47396b680b28d0628f3fb36f6d09b07\\\",\\\"symbol\\\":\\\"INDIGO\\\",\\\"exchange\\\":\\\"NSE\\\",\\\"interval\\\":\\\"D\\\",\\\"start_date\\\":\\\"2026-05-01\\\",\\\"end_date\\\":\\\"2026-07-17\\\"}' 2\\u003e\\u00261 | tail -20\\\"\\\"\\\", timeout=20)\\n\\nprint(result.get(\\\"output\\\", \\\"\\\")[:1000])\"}"}}]}, {"id": 53282, "role": "tool", "content": "{\"status\": \"success\", \"output\": \"* Certificate level 3: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384\\n* Connected to shoonya.openalgo.theworkpc.com (144.217.12.244) port 443\\n* using HTTP/1.x\\n} [5 bytes data]\\n> POST /api/v1/history HTTP/1.1\\r\\n> Host: shoonya.openalgo.theworkpc.com\\r\\n> User-Agent: curl/8.12.1\\r\\n> Accept: */*\\r\\n> Content-Type: application/json\\r\\n> Content-Length: 177\\r\\n> \\r\\n} [177 bytes data]\\n* upload completely sent off: 177 bytes\\n{ [5 bytes data]\\n* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):\\n{ [57 bytes data]\\n* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):\\n{ [57 bytes data]\\n* Operation timed out after 15002 milliseconds with 0 bytes received\\n* closing connection #0\\n\", \"exit_code\": 0, \"tool_calls_made\": 1, \"duration_seconds\": 15.35, \"stdout_truncated\": false, \"stdout_bytes_captured\": 704, \"stdout_bytes_total\": 704, \"stdout_bytes_omitted\": 0}", "timestamp": 1784289931.329884, "tool_name": "execute_code", "tool_call_id": "call_9up9e923"}, {"id": 53283, "role": "assistant", "content": "The Shoonya API is timing out for daily history. Let me use the local chart API instead, which aggregates from the 5-min data:", "timestamp": 1784289936.7926347, "tool_calls": [{"id": "call_7aus
... [33800 chars total, truncated]
2026-07-19 23:54
ASSISTANT (hermes, glm-5.1)
Found it. The conversation was from July 17 — you were looking at INDIGO on the daily chart and asked about trading with VIDYA 20. The key finding:
**"What we see is already passed"** — VIDYA-20 on daily charts flips 1-3 days AFTER the actual turn. On INDIGO daily data (27 bars), VIDYA only started producing values at bar #20 (Jul 8), completely missing the base, breakout, and peak. The signals were whipsaw-heavy:
- Jul 9: LONG (but 136 pts above the bottom)
- Jul 14: SHORT (whipsaw — just 1 day after the low)
- Jul 15: LONG (flipped back again)
**The conclusion**: VIDYA-20 on daily works as a **trend filter** (direction bias) only, NOT an entry signal. Actual entries need intraday timing (5min/15min). Multi-timeframe approach: Daily VIDYA = bias, intraday = entry timing.
This was saved as a pain point in memory. Want to continue that discussion about the daily trading approach now?
2026-07-19 23:54
USER (hermes, glm-5.1)
yes - so if we mark daily vidya on indigo chart - can you pull the data fo a week - i like to see like daily vodya level - like friday vidya value becomes line in stone for monday trading -
[Tool: execute_code]
{"status": "success", "output": "Total trading days: 87\nFrom: 2026-02-25 to 2026-07-08\n\n====================================================================================================\nINDIGO DAILY — LAST 2 WEEKS + VIDYA ANCHOR LEVELS\n====================================================================================================\n\nThe concept: Yesterday's VIDYA = Today's LINE IN STONE (fixed anchor for intraday trading)\n\nDate Close VIDYA-20 Diff Signal VIDYA-10 Sig-10\n----------------------------------------------------------------------------------------------------\n2026-06-16 4858.3 4488.2 +370.1 LONG 4543.2 LONG\n2026-06-17 4883.4 4524.1 +359.3 LONG 4571.4 LONG\n2026-06-18 5016.6 4572.5 +444.1 LONG 4617.4 LONG\n2026-06-19 5021.0 4613.4 +407.6 LONG 4661.2 LONG\n2026-06-22 5010.9 4647.4 +363.5 LONG 4716.3 LONG\n2026-06-24 5170.6 4693.6 +477.0 LONG 4787.5 LONG\n2026-06-25 5421.5 4776.0 +645.5 LONG 4896.7 LONG\n2026-06-29 5314.6 4823.5 +491.1 LONG 4957.9 LONG\n2026-06-30 5368.4 4876.4 +492.0 LONG 5014.4 LONG\n2026-07-01 5399.0 4935.1 +463.9 LONG 5063.4 LONG\n2026-07-02 5444.0 4992.9 +451.1 LONG 5117.7 LONG\n2026-07-03 5426.5 5039.9 +386.6 LONG 5159.0 LONG\n2026-07-06 5408.5 5079.4 +329.1 LONG 5187.1 LONG\n2026-07-07 5395.0 5113.4 +281.6 LONG 5209.1 LONG\n2026-07-08 5124.0 5114.3 +9.7 LONG 5207.1 SHORT\n", "exit_code": 0, "tool_calls_made": 1, "duration_seconds": 0.14, "stdout_truncated": false, "stdout_bytes_captured": 1639, "stdout_bytes_total": 1639, "stdout_bytes_omitted": 0}
2026-07-19 23:59
ASSISTANT (hermes, glm-5.1)
2026-07-19 23:59
TOOL (hermes, glm-5.1)
[Tool: execute_code]
{"status": "error", "output": "Chart API data (spot NSE):\n 2026-07-13: close=5235.0\n 2026-07-14: close=5110.0\n 2026-07-15: close=5170.0\n 2026-07-16: close=5265.0\n 2026-07-17: close=5246.0\n\nMorning sniper data (futures NFO):\n\n--- stderr ---\nTraceback (most recent call last):\n File \"/tmp/hermes_sandbox_gs52ouyi/script.py\", line 25, in <module>\n for date, close in daily_closes[-5:]:\n ^^^^^^^^^^^^\nNameError: name 'daily_closes' is not defined\n", "exit_code": 1, "tool_calls_made": 1, "duration_seconds": 0.2, "stdout_truncated": false, "stdout_bytes_captured": 198, "stdout_bytes_total": 198, "stdout_bytes_omitted": 0, "error": "Traceback (most recent call last):\n File \"/tmp/hermes_sandbox_gs52ouyi/script.py\", line 25, in <module>\n for date, close in daily_closes[-5:]:\n ^^^^^^^^^^^^\nNameError: name 'daily_closes' is not defined\n"}
2026-07-19 23:59
ASSISTANT (hermes, glm-5.1)
2026-07-19 23:59
TOOL (hermes, glm-5.1)
[Tool: execute_code]
{"status": "success", "output": "===============================================================================================\nINDIGO DAILY — VIDYA-20 AS 'LINE IN STONE'\n===============================================================================================\n\nConcept: Yesterday's VIDYA value = Today's FIXED anchor level\n - Computed at EOD, does NOT change during the trading day\n - Price ABOVE anchor → LONG bias → look for long entries intraday\n - Price BELOW anchor → SHORT bias → look for short entries intraday\n - This SOLVES the lag problem: you know the level BEFORE market opens\n\nDate Close VIDYA-20 ANCHOR Diff pts Bias\n---------------------------------------------------------------------------\n2026-06-09 4558.3 4379.0 4373.5 +184.8 LONG\n2026-06-10 4544.8 4388.1 4379.0 +165.8 LONG\n2026-06-11 4513.3 4395.3 4388.1 +125.2 LONG\n2026-06-12 4721.7 4417.7 4395.3 +326.4 LONG\n2026-06-15 4887.6 4455.5 4417.7 +469.9 LONG\n2026-06-16 4858.3 4488.2 4455.5 +402.8 LONG\n2026-06-17 4883.4 4524.1 4488.2 +395.2 LONG\n2026-06-18 5016.6 4572.5 4524.1 +492.5 LONG\n2026-06-19 5021.0 4613.4 4572.5 +448.5 LONG\n2026-06-22 5010.9 4647.4 4613.4 +397.5 LONG\n2026-06-24 5170.6 4693.6 4647.4 +523.2 LONG\n2026-06-25 5421.5 4776.0 4693.6 +727.9 LONG\n2026-06-29 5314.6 4823.5 4776.0 +538.6 LONG\n2026-06-30 5368.4 4876.4 4823.5 +544.9 LONG\n2026-07-01 5399.0 4935.1 4876.4 +522.6 LONG\n2026-07-02 5444.0 4992.9 4935.1 +508.9 LONG\n2026-07-03 5426.5 5039.9 4992.9 +433.6 LONG\n2026-07-06 5408.5 5079.4 5039.9 +368.6 LONG\n2026-07-07 5395.0 5113.4 5079.4 +315.6 LONG << LAST\n2026-07-08 5124.0 5114.3 5113.4 +10.6 LONG << LAST\n\n===========================================================================\nMONDAY'S ANCHOR (Jul 8 VIDYA): 5114.3\n If price > 5114.3 → LONG bias\n If price < 5114.3 → SHORT bias\n Gap from last close: +9.7 pts\n\nNOTE: This data is from morning sniper DB (INDIGO FUTURES, NFO)\n It only goes to Jul 8. Need broker login to fill Jul 9-17.\n", "exit_code": 0, "tool_calls_made": 2, "duration_seconds": 0.27, "stdout_truncated": false, "stdout_bytes_captured": 2361, "stdout_bytes_total": 2361, "stdout_bytes_omitted": 0}
[Tool: execute_code]
{"status": "success", "output": "==============================================================================================================\n'LINE IN STONE' TRADING SIMULATION — INDIGO FUTURES (87 days, Feb-Jul 2026)\n==============================================================================================================\n\nRules:\n 1. Yesterday's VIDYA-20 = Today's anchor (FIXED, doesn't change intraday)\n 2. If open > anchor → enter LONG at open, exit at close\n 3. If open < anchor → enter SHORT at open, exit at close\n 4. No intraday timing — just open-to-close direction trade\n 5. 1 lot = 300 shares INDIGO futures\n\nDate Anchor Open Close Dir P&L pts\n-----------------------------------------------------------------\n2026-06-09 4373.5 4424.9 4558.3 LONG +133.4\n2026-06-10 4379.0 4526.0 4544.8 LONG +18.8\n2026-06-11 4388.1 4507.6 4513.3 LONG +5.7\n2026-06-12 4395.3 4602.1 4721.7 LONG +119.6\n2026-06-15 4417.7 4820.0 4887.6 LONG +67.6\n2026-06-16 4455.5 4920.0 4858.3 LONG -61.7\n2026-06-17 4488.2 4890.0 4883.4 LONG -6.6\n2026-06-18 4524.1 4898.0 5016.6 LONG +118.6\n2026-06-19 4572.5 5001.0 5021.0 LONG +20.0\n2026-06-22 4613.4 5001.1 5010.9 LONG +9.8\n2026-06-24 4647.4 4978.0 5170.6 LONG +192.6\n2026-06-25 4693.6 5210.0 5421.5 LONG +211.5\n2026-06-29 4776.0 5423.9 5314.6 LONG -109.3\n2026-06-30 4823.5 5320.0 5368.4 LONG +48.4\n2026-07-01 4876.4 5349.5 5399.0 LONG +49.5\n2026-07-02 4935.1 5421.0 5444.0 LONG +23.0\n2026-07-03 4992.9 5459.5 5426.5 LONG -33.0\n2026-07-06 5039.9 5413.0 5408.5 LONG -4.5\n2026-07-07 5079.4 5399.0 5395.0 LONG -4.0\n2026-07-08 5113.4 5266.5 5124.0 LONG -142.5\n\n=================================================================\nSIMPLE OPEN-TO-CLOSE RESULTS:\n Total trades: 66\n Wins: 32 (48%)\n Losses: 34 (52%)\n Total P&L: +60.1 pts\n Avg trade: +0.9 pts\n Best trade: +211.5 pts\n Worst trade: -181.9 pts\n Per lot (300): ₹+18,030\n\n==============================================================================================================\nSMARTER RULE: Skip trades when open is within ±0.5% of anchor (NO-MAN'S LAND)\n==============================================================================================================\n Trades taken: 63\n Skipped: 3 (within ±0.5% of anchor)\n Wins: 31 (49% win rate)\n Losses: 32\n Total P&L: +306.1 pts\n Avg trade: +4.9 pts\n Per lot (300): ₹+91,830\n\n==============================================================================================================\nTHE BOTTOM LINE:\n===========================
... [4110 chars total, truncated]
2026-07-20 00:00
ASSISTANT (hermes, glm-5.1)
2026-07-20 00:00
TOOL (hermes, glm-5.1)
[Tool: execute_code]
{"status": "success", "output": "==============================================================================================================\nTREND vs CROSSOVER ZONES — INDIGO VIDYA-20\n==============================================================================================================\n\nFound 7 crossovers in 87 trading days:\n\n Crossover #1: 2026-04-06 — SHORT → LONG\n Price: 4331.5 | VIDYA: 4280.4 | Gap: +51.1\n Danger zone: 2026-03-30 to 2026-04-09\n\n Crossover #2: 2026-04-07 — LONG → SHORT\n Price: 4279.5 | VIDYA: 4280.4 | Gap: -0.9\n Danger zone: 2026-04-01 to 2026-04-10\n\n Crossover #3: 2026-04-08 — SHORT → LONG\n Price: 4637.9 | VIDYA: 4285.5 | Gap: +352.4\n Danger zone: 2026-04-02 to 2026-04-13\n\n Crossover #4: 2026-04-29 — LONG → SHORT\n Price: 4368.8 | VIDYA: 4374.8 | Gap: -6.0\n Danger zone: 2026-04-24 to 2026-05-05\n\n Crossover #5: 2026-05-06 — SHORT → LONG\n Price: 4541.9 | VIDYA: 4375.0 | Gap: +166.9\n Danger zone: 2026-04-30 to 2026-05-11\n\n Crossover #6: 2026-05-11 — LONG → SHORT\n Price: 4360.2 | VIDYA: 4381.2 | Gap: -21.0\n Danger zone: 2026-05-06 to 2026-05-14\n\n Crossover #7: 2026-05-21 — SHORT → LONG\n Price: 4379.3 | VIDYA: 4345.1 | Gap: +34.2\n Danger zone: 2026-05-18 to 2026-05-26\n\n==============================================================================================================\nPRACTICAL SUMMARY FOR MONDAY:\n==============================================================================================================\n\nLast trading day: 2026-07-08\nLast close: 5124.0\nLast VIDYA-20: 5114.3\nDistance: +9.7 pts (+0.2%)\n\nCURRENT STATUS: LONG BIAS\n\nNEXT TRADING DAY'S ANCHOR: 5114.3\n → If price opens ABOVE 5114.3: LONG bias, look for long setups\n → If price opens BELOW 5114.3: SHORT bias, look for short setups \n → If price opens within ±0.5% of 5114.3: SKIP, no clear direction\n\nREMEMBER: The data only goes to Jul 8. Need broker login for Jul 9-17 data.\n\n", "exit_code": 0, "tool_calls_made": 1, "duration_seconds": 0.14, "stdout_truncated": false, "stdout_bytes_captured": 1959, "stdout_bytes_total": 1959, "stdout_bytes_omitted": 0}
2026-07-20 00:00
ASSISTANT (hermes, glm-5.1)
Here's the full "Line in Stone" analysis for INDIGO:
**87 trading days (Feb-Jul 2026), VIDYA-20 on daily futures data**
---
**THE CONCEPT: Yesterday's VIDYA = Today's Fixed Anchor**
Each day's VIDYA-20 value is computed at EOD and becomes a FIXED LEVEL for the next trading day. It doesn't change during the day — it's a "line in stone."
| What | How |
|------|-----|
| Compute | EOD: VIDYA-20 from daily closes |
| Mark | Next morning: horizontal line at that level on 5min chart |
| Direction | Above line = LONG bias, Below = SHORT bias |
| Entry | Use intraday (5min/15min) for timing |
| Skip | Within ±0.5% of line = no-man's land |
---
**Results (simple open-to-close, no intraday timing):**
| Metric | Simple | Skip ±0.5% zone |
|--------|--------|-----------------|
| Trades | 66 | 63 (3 skipped) |
| Win rate | 48% | 49% |
| Total P&L | +60 pts | **+306 pts** |
| Per lot (300) | ₹18K | **₹92K** |
The skip rule is critical — near crossovers, the anchor is unreliable.
---
**7 crossovers in 87 days — these are DANGER ZONES:**
1. **Apr 6-8**: SHORT→LONG→SHORT→LONG (3 whipsaws in 3 days!) — gap was only +0.9 to -51 pts from VIDYA
2. **Apr 29**: LONG→SHORT (gap -6 pts) — barely below VIDYA
3. **May 6**: SHORT→LONG (gap +167 pts) — strong flip
4. **May 11**: LONG→SHORT (gap -21 pts) — quick reversal
5. **May 21**: SHORT→LONG (gap +34 pts) — this one held for 6+ weeks!
The May 21 crossover turned LONG and stayed LONG through the entire 4350→5400 run. That's +1050 pts over 34 trading days. The "line in stone" was 4300-5100 (rising with VIDYA), always well above the anchor.
---
**Current state (as of Jul 8 — data is stale):**
- VIDYA-20: 5114.3
- Close: 5124.0
- Gap: +9.7 pts (+0.2%) — barely LONG
- **This is a DANGER ZONE** — price is very close to VIDYA, skip or use caution
The morning sniper DB is stale (last data Jul 8). Need broker login to fill Jul 9-17 data. Want me to update the data or set this up as a daily computation on the chart?