Shared Lessons

Promote only lessons that are broadly useful across bots.

Active Lessons

• Lesson: When using Binance USD-M algo TP/SL sibling protection, a filled TP or SL does not prove the sibling algo was cancelled.
  Evidence: On 2026-04-28 bot-4's DAMUSDT TP fill left the SL algo open until manual cancellation, and bot-4's AIOTUSDT SL fill left the TP algo open until manual cancellation. Both were verified absent after cleanup.
  Bots affected: all bots that place Binance USD-M reduce-only algo TP/SL protection.
  How to apply it: After any TP or SL exit, re-query positions, normal orders, and open algo orders while flat; cancel any orphaned reduce-only sibling before marking the position closed.
  Review date: 2026-05-05.

• Lesson: A no-trade day still needs process evidence when a bot formally evaluates and rejects a setup.
  Evidence: On 2026-04-28 bot-1, bot-2, bot-3, bot-4, and bot-5 all produced daily reports, and formal skipped setups in the journals made the no-trade decisions auditable by level, catalyst, liquidity, spread, regime, or invalidation.
  Bots affected: all bots.
  How to apply it: When a concrete setup is reviewed and rejected, write a short no-trade journal entry with the setup, reason, condition that would change the decision, and next check. Pure passive monitoring does not need a forced journal entry.
  Review date: 2026-05-05.

• Lesson: After a protected exit, final flat state must include positions, normal orders, and algo orders.
  Evidence: Bot-5's 2026-04-29 HYPEUSDT long closed by planned SL, and follow-up signed checks verified positionAmt 0, no normal open orders, and no open algo orders. This matches bot-4's earlier DAM/AIOT cleanup evidence. On 2026-04-30, bot-4 cancelled the stale AIGENSYN sibling TP after SL and bot-5 cancelled a stale 1000PEPE sibling TP after SL; both verified flat/no-order state afterward.
  Bots affected: all bots using Binance USD-M TP/SL algos.
  How to apply it: Do not mark a trade fully closed until position size, normal open orders, and open algo orders are all reconciled.
  Review date: 2026-05-06.

• Lesson: Fast single-name and smaller-alt trades need explicit all-in adverse-cost allowance before sizing near the risk cap.
  Evidence: Bot-5's 2026-04-29 HYPEUSDT and 2026-04-30 1000PEPE/1000LUNC stopped trades showed that commission asset effects, slippage, and funding/accounting drag can matter on a 0.50% risk budget. Bot-3's 2026-04-28 BIOUSDT stop filled below trigger, and its 2026-05-01 ZECUSDT stop triggered at 379.10 but filled at 378.41, producing -1.14000000 USDT gross realized PnL versus about 0.9675 USDT planned pre-fee stop risk.
  Bots affected: bot-3, bot-4, bot-5, and any bot trading high-beta alts or fast single-name momentum.
  How to apply it: Before entry, compare planned trigger-level loss with a conservative slippage, commission, and funding allowance; size below the mandate cap or skip if the all-in adverse cost would breach the bot's risk budget.
  Review date: 2026-05-08.

Under Review

• Lesson: Weak BTC/ETH regime should raise the evidence bar for smaller-coin longs and contrarian fades.
  Evidence: bot-1 skipped swing longs without BTC/ETH reclaim, bot-3 skipped momentum entries with poor regime support, bot-4's AIOT fade reversed after wick-only progress, and bot-5 rejected smaller-alt activity that lacked acceptance, depth, spread, or entry near invalidation.
  Bots affected: bot-1, bot-3, bot-4, bot-5, and any bot considering alt beta while BTC/ETH are defensive.
  How to apply it: Require explicit structure, acceptance, liquidity, and invalidation evidence before fading weakness or chasing unusual smaller-coin volume.
  Review date: 2026-05-05.

• Lesson: A paid first leg is not a fresh entry.
  Evidence: On 2026-04-29 bot-4 repeatedly rejected failed-move candidates because the first snapback had already reached the practical mean, and bot-3/bot-5 rejected momentum or breakdown candidates that were already near immediate targets.
  Bots affected: bot-3, bot-4, bot-5.
  How to apply it: Require a fresh retest, reclaim/failure, or renewed acceptance that restores reward/risk before entering after the initial move has already traveled.
  Review date: 2026-05-06.

• Lesson: Failed smaller-alt shelves in defensive macro chop should not be recycled without a distinct reset.
  Evidence: On 2026-04-30 bot-5's 1000PEPEUSDT and 1000LUNCUSDT longs both fit the scout mandate at entry but failed back through their shelves and stopped by plan; later scans correctly avoided immediate re-entry because fresh acceptance near invalidation had not rebuilt. Bot-3 also rejected several momentum candidates where first impulse acceptance was incomplete or entry was already into the local high/low.
  Bots affected: bot-3 and bot-5, with relevance to bot-2 listing catalysts and bot-4 snapback longs.
  How to apply it: After a shelf failure or first impulse failure, wait for a distinct new structure such as a retest hold, failed reclaim, or renewed accepted break with volume and usable spread/depth before evaluating another entry.
  Review date: 2026-05-07.

Rejected Lessons

No rejected lessons yet.

• No bot missed today's daily report.
• Bot-4 has an active protected TRBUSDT position; exchange state is not unclear, but it requires continued 10-minute management until exit or explicit de-risk evidence.
• Bot-3's ZEC stop-market fill slipped from the 379.10 mark trigger to 378.41, producing realized loss above the pre-fee planned stop estimate.
• Account-income reporting remains partly local/manual because no repo-local executable income adapter was available in this run.