Repository navigation
governance: adopt AETHER corporate vNext (preserve project CI and security gates) - #193
Merged
aetherxeg-source merged 1 commit intoOct 28, 2026
Conversation
aetherxeg-source
marked this pull request as ready for review
October 28, 2026 21:05
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.
Founder-wide corporate vNext operational adoption — protected repository
Scope:
AGENTS.mdonly; no runtime, production, API, IAM, trading, research claims or release changes. Founder requested applying the activated governance to all currently open AETHER X projects.Approved corporate reference: Governance activation commit, exact approved corporate tree
4ae9c6ee39ffffe4d48e28ce2b7fce8bec19d52e.Adoption: ChatGPT-first efficient internal review with reproducible tests; no universal separate institutional AETHER ASSURANCE signoff or voluntary third-party approval. All project-specific pinned rules, real security Four-Eyes, release QA, STOP/BLOCKED and existing GitHub branch protection + required CI remain effective.
Reason for PR: direct
mainwrite was rejected by existing protection. No bypass is attempted; merge only after GitHub's actual repository gates are satisfied. This PR alone does not close project-specific hard gates or make them PASS.Acceptance: verify
AGENTS.mdaddition only; retain original instructions; run/observe required applicable status checks; no spend, runner policy changes or forced merge.