Repository navigation
Conversation
zibi-pplx
added this pull request to stack #768
October 21, 2026 07:56
zibi-pplx
force-pushed
the
codex/qualified-execution-selection
branch
from
October 21, 2026 13:40
9e079a9 to
04911e8
Compare
zibi-pplx
changed the title
zibi-pplx
removed this pull request from stack #768
October 21, 2026 13:44
zibi-pplx
added this pull request to stack #779
October 21, 2026 13:45
zibi-pplx
force-pushed
the
codex/qualified-execution-selection
branch
2 times, most recently
from
October 21, 2026 14:37
c7e49c6 to
a7a1cc0
Compare
Cold boots and restores prefer the recorded environment, then select only a qualified, allowed, locally verified compatible consumer when the source is revoked, absent or permanently unavailable. A transient failure of the exact source returns an error instead of changing execution. Cold boots preserve the kernel; restores also preserve the qualified state-format profile. Parse policy entries into environment identities or the separate legacy permission. Defaults and the historical E0 restore exception use the initial identity rather than a catalog display name. Parse runtime ordering versions when constructing compiled bindings; compatible selection never ranks or replaces kernels. Scratch builds use ordinary default resolution and have no compatible-selection variant. Keep trust, installation and selection separate. Adding an allowed environment does not upgrade existing work; exact requests and retries retain exact admission. ARM and custom historical contracts remain available through the explicit legacy permission. Validation: offline cargo check passed for runtime-core, node-manager, build-manager, common-core and execution-common, including their test targets. Protobuf descriptor generation and formatting passed. Added focused configuration, identity and stored-JSON regressions; test execution and KVM validation remain with CI.
zibi-pplx
force-pushed
the
codex/qualified-execution-selection
branch
from
October 21, 2026 15:41
a7a1cc0 to
d60be10
Compare
This branch has not been deployed
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.
Cold boots and restores prefer the recorded environment, then select only a qualified, allowed, locally verified compatible consumer when the source is revoked, absent or permanently unavailable. A transient failure of the exact source returns an error instead of changing execution. Cold boots preserve the kernel; restores also preserve the qualified state-format profile.
Parse policy entries into environment identities or the separate legacy permission. Defaults and the historical E0 restore exception use the initial identity rather than a catalog display name. Parse runtime ordering versions when constructing compiled bindings; compatible selection never ranks or replaces kernels. Scratch builds use ordinary default resolution and have no compatible-selection variant.
Keep trust, installation and selection separate. Adding an allowed environment does not upgrade existing work; exact requests and retries retain exact admission. ARM and custom historical contracts remain available through the explicit legacy permission.
Validation: offline cargo check passed for runtime-core, node-manager, build-manager, common-core and execution-common, including their test targets. Protobuf descriptor generation and formatting passed. Added focused configuration, identity and stored-JSON regressions; test execution and KVM validation remain with CI.