Repository navigation
Conversation
This branch has not been deployed
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.
Canonical governance-only change. PR #503 now contains the single AI engineering operating contract, thin Copilot/custom-agent adapters, and the scoped Founder CODEOWNERS lock for protected governance/release-control surfaces. It forbids overrides/patches/stacked duplicate authorities; protects proof integrity, identity/lineage, data/migrations, concurrency/queues/caches, security/privacy, providers/cloud/cost, dependencies/supply-chain, cross-version contracts, rollback/history/evidence, and unknown-case handling; and prevents AI from editing governance to self-authorize. It also requires approval identity to be separate from mutation identity: automation using the Founder credential is not itself Founder approval. No runtime application code, release workflow, deployment script, migration, or production configuration is changed. After this CODEOWNERS file is on the protected base, enable Require review from Code Owners in the existing ruleset; keep global required approvals at 0 so ordinary PRs are not globally blocked, keep bypass actors empty, and keep strict architecture-validation required.