|
| 1 | +diff --git a/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md b/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md |
| 2 | +index 7634dad42..3490df216 100644 |
| 3 | +--- a/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md |
| 4 | ++++ b/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md |
| 5 | +@@ -65,3 +65,16 @@ Add the selected assignment under Team Gamma in TEAM_ASSIGNMENTS.md. |
| 6 | + Create one Team Gamma branch for the selected assignment. |
| 7 | + Work only that assignment. |
| 8 | + ``` |
| 9 | ++ |
| 10 | ++## Day Work / EOD Merge Reminder |
| 11 | ++ |
| 12 | ++Ready-to-copy reminder: |
| 13 | ++ |
| 14 | ++```text |
| 15 | ++Commit/push during the day is allowed only on assigned team/OWNER/PR branches. |
| 16 | ++ |
| 17 | ++Merge to main is EOD-only and owner-approved, unless the owner explicitly says: |
| 18 | ++"Merge this PR now." |
| 19 | ++ |
| 20 | ++Do not treat sequential PR completion as merge approval. |
| 21 | ++``` |
1 | 22 | diff --git a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md |
2 | | -index 3408c96f2..ce04c904b 100644 |
| 23 | +index ce04c904b..0b63c376f 100644 |
3 | 24 | --- a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md |
4 | 25 | +++ b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md |
5 | | -@@ -37,3 +37,54 @@ Status: Available |
6 | | - Active assignment: none. |
7 | | - |
8 | | - Active branch: none. |
9 | | -+ |
10 | | -+## Team Name Registry |
11 | | -+ |
12 | | -+- Team Alfa |
13 | | -+- Team Bravo |
14 | | -+- Team Charlie |
15 | | -+- Team Delta |
16 | | -+- Team Echo |
17 | | -+- Team Foxtrot |
18 | | -+- Team Golf |
19 | | -+- Team Hotel |
20 | | -+- Team India |
21 | | -+- Team Juliett |
22 | | -+- Team Kilo |
23 | | -+- Team Lima |
24 | | -+- Team Mike |
25 | | -+- Team November |
26 | | -+- Team Oscar |
27 | | -+- Team Papa |
28 | | -+- Team Quebec |
29 | | -+- Team Romeo |
30 | | -+- Team Sierra |
31 | | -+- Team Tango |
32 | | -+- Team Uniform |
33 | | -+- Team Victor |
34 | | -+- Team Whiskey |
35 | | -+- Team X-ray |
36 | | -+- Team Yankee |
37 | | -+- Team Zulu |
38 | | -+- Team OWNER |
| 26 | +@@ -88,3 +88,56 @@ Rules: |
| 27 | + - stop and request owner approval for the dependency model. |
| 28 | + - Codex should reduce chit-chat by planning the full sequence before starting. |
| 29 | + - Codex must still hard-stop for conflicts, dirty worktree, scope mismatch, missing assignment, or protected instruction deletion. |
39 | 30 | + |
40 | | -+## Preferred Codex Execution Method |
| 31 | ++### All-Team Codex Execution Clarification |
41 | 32 | + |
42 | 33 | +Preferred execution model: |
43 | 34 | +Single Codex session with multiple sequential PRs. |
44 | 35 | + |
| 36 | ++Applies to: |
| 37 | ++- Team Alfa through Team Zulu |
| 38 | ++- Team OWNER |
| 39 | ++ |
45 | 40 | +Purpose: |
46 | 41 | +Reduce back-and-forth between owner and Codex while keeping PRs reviewable and scoped. |
47 | 42 | + |
48 | 43 | +Rules: |
49 | 44 | +- One Codex session may execute multiple sequential PRs. |
50 | 45 | +- Each PR must still have one clear purpose. |
51 | | -+- Each PR must create its own branch. |
52 | | -+- Each PR must be committed, pushed, and opened as a draft PR. |
| 46 | ++- Each PR must create or use its own approved branch. |
| 47 | ++- Each PR may be committed and pushed during active work. |
| 48 | ++- Each PR may be opened as a draft PR during active work. |
53 | 49 | +- Do not commit directly to main. |
54 | | -+- Do not merge without explicit owner approval. |
| 50 | ++- Do not merge to main during active work unless the owner explicitly says: "Merge this PR now." |
55 | 51 | +- If later PRs depend on earlier unmerged PRs, Codex must either: |
56 | 52 | + - stack the dependent PRs, or |
57 | 53 | + - stop and request owner approval for the dependency model. |
58 | 54 | +- Codex should reduce chit-chat by planning the full sequence before starting. |
59 | 55 | +- Codex must still hard-stop for conflicts, dirty worktree, scope mismatch, missing assignment, or protected instruction deletion. |
| 56 | ++ |
| 57 | ++Conflict note: |
| 58 | ++- Older wording that says each PR must create its own branch remains preserved. |
| 59 | ++- This all-team clarification allows an approved existing team, OWNER, or scoped PR branch when the owner assigns that dependency model. |
| 60 | ++- If a branch model is unclear, owner approval is required before continuing. |
| 61 | ++ |
| 62 | ++## Day Work / EOD Merge Rule |
| 63 | ++ |
| 64 | ++During active work: |
| 65 | ++- Work happens on assigned team branches, OWNER branches, or scoped PR branches. |
| 66 | ++- Commits are allowed only on assigned non-main branches. |
| 67 | ++- Pushes are allowed and expected. |
| 68 | ++- Draft PRs are allowed and expected. |
| 69 | ++- Direct commits to main are prohibited. |
| 70 | ++- Merges to main are prohibited unless explicitly approved by the owner. |
| 71 | ++ |
| 72 | ++At end of day: |
| 73 | ++- Owner reviews ready PRs. |
| 74 | ++- Owner explicitly approves which PRs merge. |
| 75 | ++- Only owner-approved PRs may merge to main. |
| 76 | ++- After merge, return to main and pull latest main. |
| 77 | ++- Do not treat sequential PR completion as merge approval. |
| 78 | ++ |
| 79 | ++Commit/push during the day is allowed only on assigned team/OWNER/PR branches. |
| 80 | ++ |
| 81 | ++Merge to main is EOD-only and owner-approved, unless the owner explicitly says: |
| 82 | ++"Merge this PR now." |
0 commit comments