Track implementation of the accepted Base governance plan #2665

Problem

The accepted governance design and implementation sequence were merged through PR #2664. Design review issue #2663 is closed. The implementation plan contains 21 work packages, several existing issues whose earlier scopes needed reconciliation, and repository-specific rollout work. This tracker maintains the crosswalk and sequencing; it does not authorize implementation by itself.

Expected behavior

• Every implementation deliverable has a bounded issue, acceptance criteria, validation evidence, dependencies and impact categories.
• Existing issue numbers are reused only where their scope was reconciled to the accepted plan.
• One issue/one PR is the default. Multi-PR exceptions name slices; status follows the accepted slice and PR lifecycle rules.
• New work remains in Backlog or Triage until its own readiness review is complete.
• Implementation PRs use the accepted documentation-impact and release-note contract.

Decisions and boundaries

• The accepted governance plan is the source: PR #2664, with 21 packages and staged dependencies.
• Issue and PR review loops each start with a three-round limit. Issues remain the canonical home for Project fields; those fields are not copied to PRs.
• basefoundry/.github is in the organization inventory, but its repository has Issues disabled. Track its work through Base-owned issue #2685 and title inventory #2690; do not enable Issues just for this rollout. No base_manifest.yaml or governance/ directory is required in .github.
• homebrew-base has Issues and a Project but no base_manifest.yaml; its adoption issue includes the minimal-manifest work. Its issues are represented in the Base Project because the repository has no local Project.
• The repository rollout covers every repository in basefoundry: ecosystem defaults for first-party repositories, consumer defaults for banyanlabs, and the explicitly tracked .github config-repository work.
• The .ai-context/ files remain until the replacement basectl export-context ships and is proven; only then do separate repository cleanup trains run.
• Automated review starts read-only. Automated fixes remain deferred to a separate authorization decision. No release freeze or fixed date is imposed.

Work-package crosswalk

Repository rollout issues

Each adoption or title migration issue is a separate repository-local issue/PR train. The .github exceptions are Base-owned because that repository has Issues disabled.

• Adoption: base-cli#507; base-bash-libs#585; banyanlabs#87; base-workspace#19; base-platform-tools#16; base-bash-libs-demo#84; base-cli-demo#61; base-demo#372; homebrew-base#96.
• Open-title migration: base-cli#508; base-bash-libs#586; banyanlabs#88; base-workspace#20; base-platform-tools#17; base-bash-libs-demo#85; base-cli-demo#62; base-demo#373; homebrew-base#97; Base #2689; .github #2690.
• Context-file cleanup: Base #2688, base-cli#509 and base-demo#374; all wait for the replacement export release and proof.

Reconciled existing issues

Issues #1613, #2571, #2572, #2573, #2576, #2580, #2581, #2583, #2584, and #2599 have been rewritten to bounded plan scopes, acceptance criteria, dependencies and validation. #2599 retains its pre-existing parent #2555 because GitHub allows only one parent; it is cross-linked above and remains blocked by the package prerequisites.

• #2574 remains closed as superseded; human maintainer merge authority is tracked in package 9.
• #2627 remains closed as not planned; context is generated outside the repository by the planned replacement.
• #2631 and #2632 are superseded by accepted PR Revise the Base ecosystem governance design and implementation plan #2664 and this issue-level crosswalk.
• #2663 remains the closed design-review record, not an implementation parent.

Readiness and sequencing

The linked tasks are intentionally in Backlog or Triage. Review each issue against the accepted plan before moving it to Ready. Follow the plan's stages and dependencies: establish source contracts and baseline; run manual loops; build dry-run/warn-only deterministic checks; pin before automated use; then pilot drift checks and read-only review; adopt across repositories; replace AI context only after the new export is released and proven. Packages 15 and automated repairs remain deferred until their evidence and separate authorization gates are satisfied.

Impact and evidence

1. Product intent: Tracks the accepted plan without changing product behavior.
2. Architecture and contracts: Source is the accepted design and plan in PR Revise the Base ecosystem governance design and implementation plan #2664.
3. User guidance: Package issues identify exact documentation impacts; this tracker carries the crosswalk.
4. CLI/API and reference: Tracked in configuration, release-note and export-context issues.
5. Operations and safety: Human merge authority and read-only/security gates are explicit; automated fixes are not authorized.
6. Validation and testing: Every implementation issue has focused criteria/evidence; verify these before Ready.
7. Examples and downstream use: Repository adoption issues are listed above, including banyanlabs consumer defaults and homebrew-base manifest work.
8. Governance and contributor process: Issue/PR contracts, loops, lifecycle, templates and review rules are separately tracked.
9. Decision records: The closed design review remains the source of accepted decisions; deviations need maintainer approval and a new record.
10. Release notes: Each implementation PR supplies a release-note line or reasoned none.

Plan

• S1: Complete source contracts and baseline before the manual pilot.
• S2: Run and evaluate the manual issue/PR loops before enabling checks.
• S3: Introduce checks warn-only, pin them before first automated use, and promote per rule only with evidence.
• S4: Pilot read-only review with least privilege; keep fixes separately gated.
• S5: Roll out repository by repository; remove .ai-context/ only after the replacement is released and proven.