ci: run the five gates on pull requests — the merge-gated regime's prerequisite - #8
Merged
Conversation
…d for the merge-gated regime The park condition (the D4 origin re-point) landed 2026-07-12; the stale header comment was misinformation in a load-bearing file. Under the coming main ruleset (pushes illegal, merges the only ingestion), PR verdicts become load-bearing: required status checks read the ratchet on the PR surface, so every merge carries its verdict before landing. Same five mutually-independent jobs, no paths filters, concurrency groups keyed per ref so PR runs never cancel main runs.
ascalva
force-pushed
the
workflow/ci-on-prs
branch
from
July 28, 2026 17:03
7d93f8f to
9aa0c95
Compare
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.
What
Adds
pull_request:(base: main) toci.ymland retires the stale header comment that still cited the Item 11b park — its condition (the D4 origin re-point) landed 2026-07-12.Why now
The owner's ruling this morning: many independent orchestrators produce PRs; auditors + owner at merge are THE gate, enforced externally; pushes to main become illegal on the GitHub side. Under that ruleset, merges are the only ingestion — so the verdict must exist on the PR surface, before landing. This is the sequencing prerequisite: CI-on-PRs first, then the ruleset (require PR + code-owner approval + required status checks + no bypass), then the identity split (finding-0276: a scoped credential so the ruleset cannot be edited by the thing it binds).
Notes
paths:filters (P2 posture unchanged).github.ref, so PR runs and main runs never cancel each other.🤖 Generated with Claude Code
https://claude.ai/code/session_01GTYQT2QsWskJW4HmgobyrV