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.

Advice Log

Root overseer appends advice issued to bots.

Entry format:

• Date:
• Bot:
• Observation:
• Advice:
• Reason:
• Evidence that would support it:
• Evidence that would reject it:
• Bot response:
• Later result:

2026-04-27

• Date: 2026-04-27
• Bot: bot-1
• Observation: No daily report output was present, while the journal contains a production BTCUSDT post-only order placement/cancel test and no strategy trade.
• Advice: Treat operational readiness checks as separate from strategy trading in the next daily handoff; include PnL, flat state, and whether any swing setup was actually evaluated.
• Reason: Root needs to distinguish a successful permission test from a trading decision and avoid classifying missing reporting as inactivity.
• Evidence that would support it: Future root reviews can reconcile operational tests, no-trade days, and swing setup evaluations without ambiguity.
• Evidence that would reject it: The bot already produces a complete daily report artifact elsewhere, or the report gap was a one-off schedule issue.
• Bot response: accepted 2026-04-27. Bot-1 created the 2026-04-27 daily report, labeled the BTCUSDT post-only order as an operational test rather than a strategy trade, confirmed flat state, and recorded unavailable PnL.

• Later result: resolved operationally; watch future reports for continued separation between order-permission tests and strategy trades.

• Date: 2026-04-27

• Bot: bot-2
• Observation: The trade journal has a useful DAMUSDT catalyst no-trade entry, but no daily report output was present for the collection run.
• Advice: Keep the catalyst no-trade journal format, and add a daily-report artifact after scans summarizing PnL, catalysts reviewed, skipped trades, and flat/open-position state.
• Reason: The journal shows process quality, but root collection depends on the daily report artifact for consistent cross-bot review.
• Evidence that would support it: Future catalyst scans produce both journal evidence for evaluated setups and a concise daily report.
• Evidence that would reject it: A reliable alternate report output exists and root should collect from that path instead.
• Bot response: accepted 2026-04-27. Bot-2 created the 2026-04-27 daily report, summarized catalysts reviewed, documented the DAMUSDT skip, confirmed flat state, and recorded unavailable PnL.

• Later result: resolved operationally; future catalyst scans are producing useful no-trade journal evidence.

• Date: 2026-04-27

• Bot: bot-3
• Observation: The daily report says no formal no-trade journal entries exist after waiting for BTC/ETH expansion.
• Advice: When a specific breakout/breakdown level is evaluated and skipped, journal the level, expansion evidence, reason for rejection, and next check.
• Reason: Momentum discipline is easier to evaluate when root can see whether the bot skipped a real setup or simply had no trigger.
• Evidence that would support it: Skipped BTC/ETH levels later show whether the expansion filter prevented false breaks or missed valid momentum.
• Evidence that would reject it: No concrete level was evaluated, only passive watchlist monitoring occurred.
• Bot response: accepted 2026-04-27. Bot-3 will journal formal skipped momentum setups with level, expansion evidence, rejection reason, condition that would change the decision, and next check, while not journaling purely passive monitoring as a skipped setup.

• Later result: pending; first accepted-process example is the 2026-04-27 22:19 UTC PENGUUSDT no-trade journal entry.

• Date: 2026-04-27

• Bot: bot-4
• Observation: The daily report correctly avoided fading broad weakness, but the trade journal has no no-trade entries documenting failed-move evidence reviewed.
• Advice: For each candidate fade that reaches review, journal whether flush, reclaim, absorption, and invalidation evidence were present or absent before skipping.
• Reason: Failed-move strategies can look inactive unless the missing confirmation is documented.
• Evidence that would support it: Later reviews can compare skipped failed-move candidates against actual follow-through or continuation.
• Evidence that would reject it: No candidate reached formal review and the bot only monitored the market passively.
• Bot response: accepted 2026-04-27. Bot-4 will journal candidate fades that reach formal review with flush/reclaim/absorption, missing confirmation, invalidation, and reassessment conditions; this is accepted as process evidence, not as a new forced-trade rule.

• Later result: pending; first accepted-process example is the 2026-04-27 22:28 UTC 1000LUNCUSDT no-trade journal entry.

• Date: 2026-04-27

• Bot: bot-5
• Observation: The daily report identifies a broader scout basket, but watchlist.md still only lists BTCUSDT and ETHUSDT.
• Advice: Align the active watchlist with the trading-plan scout basket, while marking extended names as observation-only until they reset and form clean structure.
• Reason: The alt scout mandate needs explicit scan targets, but extended movers should not become automatic trade candidates.
• Evidence that would support it: Future scans cover the intended basket and still reject thin, exhausted, or structureless moves.
• Evidence that would reject it: The bot intentionally keeps the active watchlist restricted to BTC/ETH and uses another documented file for alt scans.
• Bot response: accepted 2026-04-27. Bot-5 aligned watchlist.md with the broader liquid-alt scout basket and marked extended or lower-quality movers as candidates/observation-only until reset, clean structure, acceptable spread, and BTC/ETH regime permission are present.
• Later result: pending; first accepted-process example is the 2026-04-27 watchlist update plus the 2026-04-27 22:38 UTC no-trade scan rejecting extended or unconfirmed smaller-coin moves.

2026-04-28

• Date: 2026-04-28
• Bot: bot-1
• Observation: Today's swing report repeatedly mentions DOGE/APT/INJ/TIA/PENGU and other alt candidates, while the active watchlist still centers on BTC/ETH.
• Advice: Keep recurring alt candidates observation-only unless the bot writes a swing thesis with BTC permission, structural invalidation, and a reason the setup is not just relative-strength noise. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Bot-1 should preserve its swing/regime edge without letting repeated scans drift into undisciplined alt chasing.
• Evidence that would support it: The same alt appears across multiple scans, then later offers a clean breakout/retest or support reclaim with BTC/ETH permission and acceptable swing invalidation.
• Evidence that would reject it: Alt mentions remain one-off scan context and do not create repeatable swing candidates.
• Bot response: accepted 2026-04-28. Bot-1 treated recurring DOGE/1000PEPE/PENGU-style relative-strength names as observation-only unless a BTC-permitted swing thesis with structural invalidation is written.

• Later result: pending; watch whether repeated alt mentions become cleaner swing theses or remain scan context.

• Date: 2026-04-28

• Bot: bot-2
• Observation: Delisting and settlement names dominated the catalyst feed, but most were rejected because final-window mechanics overpowered ordinary invalidation.
• Advice: Add a compact settlement-window checklist before any delisting/final-window trade: time to non-reduce-only cutoff, forced-settlement time, funding crowding, order-book stability, and whether a stop can work normally. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: This preserves the catalyst mandate while making it harder to mistake official event flow for executable edge.
• Evidence that would support it: Future delisting names show high volume but fail the checklist because exits or stops would be dominated by exchange mechanics.
• Evidence that would reject it: A fresh catalyst trade outside settlement mechanics remains clean under the existing catalyst framework.
• Bot response: accepted 2026-04-28. Bot-2 added the settlement-window checklist as a pre-trade filter for delisting/final-window candidates, not as a blanket ban.

• Later result: pending; future delisting reviews should show whether the checklist improves separation between executable catalysts and settlement mechanics.

• Date: 2026-04-28

• Bot: bot-3
• Observation: Many skipped momentum setups were rejected for being late, failing acceptance, or lacking BTC/ETH regime support.
• Advice: Tag each formal skip with one primary rejection class such as late-entry, failed-acceptance, poor-R, or regime-filter. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: The current journals are detailed; a small tag will make later review faster and show whether the bot is mostly avoiding bad entries or missing valid momentum.
• Evidence that would support it: After several sessions, skipped setups cluster around one class and later outcomes show whether that filter is helping.
• Evidence that would reject it: Tags add noise without improving review or the same setup routinely needs multiple inseparable rejection reasons.
• Bot response: accepted 2026-04-28. Bot-3 will add one primary rejection tag to formal no-trade momentum evaluations as a review aid, while keeping full reasoning.

• Later result: pending; later skipped-setup reviews should show whether tags reveal a useful rejection cluster.

• Date: 2026-04-28

• Bot: bot-4
• Observation: AIOTUSDT moved favorably by wick, but never accepted below the management threshold before reversing to the SL.
• Advice: For high-beta spike fades, define the acceptance evidence needed before reducing risk or changing protection; treat wick-only favorable movement as insufficient unless later outcomes prove otherwise. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: The trade plan respected invalidation, but management review can improve by separating tradable acceptance from temporary wick progress.
• Evidence that would support it: Future spike fades that only wick toward target frequently reverse, while accepted closes/retests produce better exits or risk reductions.
• Evidence that would reject it: Wick-only progress repeatedly reaches target before reversal or waiting for acceptance gives back too much edge.
• Bot response: accepted 2026-04-28. Bot-4 added an acceptance requirement to high-beta spike-fade management: do not reduce risk or change protection on wick-only progress without accepted follow-through or verified replacement protection.

• Later result: pending; compare future spike fades where wick-only progress reverses versus accepted follow-through.

• Date: 2026-04-28

• Bot: bot-5
• Observation: Several smaller-alt candidates were identified only after they were already late, while compression names lacked a compact trigger/depth/invalidation map.
• Advice: Maintain a short active compression list with trigger level, minimum spread/depth condition, invalidation, and reassessment time for the top 3-5 scout candidates. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Bot-5's filters are working, but a compact trigger map may help catch rebuilt ranges before they become chase entries.
• Evidence that would support it: Future scans identify entries closer to invalidation or reject candidates faster because the trigger/depth map is pre-written.
• Evidence that would reject it: The active list goes stale quickly or causes premature focus on names that no longer have volume/liquidity.
• Bot response: accepted 2026-04-28. Bot-5 added an active compression trigger list with trigger level, spread/depth condition, invalidation, and reassessment notes.
• Later result: first live test produced a controlled loss rather than a rule change. Bot-5 opened HYPEUSDT long on 2026-04-29 from the compression trigger process, kept risk inside cap with live SL/TP protection, then closed by planned SL at 2026-04-29T12:20:33Z. Outcome supports keeping the trigger list as a scan aid, not a mechanical entry rule.

2026-04-29

• Date: 2026-04-29
• Bot: bot-1
• Observation: Bot-1 reviewed recurring alt strength while the swing decision still depended on BTC reclaim/acceptance or support sweep/reclaim after FOMC.
• Advice: Before promoting any recurring alt from observation to candidate, write the BTC permission condition, the alt-specific swing thesis, structural invalidation, and why the entry is not a chase. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Bot-1's edge is multi-day swing selection, not relative-strength chasing during macro whipsaw.
• Evidence that would support it: A recurring alt only becomes tradable after BTC accepts above 78.2k and preferably 79.4k-79.5k, or after BTC sweeps/reclaims 75.6k-76.4k, and the alt has its own structural invalidation.
• Evidence that would reject it: An alt presents an independent higher-timeframe swing thesis with clean invalidation and enough liquidity even while BTC remains range-bound.
• Bot response: accepted 2026-04-30. Bot-1 kept recurring alt strength observation-only unless BTC permission, an alt-specific swing thesis, structural invalidation, and non-chase entry evidence are present.

• Later result: first applied in the 2026-04-30 daily cycle. DOGE, APT, PENGU, 1000PEPE, and other active names were not promoted to trade candidates without the required BTC permission and written swing evidence.

• Date: 2026-04-29

• Bot: bot-2
• Observation: Today's strongest scheduled catalyst was FOMC, while AIGENSYN listing, settlement names, and HYPE unlock flow were crypto-specific but did not pass execution checks.
• Advice: For scheduled macro events, add the reaction window being evaluated, the instrument class, and the post-release acceptance/rejection condition separately from fresh exchange/project/security/regulatory catalyst checks. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Macro catalysts and crypto-specific catalysts have different evidence requirements; separating them keeps later catalyst review cleaner.
• Evidence that would support it: Future FOMC/GDP/PCE reactions produce trades or skips whose validity depends on post-release market structure, not project/exchange headline freshness.
• Evidence that would reject it: The existing catalyst journal already separates macro reaction windows from crypto-specific catalysts clearly enough for later review.
• Bot response: accepted 2026-04-30. Bot-2 began labeling scheduled macro catalysts separately from crypto-specific catalysts, including the reaction window, instrument class, and post-release acceptance/rejection condition.

• Later result: first applied in the 2026-04-30 daily cycle. The 12:30 UTC GDP/PCE/jobs release was reviewed as a macro reaction window, while MEGA, AIGENSYN, WLFI, and other names were evaluated as crypto-specific catalyst candidates.

• Date: 2026-04-29

• Bot: bot-3
• Observation: Today's skipped momentum setups clustered around late-entry, failed-acceptance, poor-R, and regime-filter.
• Advice: For a small sample of formal skips, add a later note at the next scan or after one 1h close: followed through, reversed, or inconclusive. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Rejection tags become more useful when later outcomes show whether they are filtering false breaks or blocking valid continuation.
• Evidence that would support it: One-hour or next-scan outcomes show repeated late-entry or failed-acceptance skips reversing, validating the filter.
• Evidence that would reject it: Outcome checks add overhead without changing future entry quality or the skipped setups are too different to compare.
• Bot response: accepted 2026-04-29. Bot-3 will add lightweight outcome checks to a small sample of formal skipped momentum setups, classifying later action as followed through, reversed, or inconclusive. This is accepted as an audit aid, not as a new trade rule.

• Later result: pending; first samples include the 2026-04-29 SUIUSDT skipped breakdown and 2026-04-30 UBUSDT skipped long outcome checks.

• Date: 2026-04-29

• Bot: bot-4
• Observation: Multiple failed-move candidates were rejected because the first move toward the practical mean had already happened before review.
• Advice: Add a brief check to formal fade reviews: distance already traveled from failure high/low to current price, distance remaining to practical mean, and whether a fresh retest restored at least about 2R. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Bot-4's edge is accepted failure with room to mean, not late entries after the mean-reversion leg has already paid.
• Evidence that would support it: Later reviews show skipped late fades had little remaining reward or chopped/reversed after the initial snapback.
• Evidence that would reject it: Fresh retests after an already-paid first leg still produce clean 2R setups often enough to justify treating them normally.
• Bot response: accepted 2026-04-30. Bot-4 added the first-leg-paid check to formal fade reviews: distance already traveled from failure high/low, distance remaining to the practical mean, and whether a fresh retest restored at least about 2R. This is accepted as process evidence, not as a blanket ban on second-chance retests.

• Later result: first applied in 2026-04-30 scans. BSBUSDT, AIOTUSDT, BIOUSDT, TACUSDT, and other high-beta candidates were skipped when the first snapback leg had already paid or remaining reward/risk to the practical mean was weak; continue comparing later retests against this filter.

• Date: 2026-04-29

• Bot: bot-5
• Observation: HYPEUSDT followed the plan and closed by SL, but stop slippage plus commission/funding drag made the local net effect worse than trigger-level realized PnL alone.
• Advice: Before the next smaller-alt live entry, compare planned max loss at the stop with a conservative slippage/commission/funding estimate from the HYPE trade, and reduce size or skip if the all-in adverse cost would exceed mandate risk. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Smaller-alt stop-risk math can understate loss if slippage, funding, and commission asset effects are material for the account size.
• Evidence that would support it: Future alt stops show similar drag relative to planned trigger-level risk, especially during high-volatility event windows.
• Evidence that would reject it: Slippage and fees remain negligible across several trades, or reducing size would materially underuse valid setups.
• Bot response: accepted 2026-04-30. Bot-5 accepted this as a live entry-sizing check, not as a reason to stop taking valid smaller-alt setups. Before each smaller-alt entry, compare planned stop loss plus a conservative slippage/commission/funding estimate against the 0.50% risk cap, then reduce size or skip if all-in adverse cost would exceed mandate risk.
• Later result: first applied on 2026-04-30. The 1000PEPEUSDT entry was immediately reduced after the fill put raw stop risk too close to the cap, and the 1000LUNCUSDT entry was sized around 0.469% planned stop risk before fees/slippage. Both later stopped by plan, reinforcing that the buffer should remain a sizing guard rather than a broad strategy ban.

2026-04-30

• Date: 2026-04-30
• Bot: bot-1
• Observation: Today's scans kept the BTC 76.4k, 77.8k-78.2k, and ETH 2,328-2,350 map consistent, while the 12:30 UTC GDP/PCE/jobs release had enough force to change the intraday regime.
• Advice: After major scheduled macro releases, add one short "map refresh" line to the next swing scan covering BTC permission, ETH permission, and whether recurring alts stay observation-only. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Bot-1 can avoid treating stale pre-data levels as permission for post-data swing entries or alt promotions.
• Evidence that would support it: Future post-data scans show BTC/ETH thresholds, support/reclaim zones, or alt permission changed materially after the release.
• Evidence that would reject it: The 4h/12h structure and actionable thresholds remain unchanged after several macro windows, making a separate refresh note redundant.
• Bot response: accepted 2026-05-01. Bot-1's 2026-05-01 daily report says the advice was accepted and applied: scans explicitly separated pre-ISM and post-ISM conditions, kept BTC permission around the 77.8k-78.2k acceptance/retest area and the 79.4k-79.5k resistance shelf, kept ETH's 2,328-2,350 reclaim as the permission zone, and left recurring alt strength observation-only without BTC permission plus a written swing thesis, structural invalidation, and non-chase evidence.

• Later result: first applied in the 2026-05-01 daily cycle. No trade was opened; the process avoided treating the first post-ISM impulse as automatic swing permission.

• Date: 2026-04-30

• Bot: bot-2
• Observation: MEGA had a valid fresh listing catalyst today, but the first spike failed, later short entries were already late or thin, and the remaining move no longer offered clean reward/risk.
• Advice: For fresh listings, record time since listing, first impulse result, depth/spread stability, and whether the remaining setup is still early before formal entry evaluation. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Bot-2 can preserve listing-catalyst discipline while avoiding trades after the clean window has passed.
• Evidence that would support it: Future listings show the best edge appears near the first accepted reclaim/break or first failed-spike retest, while later entries suffer from thin depth, wide stops, or stale impulse risk.
• Evidence that would reject it: Listing setups remain equally tradable later in the session when structure, depth, and invalidation improve.
• Bot response: accepted 2026-04-30. Bot-2 added a first-listing entry-window check: time since listing, first impulse result, depth/spread stability, and whether the remaining setup is still early before formal evaluation. This is a listing-catalyst process check, not a blanket time-based ban.

• Later result: first applied to the 2026-04-30 MEGA sequence. Later reviews found MEGA had real catalyst volume, but after the first listing spike/rejection and subsequent breakdown/rebound, remaining entries were either late, thin, or required stops too wide for normal listing volatility. Keep comparing future listings where depth and structure improve later in the session.

• Date: 2026-04-30

• Bot: bot-3
• Observation: Today's formal skips repeatedly found valid single-name movement only after the entry was late, near a 24h high/low, or no longer offered enough reward/risk.
• Advice: After each scan, write two or three active trigger/retest levels with the required volume/regime condition and invalidation area for the next scan. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Bot-3 needs more evidence on whether it is missing valid momentum because review happens too late, or correctly avoiding exhausted moves.
• Evidence that would support it: Prewritten trigger levels lead to faster formal evaluations near retest/rebreak points and fewer late-entry-only skips.
• Evidence that would reject it: Candidates remain too fast or too noisy for prewritten levels to improve entry quality.
• Bot response: accepted 2026-04-30. Bot-3 accepted prewritten trigger/retest levels as a scan aid, not a standing order or new entry filter; each trigger still requires live volume, volatility, regime support, invalidation, and reward/risk evidence.

• Later result: first applied in the 2026-04-30 21:19 UTC scan and continued through 2026-05-01 scans. Trigger maps helped focus reviews on BTC/ETH acceptance/retest areas and selected single-name continuation levels, but many candidates still remained late, noisy, or unsupported by broad-market confirmation. Keep evaluating whether trigger maps reduce late-entry skips.

• Date: 2026-04-30

• Bot: bot-4
• Observation: The AIGENSYN protection submission initially failed because client algo IDs exceeded Binance's length limit, then succeeded after shorter IDs were used and verified live.
• Advice: Before the next live order, use a short client algo ID template for SL/TP placement and record it in the execution plan. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Protection should place correctly on the first attempt, especially during high-beta failed-move trades where delay can matter.
• Evidence that would support it: Future orders using a short fixed template place SL/TP protection without ID-length retries.
• Evidence that would reject it: Binance rejects protection for unrelated reasons even with short IDs, or the current order helper already enforces safe lengths.
• Bot response: accepted 2026-05-01. Bot-4 accepted this as execution-process evidence, not a trade-selection rule. The next live order, TRBUSDT long, used short client algo IDs b4trbSL0501 and b4trbTP0501 for SL/TP placement and recorded them in the execution plan and open-position record.

• Later result: first applied on 2026-05-01 TRBUSDT. SL/TP protection placed successfully on the first attempt through /fapi/v1/algoOrder and was verified live through /fapi/v1/openAlgoOrders; continue watching for unrelated Binance validation failures, but the ID-length failure mode was resolved on this sample.

• Date: 2026-04-30

• Bot: bot-5
• Observation: Today's 1000PEPE and 1000LUNC losses were controlled by planned stops, but the local PnL record mixes realized trading PnL, BNFCR commissions, possible funding/accounting effects, and USDT wallet reconciliation.
• Advice: For each stopped smaller-alt trade, add one line with planned stop risk, realized PnL, commissions by asset, funding if any, slippage versus trigger, and USDT-equivalent all-in cost when available. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Bot-5's 0.50% risk budget is tight enough that commission asset effects, slippage, and funding can decide whether sizing was truly inside mandate.
• Evidence that would support it: All-in cost lines show material differences from trigger-level planned loss or help explain wallet-balance changes after several stopped trades.
• Evidence that would reject it: Costs remain negligible and the existing journal fields already reconcile cleanly without extra summary.
• Bot response: accepted 2026-05-01. Bot-5 accepted this as a journal/review improvement, not as a new setup filter or reason to reject valid smaller-alt trades. For future stopped smaller-alt trades, it will add one concise all-in cost line covering planned stop risk, realized PnL, commissions by asset, funding if available, slippage versus trigger, and USDT-equivalent cost when available.
• Later result: pending; compare future stopped smaller-alt records against the 0.50% risk budget before promoting this into a broader strategy rule.

2026-05-01

• Date: 2026-05-01
• Bot: bot-3
• Observation: The ZECUSDT long stopped quickly after entry; planned stop-risk was about 0.9675 USDT before fees, but the 379.10 mark-price stop filled at 378.41 for -1.14000000 USDT gross realized PnL before commission accounting. The earlier BIOUSDT stopped trade also filled through its stop trigger in fast movement.
• Advice: Before the next fast single-name momentum entry, add one line comparing planned stop risk plus a conservative slippage/commission buffer against the risk cap; either size below the cap, require a retest/hold closer to invalidation, or skip if the all-in adverse cost is not defensible. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Momentum stops can work mechanically but still exceed intended risk if the entry is close to a fast pullback zone and the size leaves no room for normal stop-market slippage.
• Evidence that would support it: Future ZEC/BIO-like breakouts with nearby stops continue to slip materially, especially near prior 4h resistance or after vertical candles.
• Evidence that would reject it: Several future trades with similar structure stop near trigger with negligible slippage, or waiting for retest/hold causes systematically worse entries without reducing realized loss.
• Bot response: pending.

• Later result: pending.

• Date: 2026-05-01

• Bot: bot-1
• Observation: BTC reached the 77.8k-78.2k confirmation band after ISM, but bot-1 still skipped because price remained below 79.4k-79.5k resistance and ETH had not reclaimed 2,328-2,350.
• Advice: In the next post-ISM swing scan, write one line defining the BTC retest-hold evidence versus continuation-chase evidence before promoting any recurring alt. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Bot-1's swing mandate needs clear BTC permission before recurring alt strength becomes a candidate rather than observation-only.
• Evidence that would support it: BTC retests 77.8k-78.2k as support, holds with controlled extension and usable room, while ETH or selected alts improve structure without forcing a chase.
• Evidence that would reject it: BTC breaks directly through 79.4k-79.5k with accepted higher-timeframe structure, or rejects back below the confirmation band and makes the distinction irrelevant.
• Bot response: pending.

• Later result: pending.

• Date: 2026-05-01

• Bot: bot-2
• Observation: SUI was a real May 1 unlock watch, but public unlock references differed on size/timing and live SUIUSDT price action stayed firm-to-rangebound rather than confirming distribution or absorption.
• Advice: For the next scheduled unlock candidate, record source, size versus float, timing uncertainty, and the exact live-flow condition required before entry. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Scheduled unlock headlines need both verified supply context and tradable live-flow confirmation.
• Evidence that would support it: Future unlock watches show that verified size/float/timing plus accepted breakdown, failed reclaim, or absorption/reclaim improves trade selection.
• Evidence that would reject it: Unlock candidates remain untradable despite better source notes, or existing catalyst notes already capture size/timing and required live-flow evidence clearly enough.
• Bot response: pending.

• Later result: pending.

• Date: 2026-05-01

• Bot: bot-4
• Observation: TRBUSDT moved above the 20.0 management threshold while still below the 20.66-20.85 objective/TP zone, leaving open profit exposed but not yet at the planned target.
• Advice: On the next active-position management wake, write the exact stall/rejection evidence that would justify manual profit capture versus leaving SL/TP unchanged. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Bot-4's edge is failed-move mean reversion; a profitable snapback should remain governed by written evidence, not drift into an unmanaged swing.
• Evidence that would support it: TRB prints acceptance above 20.0 and then stalls or rejects below 20.66-20.85 with weakening participation while the reclaim thesis remains mature.
• Evidence that would reject it: TRB accepts cleanly into the objective/TP zone or the original reclaim structure fails before any manual profit decision is relevant.
• Bot response: pending.

• Later result: pending.

• Date: 2026-05-01

• Bot: bot-5
• Observation: Today's report says the active compression trigger list is getting stale relative to current ZEC, HYPE, TAO, 1000PEPE, and newer-mover levels.
• Advice: Before the next high-quality scout scan, refresh the active compression trigger list with current trigger, invalidation, spread/depth requirement, and reassessment note for the top few liquid candidates. Evaluate this against your own trades and mandate; accept, reject, or defer based on evidence; do not add a rule unless evidence supports it.
• Reason: Bot-5 needs liquid smaller-alt entries near invalidation; stale trigger levels can turn a useful scan aid into late-entry bias.
• Evidence that would support it: Refreshed trigger levels help future scans evaluate retests or rebuilt shelves earlier and reject stale setups faster.
• Evidence that would reject it: Levels go stale too quickly to improve decisions, or live scans already adjust levels without relying on the written list.
• Bot response: pending.
• Later result: pending.