Skip to content

Commit c3c2efa

Browse files
codexcodex
committed
PR_26175_OWNER_043: align active team registry with Delta and Gamma
1 parent 6d94477 commit c3c2efa

13 files changed

Lines changed: 594 additions & 560 deletions

‎docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,3 +57,23 @@ Rules:
5757
- Teams pull backlog items only from their ownership area unless OWNER explicitly reassigns or splits the work.
5858
- Cross-team work requires OWNER approval and must identify the owning team for each PR.
5959
- Team start commands must remain aligned with this ownership model.
60+
61+
## Current Active-Capable Team Map
62+
63+
OWNER override approved: align active team governance with Delta and Gamma.
64+
65+
The current active-capable team map includes:
66+
67+
- Team Alfa
68+
- Team Bravo
69+
- Team Charlie
70+
- Team Delta
71+
- Team Gamma
72+
- Team OWNER
73+
74+
Clarification:
75+
- The four-team ownership model remains the current backlog ownership model for Alfa, Bravo, Charlie, and Delta.
76+
- Team Gamma is valid and active-capable for now because another PC may be working on it.
77+
- Do not retire Team Gamma unless OWNER explicitly approves that retirement.
78+
- 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.
79+
- 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‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -90,6 +90,28 @@ Create one Team Delta branch for the selected assignment.
9090
Work only that assignment.
9191
```
9292

93+
## Start Team Gamma
94+
95+
Ready-to-copy command:
96+
97+
```text
98+
OWNER override approved: Start Team Gamma from the ProjectInstructions release gate.
99+
100+
Read docs_build/dev/ProjectInstructions/README.txt first.
101+
Read docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md.
102+
Read docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md.
103+
Read docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md.
104+
105+
Stop if Team Gamma already has an active branch.
106+
Stop if Team Gamma already has an active assignment.
107+
Stop if OWNER has not explicitly assigned Team Gamma work.
108+
Stop if the selected work conflicts with current Alfa, Bravo, Charlie, or Delta ownership.
109+
110+
Record the selected assignment under Team Gamma in TEAM_ASSIGNMENTS.md.
111+
Create or use one Team Gamma branch for the selected assignment.
112+
Work only that assignment.
113+
```
114+
93115
## Day Work / EOD Merge Reminder
94116

95117
Ready-to-copy reminder:

‎docs_build/dev/ProjectInstructions/addendums/multi_team.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,26 @@ Rules:
1313
- Cross-team work requires OWNER approval and must identify the correct owning team for each PR.
1414
- Team start commands must use the current ownership model before pulling a backlog item.
1515

16+
## Current Active-Capable Team Map
17+
18+
OWNER override approved: align active team governance with Delta and Gamma.
19+
20+
The active-capable team map currently includes:
21+
22+
- Team Alfa
23+
- Team Bravo
24+
- Team Charlie
25+
- Team Delta
26+
- Team Gamma
27+
- Team OWNER
28+
29+
Rules:
30+
- Historical four-team ownership wording remains preserved for backlog ownership traceability.
31+
- Team Gamma remains valid and active-capable for now because another PC may be working on it.
32+
- Do not retire Team Gamma unless OWNER explicitly approves retirement.
33+
- Team Gamma may be active when it has OWNER-assigned work, an active branch, an active draft/open PR, or active release/cleanup responsibility.
34+
- If Team Gamma work touches an Alfa, Bravo, Charlie, or Delta ownership area, the PR must document the OWNER assignment or cross-team decision.
35+
1636
## All-Team Preferred Codex Execution Method
1737

1838
Preferred execution model:

‎docs_build/dev/ProjectInstructions/addendums/pr_workflow.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,8 @@ Applies to:
5454
- Team Alfa
5555
- Team Bravo
5656
- Team Charlie
57+
- Team Delta
58+
- Team Gamma
5759
- Any future NATO-named team
5860

5961
Behavior:

‎docs_build/dev/ProjectInstructions/addendums/team_release_readiness.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,12 @@
44

55
This gate prevents Team Alfa, Team Bravo, Team Charlie, or Team OWNER from starting regular assigned work before the ProjectInstructions operating system is ready.
66

7+
Current OWNER clarification:
8+
- The current release-readiness gate also applies to Team Delta and Team Gamma.
9+
- Team Gamma is valid and active-capable for now because another PC may be working on it.
10+
- Do not retire Team Gamma unless OWNER explicitly approves retirement.
11+
- Historical wording that listed fewer teams remains traceable, but it must not exclude Delta or Gamma from current active-capable governance.
12+
713
## Release Rule
814

915
Teams may start only when all of the following are true:

‎docs_build/dev/ProjectInstructions/addendums/team_start_and_release.md‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,25 @@ The current active delivery teams for backlog start commands are:
3131

3232
Each team start must confirm the selected backlog item is inside that team's ownership area.
3333

34+
## Current Active-Capable Start Map
35+
36+
OWNER override approved: align active team governance with Delta and Gamma.
37+
38+
The current active-capable start map includes:
39+
40+
- Team Alfa
41+
- Team Bravo
42+
- Team Charlie
43+
- Team Delta
44+
- Team Gamma
45+
- Team OWNER
46+
47+
Clarification:
48+
- The four-team start set remains the backlog ownership start set for Alfa, Bravo, Charlie, and Delta.
49+
- Team Gamma is valid and active-capable for OWNER-assigned, branch-backed, PR-backed, release, or cleanup work.
50+
- Do not retire Team Gamma unless OWNER explicitly approves retirement.
51+
- Gamma work must not silently take ownership from Alfa, Bravo, Charlie, or Delta; cross-team work requires OWNER approval.
52+
3453
## Assignment Flow
3554

3655
For backlog-driven work:

‎docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -162,6 +162,12 @@
162162

163163
## Four-Team Backlog Alignment
164164

165+
Current OWNER clarification:
166+
- The backlog alignment below preserves the current Alfa, Bravo, Charlie, and Delta ownership model.
167+
- 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.
168+
- Do not retire Team Gamma unless OWNER explicitly approves retirement.
169+
- 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.
170+
165171
### Team Alfa
166172

167173
- [ ] Alfa - Game Hub polish

‎docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,23 @@ If a team has no assignment, no active branch, and no active PR, it is inactive
2828

2929
| Team | Active Assignment | Branch | PR | Status | OWNER Decision |
3030
|------|-------------------|--------|----|--------|----------------|
31+
| Team Alfa | none | none | none | Available | Active-capable under current OWNER map |
32+
| Team Bravo | none | none | none | Available | Active-capable under current OWNER map |
33+
| Team Charlie | none | none | none | Available | Active-capable under current OWNER map |
34+
| Team Delta | none | none | none | Available | Active-capable under current OWNER map |
35+
| Team Gamma | none | unknown external PC possible | unknown external PR possible | Active-capable | Do not retire Gamma without explicit OWNER approval |
3136
| Team OWNER | none | none | none | Available | Governance Phase 1 complete |
3237

38+
## Current Active-Capable Team Map
39+
40+
OWNER override approved: align active team governance with Delta and Gamma.
41+
42+
The current active-capable team map includes Team Alfa, Team Bravo, Team Charlie, Team Delta, Team Gamma, and Team OWNER.
43+
44+
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.
45+
46+
Historical four-team wording remains preserved for backlog ownership traceability, but it must not be read as excluding Team Gamma from active-capable governance.
47+
3348
## Update Rules
3449

3550
Update the registry when:

‎docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,12 @@
44

55
| Team | Assignment | Branch | PR | Status |
66
|------|------------|--------|----|--------|
7+
| Team Alfa | none | none | none | Available |
8+
| Team Bravo | none | none | none | Available |
9+
| Team Charlie | none | none | none | Available |
10+
| Team Delta | none | none | none | Available |
11+
| Team Gamma | none | unknown external PC possible | unknown external PR possible | Active-capable |
12+
| Team OWNER | none | none | none | Available |
713

814
Rules:
915
- Registry is the authoritative active-work view.
@@ -27,6 +33,12 @@ Result:
2733
If a team is missing from Active Team Registry:
2834
it is currently inactive.
2935

36+
Current OWNER clarification:
37+
- The active-capable team map includes Team Alfa, Team Bravo, Team Charlie, Team Delta, Team Gamma, and Team OWNER.
38+
- Team Gamma remains valid and active-capable for now because another PC may be working on it.
39+
- Do not retire Team Gamma unless OWNER explicitly approves retirement.
40+
- Historical four-team wording remains preserved for backlog ownership traceability, but it must not exclude Gamma from active-capable governance.
41+
3042
## Assignment Status Legend
3143

3244
- Available: team may pull one `[ ]` backlog item when explicitly instructed.
@@ -65,6 +77,18 @@ Active assignment: none.
6577

6678
Active branch: none.
6779

80+
## Team Gamma
81+
82+
Status: Active-capable
83+
84+
Active assignment: none recorded locally.
85+
86+
Active branch: unknown external PC possible.
87+
88+
Active PR: unknown external PR possible.
89+
90+
OWNER decision: Do not retire Gamma without explicit OWNER approval.
91+
6892
## Team OWNER
6993

7094
Status: Available

‎docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,27 @@ Alfa, Bravo, Charlie, and Delta are the four active delivery teams for backlog o
5252

5353
Each team may pull only from its ownership area unless OWNER explicitly reassigns, splits, or approves cross-team work.
5454

55+
## Current Active-Capable Team Map
56+
57+
OWNER override approved: align active team governance with Delta and Gamma.
58+
59+
The current active-capable team map includes:
60+
61+
- Team Alfa
62+
- Team Bravo
63+
- Team Charlie
64+
- Team Delta
65+
- Team Gamma
66+
- Team OWNER
67+
68+
Clarification:
69+
- The four-team rule remains the current backlog ownership model for Alfa, Bravo, Charlie, and Delta.
70+
- Team Gamma is valid and active-capable for now because another PC may be working on it.
71+
- Team Gamma does not receive a standing backlog ownership area in this file.
72+
- Do not retire Team Gamma unless OWNER explicitly approves retirement.
73+
- Gamma work requires OWNER assignment, an active branch, an active draft/open PR, or active release/cleanup responsibility.
74+
- Gamma work that touches Alfa, Bravo, Charlie, or Delta areas must document the OWNER cross-team decision.
75+
5576
## Rule
5677

5778
Ownership may only be reassigned by OWNER governance.

0 commit comments

Comments
 (0)