|
1 | 1 | diff --git a/docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md b/docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md |
2 | | -index 40db33c44..9636e2d41 100644 |
| 2 | +index 9636e2d41..96c4e5622 100644 |
3 | 3 | --- a/docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md |
4 | 4 | +++ b/docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md |
5 | | -@@ -33,6 +33,15 @@ Existing Project Instructions remain preserved in their current locations. This |
6 | | - |
7 | | - No PR in this operating system is merged without explicit owner approval. |
8 | | - |
9 | | -+## Day Work / EOD Merge Rule |
10 | | -+ |
11 | | -+Commit/push during the day is allowed only on assigned team/OWNER/PR branches. |
12 | | -+ |
13 | | -+Merge to main is EOD-only and owner-approved, unless the owner explicitly says: |
14 | | -+"Merge this PR now." |
| 5 | +@@ -53,3 +53,11 @@ OWNER follows the same safety rules: |
| 6 | + - One active OWNER assignment at a time. |
| 7 | + - OWNER may override team locks, but may not silently delete, rewrite, or remove protected instructions. |
| 8 | + - OWNER override must be explicitly documented. |
15 | 9 | + |
16 | | -+Do not treat sequential PR completion as merge approval. |
17 | | -+ |
18 | | - ## OWNER Governance |
19 | | - |
20 | | - OWNER override wording: |
21 | | -diff --git a/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md b/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md |
22 | | -index 35279e8f1..ff60e7bbb 100644 |
23 | | ---- a/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md |
24 | | -+++ b/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md |
25 | | -@@ -70,6 +70,8 @@ Work only that assignment. |
26 | | - |
27 | | - Ready-to-copy reminder: |
28 | | - |
29 | | -+Confirmed required rule: |
| 10 | ++### OWNER Branch Lock Governance |
30 | 11 | + |
31 | | - ```text |
32 | | - Commit/push during the day is allowed only on assigned team/OWNER/PR branches. |
33 | | - |
| 12 | ++- OWNER may override team locks. |
| 13 | ++- OWNER still has one active assignment at a time. |
| 14 | ++- OWNER still has one active branch at a time. |
| 15 | ++- OWNER may not silently delete, rewrite, or remove protected instructions. |
| 16 | ++- OWNER override must be documented. |
34 | 17 | diff --git a/docs_build/dev/ProjectInstructions/addendums/multi_team.md b/docs_build/dev/ProjectInstructions/addendums/multi_team.md |
35 | | -index 373a51ed0..f0a369ee9 100644 |
| 18 | +index f0a369ee9..670543d1a 100644 |
36 | 19 | --- a/docs_build/dev/ProjectInstructions/addendums/multi_team.md |
37 | 20 | +++ b/docs_build/dev/ProjectInstructions/addendums/multi_team.md |
38 | | -@@ -28,6 +28,8 @@ Rules: |
| 21 | +@@ -55,3 +55,11 @@ Merge to main is EOD-only and owner-approved, unless the owner explicitly says: |
| 22 | + Existing ProjectInstructions wording that appears to require immediate or automatic merge remains preserved for traceability. |
39 | 23 |
|
40 | | - ## Day Work / EOD Merge Rule |
41 | | - |
42 | | -+Confirmed required rule: |
| 24 | + This addendum clarifies that merge to `main` remains owner-controlled. If a workflow rule appears to conflict with this addendum, stop and request explicit owner approval before merging. |
| 25 | ++ |
| 26 | ++## OWNER Branch Lock Governance |
43 | 27 | + |
44 | | - During active work: |
45 | | - - Work happens on assigned team branches, OWNER branches, or scoped PR branches. |
46 | | - - Commits are allowed only on assigned non-main branches. |
| 28 | ++- OWNER may override team locks. |
| 29 | ++- OWNER still has one active assignment at a time. |
| 30 | ++- OWNER still has one active branch at a time. |
| 31 | ++- OWNER may not silently delete, rewrite, or remove protected instructions. |
| 32 | ++- OWNER override must be documented. |
| 33 | +diff --git a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md |
| 34 | +index b7c5df692..04ff72616 100644 |
| 35 | +--- a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md |
| 36 | ++++ b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md |
| 37 | +@@ -38,6 +38,14 @@ Active assignment: none. |
| 38 | + |
| 39 | + Active branch: none. |
| 40 | + |
| 41 | ++### OWNER Branch Lock Governance |
| 42 | ++ |
| 43 | ++- OWNER may override team locks. |
| 44 | ++- OWNER still has one active assignment at a time. |
| 45 | ++- OWNER still has one active branch at a time. |
| 46 | ++- OWNER may not silently delete, rewrite, or remove protected instructions. |
| 47 | ++- OWNER override must be documented. |
| 48 | ++ |
| 49 | + ## Team Name Registry |
| 50 | + |
| 51 | + - Team Alfa |
0 commit comments