Skip to content

Rollout: idea→initiative pipeline — staged ring rollout #515

Closed

Description

@don-petry

Operational tracker for rolling the idea→initiative caller stubs (initiative-planner, idea-triage, idea-enhancer) across the fleet using ring discipline. The formal ring/release-channel standard is a separate initiative — this issue only governs this rollout.

Ring → repo map

Ring Channel tag Repos Notes
next <name>/next hosting repo (local ./ ref ⇒ always main) .github is host/next for these 3 reusables
ring0 <name>/ring0 .github = host/next for these reusables (no separate ring0 consumer)
ring1 <name>/ring1 TalkTerm, bmad-bgreat-suite early adopters
stable <name>/stable markets, ContentTwin, google-app-scripts, broodly broad production

Channels cut at v1.0.0 (4d05546). For a first version all rings coincide; staging is by enrollment order + future-version promotion.

Promotion gate (per maintainer guidance)

Before promoting a change (or enrolling the next ring), the lower ring must show:

  • healthy runs ≥ the 7-day moving average of its daily run count, AND
  • failure rate ≤ the baseline, AND
  • every failure investigated and confirmed pre-existing (not caused by the change).

Note: the idea-pipeline is event-driven (low run volume), so the 7-day daily-run average — and thus the soak threshold — is small; the gate is mainly "confirm no new failures before widening."

Rollout state

Per-repo enrollment checklist (when a ring's gate passes)

  1. Copy standards/workflows/{initiative-planner,idea-triage,idea-enhancer}.yml, repin uses: …@<name>/<ring>.
  2. Enable Discussions + "Ideas" category; create idea:approved label.
  3. Confirm GH_PAT_WORKFLOWS owner has write to the repo.
  4. Point add-to-project per the hybrid board rule.

Activity

  1. don-petry commented on Jun 21, 2026

    @don-petry
    ContributorAuthor

    Realignment (per discussion .github-private#866 + Release Strategy epic .github-private#495)

    1. idea-enhancer removed from this rollout. #866's archaeology shows idea-enhancer duplicates feature-ideation's discussion:created enhancement mode (both enhance the same new human idea, un-deduped). It is to be deprecated and folded into feature-ideation, not rolled out. Its ring + version tags (idea-enhancer/{next,ring0,ring1,stable,v1.0.0}) have been deleted. The standards/workflows/idea-enhancer.yml stub + idea-enhancer-reusable.yml are now inert (no consumers) and will be removed by the #866 consolidation initiative.

    2. bmad-bgreat-suite stays in ring1 (maintainer decision; overrides #866's stable placement).

    3. Align with the existing framework, don't reinvent. The org already has the canary/ring release process (epic #495): immutable <agent>/vX.Y.Z + channel tags managed by scripts/cut-release.sh, documented in docs/release/versioning.md; dev-lead and pr-review already ship {next,ring0,ring1,stable}. The initiative-planner + idea-triage ring tags I cut here with raw git tag are interim — they should be migrated under cut-release.sh (extend its valid_agent allow-list beyond pr-review|dev-lead) so promotion is health-checked and rollback is a framework pointer-flip. This tracker defers to epic #495's model.

    Revised rollout scope: initiative-planner + idea-triage only (enhancer consolidated separately via #866).

  2. added 4 commits that reference this issue on Jul 10, 2026
  3. added 10 commits that reference this issue on Aug 3, 2026
  4. added 11 commits that reference this issue on Aug 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions