Skip to content

[codex] Add Telegram anti-martingale execution policy - #144

Draft
LimiNode wants to merge 2 commits into
feat/telegram-timing-martingalefrom
feat/telegram-antimartingale
Draft

[codex] Add Telegram anti-martingale execution policy#144
LimiNode wants to merge 2 commits into
feat/telegram-timing-martingalefrom
feat/telegram-antimartingale

Conversation

@LimiNode

@LimiNode LimiNode commented Aug 21, 2026

Copy link
Copy Markdown
Owner

Summary

  • add opt-in Telegram anti-martingale sizing driven only by terminal broker TradeResult updates
  • keep one pending trade per chat/topic/symbol/direction/strategy group and reject later signals until the result arrives
  • bound progression by an explicit multiplier, maximum winning steps, and maximum amount; reset on every non-WIN terminal result
  • reject the incompatible source-side CONTIGUOUS_STEPS policy and document the result-authoritative contract
  • reserve anti-martingale signal_id state before callback dispatch so synchronous broker results cannot be lost
  • keep dedupe and money-management reservations fail-closed when a callback throws after an ambiguous handoff

Validation

  • telegram_signal_bridge_test (18/18)
  • telegram_signal_parser_test (28/28)
  • bridge_umbrella_include_test (8/8, MinGW with -Wa,-mbig-obj)

Stack

This draft is stacked on #143 (feat/telegram-timing-martingale) and should merge after it.

Size Telegram bridge signals from confirmed broker results with bounded per-group anti-martingale state.
Keep dedupe and money-management state fail-closed after ambiguous callback failures and register anti-martingale signal IDs before dispatch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant