Hard-disable live execution capability - #19
Merged
Conversation
12 tasks
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
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.
What changed
LiveTraderconstruction, placement, and internal submission fail before adapters or flags are inspectedLiveTraderfrom the public live package export and removes the published Polymarket trading extra__new__, injected-client, venue mutation, entrypoint, and audit bypassesWhy / root cause
Supported commands were disabled, but direct Python imports could still construct a live trader or call authenticated venue mutations. The former safety audit could also report success for a credentialed live configuration without operational evidence. That was a capability and product-claim mismatch.
User and developer impact
No credential, configuration, confirmation flag, injected adapter/client, direct import, or installed-wheel path can enable live submission in this release. Public scanning and shadow replay remain supported. Operators receive an explicit NO-GO and a concrete evidence template for any later, separately authorized readiness project.
Schema and migration
polymarkettrading dependency extra from the published packageautopredict.live.trader.LiveTrader, but construction and mutation always raiseLiveExecutionDisabledErrorautopredict.live.LiveTraderre-exportlive_execution_capability_enabled: falseand fails any live requestVerification
git diff --check: passedLiveExecutionDisabledErrorReadiness decision
NO-GO. Live execution remains disabled. Seven days of clean representative shadow evidence do not exist, and no later human-authorized live-enablement project has approved the capability. This PR cannot and does not satisfy those future gates.
Residual risks
MarketAdapterprotocol still describes mutation methods, while the concrete Polymarket implementation fails closed; removing those protocol members is broader API cleanupTracks #2
Closes #11