docs: mark the planned CS-RG managed-execution design as suspended - #75
Merged
Merged
Conversation
DevGuard's owner put its CS-RG integration plan on hold before any implementation, pending an owner-directed integration-boundary revalidation. That plan includes the default of a CodeSpace-owned Unix transport for required execution and the planned legacy-backend decision. Add status notices under the titles and affected sections of the Codex reuse, DevGuard integration, execution contracts, architecture and upstream update pages, with matching Korean notices and reviewed hashes. Nothing is deleted or reworded. Current behavior, implemented contracts, dependency and CI rules are unchanged. No replacement architecture is approved and no safety requirement is relaxed.
This was referenced Sep 27, 2026
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.
Summary
Marks the planned CS-RG managed-execution design as a suspended implementation directive while DevGuard's owner-directed CS-RG integration-boundary revalidation is pending. Documentation only: it adds status notices and deletes or rewords nothing.
Why
The owner put DevGuard's CS-RG plan on hold before any implementation, including the default of a CodeSpace-owned Unix transport for
requiredexecution and the planned legacy-backend decision. These pages describe that plan as CodeSpace's target, so they are marked so that nobody implements from them in the meantime. The matching DevGuard change marks the plan itself.What changed
docs/codex-reuse.md: Reuse decisions for managed executiondocs/devguard-integration.md: CS-RG work order, Consumer boundary, Design revision 1 referencesdocs/execution-substrate.md: Planned managed-execution contractsdocs/architecture.md: the target CS-RG structure in Planned execution coordination (the current-behavior paragraph is unaffected)docs/upstream-update.md: the planned execution backends in Boundaries for future crates and backends (the dependency and CI rules are unchanged)scripts/check_docs.py record.What did not change
Verification
python3 -B scripts/check_docs.py: registry verified (17 paired documents).git diff --check: clean; the diff only adds lines.Merge and rollback
Merging requires the owner's explicit approval of this exact head. Rollback: revert this commit.
Related
docs/handoff/2026-09-27-cs-rg-boundary-revalidation.mdin DevGuard). It is a record for the owner's decision, not a design decision.Handoff (session of 2026-09-27)
.github/notes/pr75-cs-rg-suspension-handoff.md) and docs(handoff): record the close of the 2026-09-27 session DevGuard#15.1bee230595698b0974df43561bccfce67d7e8cb9, CLEAN, not merged. Merging needs the owner's approval of this exact head.