You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bootstrap the public MIT Web Components 2.0 governance system, with humans limited to product management and AI responsible for engineering. Includes the product charter, Git Flow policies, Issue forms, native Issue association, CI evidence, dependency handoff and release prerequisites. No components, package publication or release are implemented.
The required independent check is bound to App 5210232. Protected target updates require that App through PRs, without bypassing approval, CI or resolved conversations. The control worker is disabled until independently reviewed safeguards in control PR #4 are merged and verified.
Consolidated validation: seven governance/handoff regression tests, including fork-promotion rejection, Issue reference matching, both workflow extensions, failure evidence, candidate state changes and distinct commit history. The control PR adds live Issue-link and final PR-state authorization with 25 tests.
Automatic Copilot reviews are disabled in both repositories. No new paid review or spending-limit increase is authorized. Current-head independent approval and live deployment verification remain pending; Phase 0 is not complete.
Missing required files prevent governance evidence from being written
.github/scripts/validate_governance.py:19
If LICENSE or .github/ai-dlc.json is missing, this loop records the error but the unconditional reads below raise FileNotFoundError before governance-evidence.json is written. The workflow's always-run upload then fails without retaining validation evidence. Write failed evidence and exit after the required-file checks, before reading those inputs.
The final preflight checks only SHAs. If Dependabot closes a withdrawn or superseded candidate during preflight without changing those SHAs, the script still creates an Issue, branch and draft PR for it. Revalidate candidate eligibility using fresh after the SHA check and before creating resources, so a closure already visible in this response stops the handoff.
Hotfix branches encode an Issue number too (docs/governance.md:8), but this check only runs for features. A hotfix/42-fix PR targeting main with only Refs #1 therefore passes without referencing its corresponding Issue. Apply the Issue-number check to both feature and hotfix branches.
Missing final candidate validation before resource creation
.github/scripts/handoff_dependabot.py:64
The final preflight check compares only SHAs. A candidate closed during preflight can retain both SHAs, so the script still creates an Issue, branch and draft PR despite requiring an open candidate. A retarget to another branch at the same commit also passes. After checking the SHAs, call validate_candidate(fresh, comparison, files) to recheck the candidate's state, identity and target before creating resources.
This regex accepts a textual Issue reference without checking whether the Issue exists or has the native Development link required by docs/governance.md:26. The trusted control repository's verifier and merge guard do not check that association either, so an unlinked PR can satisfy the gates. Validate the live association to the corresponding Issue in the trusted pre-merge path and fail closed on missing links or API errors. A CI-only check is insufficient because removing a link does not change the approved head SHA.
This is independent engineering review evidence, not a native GitHub APPROVED review. The authenticated GitHub identity is the PR author, glyad, and cannot approve its own PR. Required native approval and trusted-App gates remain enforced. Current-head CI passes; merge/deployment and Phase 0 acceptance are not yet complete.
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
blocked:ai-approvalIndependent AI approval policy must be authorizedgovernanceAI-DLC policies, Git Flow and enforcementphase:0Autonomous engineering bootstrap; no components
2 participants
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.
Refs #1
Bootstrap the public MIT Web Components 2.0 governance system, with humans limited to product management and AI responsible for engineering. Includes the product charter, Git Flow policies, Issue forms, native Issue association, CI evidence, dependency handoff and release prerequisites. No components, package publication or release are implemented.
The required independent check is bound to App 5210232. Protected target updates require that App through PRs, without bypassing approval, CI or resolved conversations. The control worker is disabled until independently reviewed safeguards in control PR #4 are merged and verified.
Consolidated validation: seven governance/handoff regression tests, including fork-promotion rejection, Issue reference matching, both workflow extensions, failure evidence, candidate state changes and distinct commit history. The control PR adds live Issue-link and final PR-state authorization with 25 tests.
Automatic Copilot reviews are disabled in both repositories. No new paid review or spending-limit increase is authorized. Current-head independent approval and live deployment verification remain pending; Phase 0 is not complete.