[codex] Document conditioned account-root trust calibration#75
Merged
InfoSecHack merged 1 commit intoJun 6, 2026
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 a docs-only design note for the next admin_reachability calibration candidate: whether conditioned account-root trust narrowed by aws:PrincipalArn can count as a clean AssumeRole trust witness. Captures the real-pilot trigger, candidate safe clean-trust rule, ambiguous cases, required tests, expected impact, risks, non-claims, and exact next slice. Validation: targeted greps passed; account and ARN hygiene scans clean; Terraform/raw artifact scan clean; scripts/check.sh passed; scripts/test_fast.sh passed with 2059 tests; git diff --check passed.