policy: enter roadmap construction mode - #188
Merged
Merged
Conversation
Owner
Author
Codex reviewer (cross-vendor, read-only)Reviewed-head: 7510c6c Posted verbatim by The construction-mode identities match the changed Roadmap and north-star blobs, and the consolidated test runner preserves coverage of all existing test scripts. No actionable regression was identified. |
yihanzhu
pushed a commit
that referenced
this pull request
Sep 7, 2026
#188 entered construction mode but was merged under the normal gates, so the re-review question now covers the PRs merged after it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
yihanzhu
added a commit
that referenced
this pull request
Sep 7, 2026
* Record that every construction row is merged All roadmap units reached main, so the transition proposal now reads every row as merged and states that the precondition for writing the transition PR is met once the operator answers the open questions. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * Reword the open questions now that every row is merged Questions 6 and 7 still spoke of pending PRs; they now ask only whether any merged unit should be dropped or re-reviewed before the transition. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * Say which construction units had two vendors on them The reworded question 7 called every construction review cross-vendor while question 3 said Codex both wrote and reviewed; both now state that the earliest units were single-vendor and the later ones Claude-produced, Codex-reviewed. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * State the vendor history per unit instead of by era Some roadmap item 5 units after the eval framework were still Codex-authored, so the claim that every later unit was Claude-produced overstated the history. The questions now say the producer varied by unit and point at where each PR records it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * Let question 7 cover every construction PR, this one included The re-review question named a fixed PR range that left out later construction PRs, including the one carrying this change. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * Start the construction re-review range at the PR that entered the mode Construction mode began with #188, not #233; the question now names the whole active-mode span. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * Exclude the bootstrap PR from the construction-mode range #188 entered construction mode but was merged under the normal gates, so the re-review question now covers the PRs merged after it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: ci <ci@example.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.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.
Closes #187
Outcome
Enter a temporary ystack-self construction mode so the agreed Roadmap can be implemented directly as machine-gated PRs. This does not enable real-target use or operating mode.
Trust and bootstrap
The mode record binds the repository, activation base, operator-authorized source Roadmap/north-star blobs, effective post-transition blobs, frozen #183 tuple, restore-manifest trust floor, and exact desired post-transition ruleset.
The operator directly authorized this one bootstrap in the active session. This PR still requires exact CI and independent review. No other PR inherits the bootstrap. After merge, the construction session will reconcile ruleset 21500323 to PR + strict required ci + zero approvals + no bypass actors before any Roadmap unit.
Proof
This transition is intentionally auto-merged after GitHub CI and final independent Codex review. It does not wait for a human merge.