[codex] Add policy decision explainability guide#45
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.
Brief Design Summary
This PR adds a reviewer-facing policy decision explainability guide for the JSON policy metadata added in v0.8 work.
The guide explains where
decision_reason,policy_rule,severity_source,matched_threshold, andobserved_valueappear, how reviewers and CI consumers can interpret them, and the non-claims around dependency safety, CVEs, and network behavior.This PR also fixes stale reviewer-facing v0.6.0 release references now that v0.7.0 is the current GitHub Release, updates the consumer GitHub Actions example to install the v0.7.0 wheel, and keeps the production PyPI decision gate explicitly deferred without adding any publishing path.
No runtime behavior, CLI flags, JSON schema, SARIF/Markdown output behavior, workflows, package metadata, release tags, or PyPI/TestPyPI publishing changed.
Files Changed
tools/sbom-diff-and-risk/docs/policy-decision-explainability.mdtools/sbom-diff-and-risk/README.mdtools/sbom-diff-and-risk/docs/report-schema.mdtools/sbom-diff-and-risk/docs/policy-schema.mdtools/sbom-diff-and-risk/docs/reviewer-brief.mdtools/sbom-diff-and-risk/docs/reviewer-evidence-pack.mdtools/sbom-diff-and-risk/docs/github-actions-consumer-example.mdtools/sbom-diff-and-risk/examples/github-actions-consumer.ymltools/sbom-diff-and-risk/docs/pypi-production-publishing-decision.mdValidation
git diff --checkpassed.0.7.0..github/workflowswas unchanged and no production PyPI workflow exists.Out of Scope