Apply an already-saved HK stop with verified runtime controls - #468
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
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.
An already-saved HK stop can now be applied by the platform: the workflow validates the exact target against its protected environment, disables the existing runtime flag and pauses matching Scheduler jobs, then verifies both controls. Ambiguous state or an uncertain write stops further mutations. In-flight requests, broker orders and account retirement remain unverified.
The workflow shares the existing deployment concurrency group and triggers the existing lifecycle readback. It does not activate accounts, cancel orders, liquidate holdings or delete resources.
Validation: 7 focused tests passed, including zero-I/O identity rejection, ambiguous cloud state, bounded writes, failure handling and unchanged unrelated configuration; Ruff, actionlint and diff checks passed. One bounded independent material review found no P1/P2. Real HK application remains a post-merge verification step.