Validate complete SOXL P1 inputs on the VPS - #173
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 VPS readback currently verifies only that the original SOXL P1 completion object exists. Read all four exact objects under the existing restricted identity and call the original pinned UESP input and completion validators, accepting only the expected manifest digest.
Install the original locked runtime before minting the short-lived credential. Bound input sizes and command times, reject missing or invalid temporary identity without personal ADC fallback, emit only safe result fields, and remove temporary input files on success or failure. This workflow performs no model call, research, provider acquisition, or trading.
Validation: six workflow behavior tests passed; actionlint and git diff checks passed. Both actual original validators also passed an isolated synthetic P1 integration check using the pinned runtime. A single real VPS input check remains pending after merge.