Repository navigation
Closed
Description
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
- next / ring0 (
.github) — live; pilot succeeded (epic Enable GitHub pull request limits to cut automation-PR noise #505 + DAG created cross-repo; 1 healthy run). Canaryinitiative-planner-canary.yml(Canary blocker: dependabot-automerge ring0->ring1 (cum_fail=1, REGRESSION) #822) provides ongoing health signal. - ring1 (
TalkTerm,bmad-bgreat-suite) — HELD pendingnextsoak gate. Enroll = copy the 3 stubs pinned@<name>/ring1, enable Discussions+Ideas+idea:approvedlabel. - stable (
markets,ContentTwin,google-app-scripts,broodly) — held pendingring1soak gate.
Per-repo enrollment checklist (when a ring's gate passes)
- Copy
standards/workflows/{initiative-planner,idea-triage,idea-enhancer}.yml, repinuses: …@<name>/<ring>. - Enable Discussions + "Ideas" category; create
idea:approvedlabel. - Confirm
GH_PAT_WORKFLOWSowner has write to the repo. - Point
add-to-projectper the hybrid board rule.
Metadata
Metadata
Assignees
Labels
No labels
Activity
don-petry commentedon Jun 21, 2026
Realignment (per discussion .github-private#866 + Release Strategy epic .github-private#495)
1.
idea-enhancerremoved from this rollout. #866's archaeology showsidea-enhancerduplicatesfeature-ideation'sdiscussion:createdenhancement mode (both enhance the same new human idea, un-deduped). It is to be deprecated and folded intofeature-ideation, not rolled out. Its ring + version tags (idea-enhancer/{next,ring0,ring1,stable,v1.0.0}) have been deleted. Thestandards/workflows/idea-enhancer.ymlstub +idea-enhancer-reusable.ymlare now inert (no consumers) and will be removed by the #866 consolidation initiative.2.
bmad-bgreat-suitestays inring1(maintainer decision; overrides #866'sstableplacement).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 byscripts/cut-release.sh, documented indocs/release/versioning.md;dev-leadandpr-reviewalready ship{next,ring0,ring1,stable}. Theinitiative-planner+idea-triagering tags I cut here with rawgit tagare interim — they should be migrated undercut-release.sh(extend itsvalid_agentallow-list beyondpr-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-triageonly (enhancer consolidated separately via #866).chore: enroll TalkTerm in idea→initiative pipeline (ring1) (#331)
chore: enroll bmad-bgreat-suite in idea→initiative pipeline (ring1) (#…
docs+ci: inline S7635 NOSONAR marker for idea-pipeline caller stubs (#…
feat(#1008): onboard initiative-planner + idea-triage to canary-rollo…
feat(#1008): onboard initiative-planner + idea-triage (organic-traffi…
feat(#651): add `unmanaged` registry mechanism; record add-to-project…
feat(#1159): register ci-failure-analyst in canary-rings.json (PR-2) (#…
feat(#1008): onboard initiative-planner + idea-triage (organic-traffi…
feat(#1159): register ci-failure-analyst in canary-rings.json (PR-2) (#…
feat(#515): register idea-enhancer in canary-rings.json (PR-B) (#660)
docs+ci: inline S7635 NOSONAR marker for idea-pipeline caller stubs (#…
feat(#1008): onboard initiative-planner + idea-triage (organic-traffi…
feat(#1159): register ci-failure-analyst in canary-rings.json (PR-2) (#…
feat(#515): register idea-enhancer in canary-rings.json (PR-B) (#660)
feat(#1008): onboard initiative-planner + idea-triage (organic-traffi…
feat(#1159): register ci-failure-analyst in canary-rings.json (PR-2) (#…
feat(#515): register idea-enhancer in canary-rings.json (PR-B) (#660)
docs+ci: inline S7635 NOSONAR marker for idea-pipeline caller stubs (#…
feat(#1008): onboard initiative-planner + idea-triage (organic-traffi…
feat(#1159): register ci-failure-analyst in canary-rings.json (PR-2) (#…
feat(#515): register idea-enhancer in canary-rings.json (PR-B) (#660)
chore: enroll TalkTerm in idea→initiative pipeline (ring1) (#331)
chore: enroll TalkTerm in idea→initiative pipeline (ring1) (#331)
chore: enroll TalkTerm in idea→initiative pipeline (ring1) (#331)
docs+ci: inline S7635 NOSONAR marker for idea-pipeline caller stubs (#…
feat(#1008): onboard initiative-planner + idea-triage (organic-traffi…
feat(#1159): register ci-failure-analyst in canary-rings.json (PR-2) (#…
feat(#515): register idea-enhancer in canary-rings.json (PR-B) (#660)