Repository navigation
docs(governance): add agent baseline - #20
Merged
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.
📝 Description
Adds the organization-wide, synchronized
AGENTS.mdbaseline and documents how repositories extend it through an optionalAGENTS.local.md.The baseline links agents to the central Brand repository and its canonical product, design, and generated-asset references. It also records shared Git, pull-request, security, privacy, baseline-sync, and AI-assisted-work rules without imposing Core-specific architecture on every repository. It also protects both global and local agent-guidance files from untrusted pull-request changes.
Refs PAB-52
🧩 Type of Change
🗺️ Areas
🧪 Testing and Validation
🔐 Security, Compatibility, and Operations
This adds a managed root-level file to the repository baseline. It does not add
credentials, network requests, runtime code, public APIs, or persisted data.
The synchronizer's existing three-way merge behavior applies to the new file.
📋 Checklist
🤖 AI Usage
🛠️ How AI Was Used
🔎 AI Tools and Human Review
Codex helped plan and apply the documentation and baseline-manifest changes. The
repository owner will review the complete diff, agent instructions, and
synchronization impact before merge.
✅ AI Responsibility
📸 Screenshots, Logs, or Traces
Not applicable.
💬 Additional Context
The follow-up Core PR will add only
AGENTS.local.md. It will not alter thiscentral baseline.