Cite #176 from the ADR-0003 open-work note - #177
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <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.
The 2026-08-27 amendment to ADR-0003 recorded that
default_repository_permissionis live-only org state and called codifying it "open work", but pointed at no issue. Under the fleet's bless-and-forget rule, documenting a known gap is a tracking action only when an open issue owns closing it; without the reference the note is the exact anti-pattern that rule forbids.This adds the reference to #176, which owns the adoption, and notes that the same issue carries the prior question — whether the CI apply should be able to mutate org settings at all, given that
FLEET_ADMIN_TOKENalready holds the permission butterraform/README.mdannotates it "(repo creation only)". That is a question about the rails rather than about this ADR, so it is cited rather than answered here.Documentation only; no resource, variable, or input JSON changes, so the plan is expected to be a no-op.
Refs #176
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com