[harness] Decisions impact required in every repository #71

Activity

1. wikki26 commented on Oct 31, 2026

   

   wikki26

   on Oct 31, 2026 – with ChatGPT Codex Connector

   More actions

   CI owner triage, 31 October 2026:

   This is a staged organization rollout, not a one-PR cross-repository bulk edit. The prerequisite harness design is still open in .github #70; safety/publishing review must close there before assuming that its planned automation or --require-decisions-impact behavior is active.

   Suggested order after the owner accepts the evidence-check contract:

   1. First verify the canonical example on .github and pin the applicable checker revision, with a deliberately missing or malformed Decisions impact fixture.
   2. Roll out the template and --decisions --files-json --repository checker arguments to software repos in small reviewed batches, using warning-only reporting as documented.
   3. Track actual false positives/negatives and repository owners' reviews for two weeks; only then enforce --require-decisions-impact where the prerequisite checker/run evidence is green.
   4. Treat firmware, hardware, CODEOWNERS and workflow edits as protected paths needing the corresponding human approvals. Record each repository's measured check result and reviewer instead of marking it complete from a copied template.

   Current work priorities: security review patch .github #76 awaiting Alex/Mohammad, platform shared gate #101 with DCO identity correction/re-review, and main-published image .github #41. The interfaces shared gate #29 is already merged with passing main checks; that does not by itself implement this additional PR-description policy.

   No repository is marked complete in #71 until the explicit Decisions impact acceptance check is demonstrated.