OPC: reject scope drift and premature global stop - #13
Merged
Merged
Conversation
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.
Why
This is an incident-driven OPC hardening pass from a real failure mode: a leaf publish blocker was incorrectly promoted into a global stop, and the owner turn then drifted into unrelated business lines.
What
opc continuationverifierleaf_blocker_promoted_globalpremature_global_stopscope_drift_without_handoffBoundary
This does not add a parallel orchestration system. It makes the existing Task Continuity contract executable: one canonical task, stable owner, replaceable worker, explicit handoff for scope changes.
Local verification
No production topology, private prompts, scheduler bindings, wallet/trading data, or exact quota routing are exposed.