Repository navigation
Conversation
zibi-pplx
added this pull request to stack #768
October 21, 2026 07:56
zibi-pplx
force-pushed
the
codex/node-compatible-selection
branch
from
October 21, 2026 13:40
3a9c7b1 to
0d72859
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/node-compatible-selection
branch
from
October 21, 2026 13:51
0d72859 to
1e80e9e
Compare
Replace deployment-name approval and version overrides with SPACE_ALLOWED_EXECUTION_ENVIRONMENTS and SPACE_DEFAULT_EXECUTION_ENVIRONMENT. Absent settings preserve E0 and historical unbound execution; legacy permission is explicit, independently removable and cannot bypass a bound environment's revocation or activate unbound managed candidates. ARM retains its existing unbound path without claiming environment qualification. Validate configuration at startup and recheck eligibility at prepare/launch. Report compiled references and the separate legacy permission through execution inventory, periodic publication and admin inspection. Policy has an independent database receipt time, so older writers refreshing inventory cannot renew policy evidence. Missing or invalid observations withhold evidence. Compatible resolver responses acknowledge intent; fallback decisions log source/consumer identities and increment a decision counter, not a launch counter. Deploy the schema and cluster readers before publishers. Keep policy uniform within role/platform cohorts and shared fleet defaults at E0 until placement consumes environment evidence. Audit historical templates, sandboxes and snapshots before removing legacy. Policy reporting is not proof of usable installation; resident-VM incident stopping remains separate lifecycle work. Validation: offline compilation passed for node-manager, node-ctl, execution-common and internal API libraries and tests. Targeted policy, selection and wire-compatibility tests passed; historical admission and transient-source regressions were also verified failing with the old behavior. Go protobuf bindings were regenerated with the pinned compiler and compiled. Admission regression covers custom kernels, external legacy runtimes, restore without boot files and explicit legacy revocation. Database integration, full tests and KVM validation remain with CI.
zibi-pplx
force-pushed
the
codex/node-compatible-selection
branch
from
October 21, 2026 14:37
1e80e9e to
069262f
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.
Replace deployment-name approval and version overrides with SPACE_ALLOWED_EXECUTION_ENVIRONMENTS and SPACE_DEFAULT_EXECUTION_ENVIRONMENT. Absent settings preserve E0 and historical unbound execution; legacy permission is explicit, independently removable and cannot bypass a bound environment's revocation or activate unbound managed candidates. ARM retains its existing unbound path without claiming environment qualification. Validate configuration at startup and recheck eligibility at prepare/launch.
Report compiled references and the separate legacy permission through execution inventory, periodic publication and admin inspection. Policy has an independent database receipt time, so older writers refreshing inventory cannot renew policy evidence. Missing or invalid observations withhold evidence. Compatible resolver responses acknowledge intent; fallback decisions log source/consumer identities and increment a decision counter, not a launch counter.
Deploy the schema and cluster readers before publishers. Keep policy uniform within role/platform cohorts and shared fleet defaults at E0 until placement consumes environment evidence. Audit historical templates, sandboxes and snapshots before removing legacy. Policy reporting is not proof of usable installation; resident-VM incident stopping remains separate lifecycle work.
Validation: offline compilation passed for node-manager, node-ctl, execution-common and internal API libraries and tests. Targeted policy, selection and wire-compatibility tests passed; historical admission and transient-source regressions were also verified failing with the old behavior. Go protobuf bindings were regenerated with the pinned compiler and compiled. Admission regression covers custom kernels, external legacy runtimes, restore without boot files and explicit legacy revocation. Database integration, full tests and KVM validation remain with CI.