Skip to content

Decide a Squadron's end of life: archive, or delete only #362

Description

@Jacksondr5

Today a Squadron can be renamed and hard-deleted (#247). Delete is refused while unarchived agents or Crews remain; otherwise it purges the Squadron's history, and its threads then read as having an unknown home (SquadronManagementService.ts).

The Squadron definition says "End of life is archive; its details arrive with the container's growth", but no acceptance criterion covers it. Decide whether a reversible Squadron archive exists (hidden from pickers and scope, history kept) or delete is the end of life. Then write the answer into the definition as an AC. Relates to #254.

Carried over from the dogfood v0 plan's "what the current build narrows" table, which #354 removes.

Activity

  1. added
    jackson-directTaken by Jackson + Astra outside the fleet methodology; lanes never staff these
    on Sep 29, 2026
  2. Jacksondr5 commented on Oct 8, 2026

    @Jacksondr5
    OwnerAuthor

    Closing: Squadrons are retired and their behaviour is folded into projects (#412; merged in #454, #455, #456, #457, #482, #483, #484 and #489). A thread's home is now its project, so the Squadron this issue is about no longer exists. If part of this still applies to projects, reopen it or file it in those terms.

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

    jackson-directTaken by Jackson + Astra outside the fleet methodology; lanes never staff these

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions