docs(governance): adopt repository trust policy - #16
Merged
Conversation
Signed-off-by: Codex <codex@openai.com>
Pull Request Summary by devActivityMetricsAchievements
|
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
Adopt the organization-facing trust-policy contract required by #9 while preserving the agreed policy-first dependency direction.
This pull request:
R0–R3);legacy-unclassified,planned,piloting,enforcing,conformant, andretiredmigration states;Dependency resolution
This is the normative policy layer, not implementation evidence:
.githubdefines the policy first.R3image requirements.Scope boundary
This pull request does not:
Validation
The branch contains one DCO-signed scoped commit over current
main.Review gates
R0–R3class matrix maps cleanly to Relay release profiles..githubresponsibilities remain separate.Fixes #9