fix: add recommendedAction to oe_matchup_edge signal package#71
Open
bongofounder-hub wants to merge 2 commits intoVirtual-Protocol:mainfrom
Open
fix: add recommendedAction to oe_matchup_edge signal package#71bongofounder-hub wants to merge 2 commits intoVirtual-Protocol:mainfrom
bongofounder-hub wants to merge 2 commits intoVirtual-Protocol:mainfrom
Conversation
added 2 commits
March 28, 2026 18:43
B strategy signal-guided rate was ~6.7% because oe_matchup_edge did not include recommendedAction field. League runner reads this field and falls back to neutral/random when null. Adding oe_matchup_edge to the existing confidence/recommendedAction/signalDrivers block should raise signal-guided rate to ~90%+.
- fetchSignal was reading recommendedAction from top-level deliverable instead of deliverable.value (signal envelope). Now unwraps properly. - Adaptive joiner/creator modes were using pre-fix rounds (where signal was always null) to calculate accuracy → always 50% → mode=random. Now filters to rounds with actual signal data (rawAction non-null) and forces align/follow until 12+ real signal rounds accumulate.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
B strategy's signal-guided decision rate was ~6.7% despite valid signals being generated.
signalRecommendedActionRawwas always NULL in league results.Root Cause
oe_matchup_edgepackage was excluded from the block that setsrecommendedAction,confidence, andsignalDrivers. The league runner readsrecommendedAction→ gets null → treats signal as neutral → falls back to random.Meanwhile the
signalfield correctly contained 'ODD'/'EVEN' values with meaningful edge (0.05+), but was ignored by the runner's decision logic.Fix
Added
oe_matchup_edgeto the existing confidence/recommendedAction/signalDrivers inclusion list (1-line change).Expected Impact