Allow manual SOXL job workflow identity - #175
Merged
Merged
Conversation
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.
The manual SOXL workflow passed its bounded P1 input verification but the AI service rejected job admission because the job workflow identity was not allowed. The deployment defaults added the workflow identity to
ALLOWED_WORKFLOW_REFSonly, while the existing verifier independently checksALLOWED_JOB_WORKFLOW_REFSwhen that claim is present. The original test omitted that claim.Add the same exact AIAuditBridge manual workflow on protected main to the job-workflow defaults in the deployment script and its caller. Keep all other workflow identities, QPK pins, direct-call behavior and authentication rules unchanged. Exercise both claims using the actual deployment defaults, including mismatched job and branch rejection.
This does not rerun the failed research, change AI routing, or relax source, numeric, promotion or trading controls. Production configuration and another bounded run remain separate operations under the applicable recovery authorization.
Validation: the new claim case first failed against the old deployment defaults with
OIDC job workflow ref is not allowed. After the two-line configuration change, all 12 manual-learning tests and the deployment-default consistency test pass; the focused authentication/consistency subset also passes. Actionlint, Ruff andgit diff --checkpass. Both configured lists match exactly and contain the new identity once. No remote authentication request, model call, deployment or research retry was made during this correction.