backlog(B-0580): Enterprise GitHub ruleset management — new layer above org/individual mapping#3957
Merged
AceHack merged 2 commits intoMay 16, 2026
Conversation
…ve org/individual mapping Aaron 2026-05-16, after creating a "light default" enterprise-level ruleset at #16490134: "we should backlog enterpirse ruleselt managment now we had started decomposing those too for our repo split later, they were smell we have backlog around this. but now enterpirse too not just individiual and team github mapping." Two reframings: 1. Surface expansion: Enterprise tier (new 2026-05-16 via 30-day trial, B-0572) adds a third layer above org + per-repo. Light default Aaron created is the enterprise baseline. 2. DV2.0 ruleset-divergence smell composes: per dv2-data-split-discipline-activated.md, the smell was already known for repo-split (B-0427). Enterprise multiplies the surface — now (repo × org × enterprise) potential divergence. Files the design row with 5-slice decomposition: - Slice 1: tools/github/list-rulesets.ts — REST enumeration - Slice 2: manual audit of #16490134 + any others - Slice 3: tools/github/audit-ruleset-divergence.ts — cross-layer diff - Slice 4: docs/governance/RULESETS.md — authoritative policy - Slice 5 (deferred): policy-as-code apply tool Composes with B-0427 (repo-split axis 3 — ruleset-divergence smell test), B-0572 (tier decision that created the new layer), and dv2-data-split-discipline-activated.md (DV2.0 partition-by-change-rate catches this kind of layered-governance smell). Co-Authored-By: Claude <noreply@anthropic.com>
…ce 1+2 ad-hoc) After admin:enterprise scope landed mid-session, Slices 1 (enumeration) + 2 (audit) became immediately doable via single `gh api` calls. Captured the live ruleset content in the row body so the substrate preserves the discovery + the cost-composition note: copilot_code_review on push will burn Copilot premium requests on every push, fail-closing at $0 spending limit (UI-only to set; see body). Substrate-impact note for lfg-acehack-topology.md: the non_fast_forward rule now lives at the enterprise tier (via #16490134 with ~ALL repository condition), cascading to all member orgs/repos. The rule's content is the same as what lfg-acehack-topology.md documents, but its WHERE-it-lives has changed — small rule-update opportunity, low priority. Pre-start checklist boxes #1 and #2 flipped to complete; #3 (layer context) was already checked. Co-Authored-By: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a new P2 backlog entry (B-0580) tracking enterprise-level GitHub ruleset management as a third governance layer above existing org/individual rulesets, and registers it in the main backlog index.
Changes:
- New backlog doc B-0580 describing motivation, slices, acceptance criteria, and first-discovery findings for the new enterprise ruleset created (
16490134). - Adds B-0580 entry to
docs/BACKLOG.mdunder P2.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/backlog/P2/B-0580-enterprise-ruleset-management-2026-05-16.md | New backlog row defining the 5-slice work-stream for enterprise ruleset governance. |
| docs/BACKLOG.md | Registers B-0580 in the P2 backlog list. |
AceHack
deleted the
backlog/b-0580-enterprise-ruleset-management-2026-05-16
branch
AceHack
commented
May 16, 2026
Member
Author
AceHack
left a comment
AceHack
left a comment
There was a problem hiding this comment.
Maji Antigravity Check: Drift detected. Metadata churn / narration-over-action identified. Next step: peel one slice off this design row and execute it to restore parity and operational alignment.
This was referenced May 16, 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
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
Files B-0580 — Enterprise GitHub ruleset management work-stream. Per Aaron 2026-05-16, after creating the first enterprise-level ruleset (#16490134) under the 30-day Enterprise trial: the Enterprise tier adds a THIRD ruleset layer above org + per-repo, multiplying the existing ruleset-divergence smell from B-0427.
Why
Two reframings:
dv2-data-split-discipline-activated.md— the smell was known for repo-split (B-0427); Enterprise multiplies it5-slice decomposition
tools/github/list-rulesets.ts— REST enumeration at all 3 layerstools/github/audit-ruleset-divergence.ts— cross-layer diff, flag conflictsdocs/governance/RULESETS.md— authoritative policy doc (which rule belongs at which layer)tools/github/apply-rulesets.ts— policy-as-code applyComposes with
.claude/rules/dv2-data-split-discipline-activated.md(the smell-detection framework).claude/rules/methodology-hard-limits.md(rulesets ARE policy-as-code substrate for governance hard-limits)Caveat re scope
Enterprise-layer writes (slice 5) require
admin:enterprisescope — current local PAT lacks it. Slices 1-4 work withread:orgscope (which the current PAT has). Authoritative policy doc + tooling can land before any policy-as-code apply.🤖 Generated with Claude Code