Skip to content

Reconcile GitHub rulesets and CODEOWNERS as projections #2031

Description

@shiny-code-bot

Goal

Reconcile GitHub rulesets, required checks, and CODEOWNERS as non-authoritative enforcement/routing projections of Launchplane policy.

Scope

  • Read ruleset-derived requirements as well as classic branch protection; absence or API ambiguity must fail closed in drift reporting.
  • Compare Launchplane's intended engineering/Owner check posture with actual repository rulesets and CODEOWNERS.
  • Keep CODEOWNERS assert-only/report-only; it must never supply Owner identity or authorization.
  • Add idempotent plan/apply/rollback records for bounded provider-API reconciliation.
  • Delete superseded .github/github.json authority fields as each repository cuts over; retain only non-authoritative routing/generated metadata.

Finish Line

Launchplane can produce and safely apply an auditable reconciliation plan for the canary repository, detect drift across rulesets and CODEOWNERS, and roll back without moving runtime authority into GitHub.

Parent: #2004

Current Status

State: Blocked on August 7, 2026. Re-scoped #2030 is complete and deployed; #2042 now owns the truthful live engineering-review advisory check canary.

Next action: after #2042 completes the truthful live engineering-check canary, implement assert-first ruleset and CODEOWNERS reconciliation with auditable plan/apply/rollback records.

Blocked by: #2042. Do not make either Launchplane advisory context required while the governance contracts remain shadow-only.

Waiting for: genuine product work suitable for #2042.

Last verified: August 7, 2026 from merged/deployed PR #2041, native issue relationships, and live canary repository protection state.

Metadata

Metadata

Assignees

No one assigned

    Labels

    planDurable planning issueplan:blockedPlan is blocked

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions