Skip to content

Define publish fallback and escalation protocol #559

New issue
New issue
Closed
Closed
Define publish fallback and escalation protocol#559
Labels
go:needs-researchNeeds investigationrelease:nextTargeted for next releasesquadSquad triage inbox — Lead will assign to a member

Description

@bradygaster
bradygaster
opened on Mar 23, 2026

From v0.9.1 retro (A4): Define two publish paths: primary (CI workflow) and fallback (local direct publish). Coordinator agents must escalate to human Release Manager if the workflow fails more than once. This provides a clear escalation path during release incidents.

Acceptance Criteria:

  • Document primary publish flow (CI-based)
  • Document fallback publish flow (local direct)
  • Clear escalation criteria (failure threshold)
  • Release Manager contact/notification procedure
  • Decision tree in PUBLISH-README.md

Activity

  1. bradygaster
    added
    squadSquad triage inbox — Lead will assign to a member
    release:nextTargeted for next release
    on Mar 23, 2026
  2. github-actions
    added
    squad:flight
    go:needs-researchNeeds investigation
    on Mar 23, 2026

  3. github-actions commented on Mar 23, 2026

    @github-actions
    github-actionsBot
    on Mar 23, 2026 – with GitHub Actions
    Contributor

    🏗️ Squad Triage — Flight (Lead)

    Issue: #559 — Define publish fallback and escalation protocol
    Assigned to: Flight (Lead)
    Reason: No specific domain match — assigned to Lead for further analysis

    @copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

    Team roster:

    • Flight (Lead) → label: squad:flight
    • Procedures (Prompt Engineer) → label: squad:procedures
    • EECOM (Core Dev) → label: squad:eecom
    • FIDO (Quality Owner) → label: squad:fido
    • PAO (DevRel) → label: squad:pao
    • CAPCOM (SDK Expert) → label: squad:capcom
    • CONTROL (TypeScript Engineer) → label: squad:control
    • Surgeon (Release Manager) → label: squad:surgeon
    • Booster (CI/CD Engineer) → label: squad:booster
    • GNC (Node.js Runtime) → label: squad:gnc
    • Network (Distribution) → label: squad:network
    • RETRO (Security) → label: squad:retro
    • INCO (CLI UX & Visual Design) → label: squad:inco
    • GUIDO (VS Code Extension) → label: squad:guido
    • Telemetry (Aspire & Observability) → label: squad:telemetry
    • VOX (REPL & Interactive Shell) → label: squad:vox
    • DSKY (TUI Engineer) → label: squad:dsky
    • Sims (E2E Test Engineer) → label: squad:sims
    • Handbook (SDK Usability) → label: squad:handbook
    • Ralph (Work Monitor) → label: squad:ralph
    • @copilot (Coding Agent) → label: squad:copilot

    To reassign, remove the current squad:* label and add the correct one.

  4. bradygaster commented on Mar 24, 2026

    @bradygaster
    bradygaster
    on Mar 24, 2026
    CollaboratorAuthor

    Absorbed into #564 — fallback/escalation protocol documented in release playbook (PR #584).

  5. bradygaster
    closed this as completedon Mar 24, 2026
  6. bradygaster
    removed
    squad:flight
    on Sep 11, 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

    go:needs-researchNeeds investigationrelease:nextTargeted for next releasesquadSquad triage inbox — Lead will assign to a member

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions