Skip to content

[#1086 slice 3] Record dev-lead's next-tier SC2 contradiction explicitly in canary-rings.json #1122

Open

Description

@don-petry

Story

As a maintainer reading the ring registry,
I want dev-lead's next tier's SC2 contradiction recorded explicitly in standards/canary-rings.json,
so that the topology says what actually happens instead of implying a tier that can never have an occupant.

Slice 3 of #1086 (its AC4). Blocked by slice 2, whose NO_COVERAGE state this slice relies on.

Acceptance Criteria

  1. Resolve dev-lead's next tier explicitly. Either mark it non-evidence-bearing (so next->ring0 evaluates as NO_COVERAGE by design), or give it a real non-self-hosting member that pins dev-lead/v139-next, following the pr-review-trigger.yml pattern. Record the choice and the SC2 reason next to the entry.
  2. Do not weaken SC2. .github-private's dev-lead.yml stays pinned to a stable-tier channel; tests/test_sc2_self_review_channel.bats must stay green.
  3. Registry-agreement tests stay green (ring-pins.bats, canary_rollout.bats).

Blocked by #1121 (slice 2).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions