[governance] Document main branch ruleset evidence - #3
Merged
Conversation
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
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
Adds an audit-ready governance evidence document for the manually configured
mainbranch ruleset.Why this matters
GitHub Rulesets are repository settings and are not stored directly as versioned source files. This document records the intended ruleset state after branch protection and required CI were configured.
Evidence recorded
main-defensive-ci-protectionmainStatic Defensive ValidationDefensive scope
This change documents repository governance only. It does not scan external targets, install dependencies, run offensive tests, or modify runtime app behavior.
Validation expectation
This PR should trigger the
Static Defensive Validationworkflow and prove that the new CI gate is active on pull requests.