PR_26175_OWNER_043: align active team registry with Delta and Gamma

Author: codex

docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md

@@ -57,3 +57,23 @@ Rules:
 - Teams pull backlog items only from their ownership area unless OWNER explicitly reassigns or splits the work.
 - Cross-team work requires OWNER approval and must identify the owning team for each PR.
 - Team start commands must remain aligned with this ownership model.
+
+## Current Active-Capable Team Map
+
+OWNER override approved: align active team governance with Delta and Gamma.
+
+The current active-capable team map includes:
+
+- Team Alfa
+- Team Bravo
+- Team Charlie
+- Team Delta
+- Team Gamma
+- Team OWNER
+
+Clarification:
+- The four-team ownership model remains the current backlog ownership model for Alfa, Bravo, Charlie, and Delta.
+- Team Gamma is valid and active-capable for now because another PC may be working on it.
+- Do not retire Team Gamma unless OWNER explicitly approves that retirement.
+- Gamma work requires OWNER assignment, an active branch, an active draft/open PR, or an OWNER cleanup/release responsibility before it is treated as active.
+- Historical four-team wording remains preserved for traceability, but it must not be read as excluding Team Gamma from active-capable governance.

docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md

@@ -90,6 +90,28 @@ Create one Team Delta branch for the selected assignment.
 Work only that assignment.
 ```
 
+## Start Team Gamma
+
+Ready-to-copy command:
+
+```text
+OWNER override approved: Start Team Gamma from the ProjectInstructions release gate.
+
+Read docs_build/dev/ProjectInstructions/README.txt first.
+Read docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md.
+Read docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md.
+Read docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md.
+
+Stop if Team Gamma already has an active branch.
+Stop if Team Gamma already has an active assignment.
+Stop if OWNER has not explicitly assigned Team Gamma work.
+Stop if the selected work conflicts with current Alfa, Bravo, Charlie, or Delta ownership.
+
+Record the selected assignment under Team Gamma in TEAM_ASSIGNMENTS.md.
+Create or use one Team Gamma branch for the selected assignment.
+Work only that assignment.
+```
+
 ## Day Work / EOD Merge Reminder
 
 Ready-to-copy reminder:

docs_build/dev/ProjectInstructions/addendums/multi_team.md

@@ -13,6 +13,26 @@ Rules:
 - Cross-team work requires OWNER approval and must identify the correct owning team for each PR.
 - Team start commands must use the current ownership model before pulling a backlog item.
 
+## Current Active-Capable Team Map
+
+OWNER override approved: align active team governance with Delta and Gamma.
+
+The active-capable team map currently includes:
+
+- Team Alfa
+- Team Bravo
+- Team Charlie
+- Team Delta
+- Team Gamma
+- Team OWNER
+
+Rules:
+- Historical four-team ownership wording remains preserved for backlog ownership traceability.
+- Team Gamma remains valid and active-capable for now because another PC may be working on it.
+- Do not retire Team Gamma unless OWNER explicitly approves retirement.
+- Team Gamma may be active when it has OWNER-assigned work, an active branch, an active draft/open PR, or active release/cleanup responsibility.
+- If Team Gamma work touches an Alfa, Bravo, Charlie, or Delta ownership area, the PR must document the OWNER assignment or cross-team decision.
+
 ## All-Team Preferred Codex Execution Method
 
 Preferred execution model:

docs_build/dev/ProjectInstructions/addendums/pr_workflow.md

@@ -54,6 +54,8 @@ Applies to:
 - Team Alfa
 - Team Bravo
 - Team Charlie
+- Team Delta
+- Team Gamma
 - Any future NATO-named team
 
 Behavior:

docs_build/dev/ProjectInstructions/addendums/team_release_readiness.md

@@ -4,6 +4,12 @@
 
 This gate prevents Team Alfa, Team Bravo, Team Charlie, or Team OWNER from starting regular assigned work before the ProjectInstructions operating system is ready.
 
+Current OWNER clarification:
+- The current release-readiness gate also applies to Team Delta and Team Gamma.
+- Team Gamma is valid and active-capable for now because another PC may be working on it.
+- Do not retire Team Gamma unless OWNER explicitly approves retirement.
+- Historical wording that listed fewer teams remains traceable, but it must not exclude Delta or Gamma from current active-capable governance.
+
 ## Release Rule
 
 Teams may start only when all of the following are true:

docs_build/dev/ProjectInstructions/addendums/team_start_and_release.md

@@ -31,6 +31,25 @@ The current active delivery teams for backlog start commands are:
 
 Each team start must confirm the selected backlog item is inside that team's ownership area.
 
+## Current Active-Capable Start Map
+
+OWNER override approved: align active team governance with Delta and Gamma.
+
+The current active-capable start map includes:
+
+- Team Alfa
+- Team Bravo
+- Team Charlie
+- Team Delta
+- Team Gamma
+- Team OWNER
+
+Clarification:
+- The four-team start set remains the backlog ownership start set for Alfa, Bravo, Charlie, and Delta.
+- Team Gamma is valid and active-capable for OWNER-assigned, branch-backed, PR-backed, release, or cleanup work.
+- Do not retire Team Gamma unless OWNER explicitly approves retirement.
+- Gamma work must not silently take ownership from Alfa, Bravo, Charlie, or Delta; cross-team work requires OWNER approval.
+
 ## Assignment Flow
 
 For backlog-driven work:

docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md

@@ -162,6 +162,12 @@
 
 ## Four-Team Backlog Alignment
 
+Current OWNER clarification:
+- The backlog alignment below preserves the current Alfa, Bravo, Charlie, and Delta ownership model.
+- Team Gamma is valid and active-capable for now because another PC may be working on it, but no standing Gamma backlog ownership area is assigned here.
+- Do not retire Team Gamma unless OWNER explicitly approves retirement.
+- Gamma work must be OWNER-assigned, branch-backed, PR-backed, release, or cleanup work and must not silently replace Alfa, Bravo, Charlie, or Delta ownership.
+
 ### Team Alfa
 
 - [ ] Alfa - Game Hub polish

docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md

@@ -28,8 +28,23 @@ If a team has no assignment, no active branch, and no active PR, it is inactive
 
 | Team | Active Assignment | Branch | PR | Status | OWNER Decision |
 |------|-------------------|--------|----|--------|----------------|
+| Team Alfa | none | none | none | Available | Active-capable under current OWNER map |
+| Team Bravo | none | none | none | Available | Active-capable under current OWNER map |
+| Team Charlie | none | none | none | Available | Active-capable under current OWNER map |
+| Team Delta | none | none | none | Available | Active-capable under current OWNER map |
+| Team Gamma | none | unknown external PC possible | unknown external PR possible | Active-capable | Do not retire Gamma without explicit OWNER approval |
 | Team OWNER | none | none | none | Available | Governance Phase 1 complete |
 
+## Current Active-Capable Team Map
+
+OWNER override approved: align active team governance with Delta and Gamma.
+
+The current active-capable team map includes Team Alfa, Team Bravo, Team Charlie, Team Delta, Team Gamma, and Team OWNER.
+
+Team Gamma remains valid and active-capable for now because another PC may be working on it. Do not retire Gamma unless OWNER explicitly approves retirement.
+
+Historical four-team wording remains preserved for backlog ownership traceability, but it must not be read as excluding Team Gamma from active-capable governance.
+
 ## Update Rules
 
 Update the registry when:

docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md

@@ -4,6 +4,12 @@
 
 | Team | Assignment | Branch | PR | Status |
 |------|------------|--------|----|--------|
+| Team Alfa | none | none | none | Available |
+| Team Bravo | none | none | none | Available |
+| Team Charlie | none | none | none | Available |
+| Team Delta | none | none | none | Available |
+| Team Gamma | none | unknown external PC possible | unknown external PR possible | Active-capable |
+| Team OWNER | none | none | none | Available |
 
 Rules:
 - Registry is the authoritative active-work view.
@@ -27,6 +33,12 @@ Result:
 If a team is missing from Active Team Registry:
 it is currently inactive.
 
+Current OWNER clarification:
+- The active-capable team map includes Team Alfa, Team Bravo, Team Charlie, Team Delta, Team Gamma, and Team OWNER.
+- Team Gamma remains valid and active-capable for now because another PC may be working on it.
+- Do not retire Team Gamma unless OWNER explicitly approves retirement.
+- Historical four-team wording remains preserved for backlog ownership traceability, but it must not exclude Gamma from active-capable governance.
+
 ## Assignment Status Legend
 
 - Available: team may pull one `[ ]` backlog item when explicitly instructed.
@@ -65,6 +77,18 @@ Active assignment: none.
 
 Active branch: none.
 
+## Team Gamma
+
+Status: Active-capable
+
+Active assignment: none recorded locally.
+
+Active branch: unknown external PC possible.
+
+Active PR: unknown external PR possible.
+
+OWNER decision: Do not retire Gamma without explicit OWNER approval.
+
 ## Team OWNER
 
 Status: Available

docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md

@@ -52,6 +52,27 @@ Alfa, Bravo, Charlie, and Delta are the four active delivery teams for backlog o
 
 Each team may pull only from its ownership area unless OWNER explicitly reassigns, splits, or approves cross-team work.
 
+## Current Active-Capable Team Map
+
+OWNER override approved: align active team governance with Delta and Gamma.
+
+The current active-capable team map includes:
+
+- Team Alfa
+- Team Bravo
+- Team Charlie
+- Team Delta
+- Team Gamma
+- Team OWNER
+
+Clarification:
+- The four-team rule remains the current backlog ownership model for Alfa, Bravo, Charlie, and Delta.
+- Team Gamma is valid and active-capable for now because another PC may be working on it.
+- Team Gamma does not receive a standing backlog ownership area in this file.
+- Do not retire Team Gamma unless OWNER explicitly approves retirement.
+- Gamma work requires OWNER assignment, an active branch, an active draft/open PR, or active release/cleanup responsibility.
+- Gamma work that touches Alfa, Bravo, Charlie, or Delta areas must document the OWNER cross-team decision.
+
 ## Rule
 
 Ownership may only be reassigned by OWNER governance.