ToolboxAid · ToolboxAid · Jun 21, 2026
diff --git a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md
@@ -37,3 +37,54 @@ Status: Available
 Active assignment: none.
 
 Active branch: none.
+
+## Team Name Registry
+
+- Team Alfa
+- Team Bravo
+- Team Charlie
+- Team Delta
+- Team Echo
+- Team Foxtrot
+- Team Golf
+- Team Hotel
+- Team India
+- Team Juliett
+- Team Kilo
+- Team Lima
+- Team Mike
+- Team November
+- Team Oscar
+- Team Papa
+- Team Quebec
+- Team Romeo
+- Team Sierra
+- Team Tango
+- Team Uniform
+- Team Victor
+- Team Whiskey
+- Team X-ray
+- Team Yankee
+- Team Zulu
+- Team OWNER
+
+## Preferred Codex Execution Method
+
+Preferred execution model:
+Single Codex session with multiple sequential PRs.
+
+Purpose:
+Reduce back-and-forth between owner and Codex while keeping PRs reviewable and scoped.
+
+Rules:
+- One Codex session may execute multiple sequential PRs.
+- Each PR must still have one clear purpose.
+- Each PR must create its own branch.
+- Each PR must be committed, pushed, and opened as a draft PR.
+- Do not commit directly to main.
+- Do not merge without explicit owner approval.
+- If later PRs depend on earlier unmerged PRs, Codex must either:
+  - stack the dependent PRs, or
+  - stop and request owner approval for the dependency model.
+- Codex should reduce chit-chat by planning the full sequence before starting.
+- Codex must still hard-stop for conflicts, dirty worktree, scope mismatch, missing assignment, or protected instruction deletion.
diff --git a/...to-team-registry-and-codex-execution-method-instruction-compliance-checklist.md b/...to-team-registry-and-codex-execution-method-instruction-compliance-checklist.md
@@ -0,0 +1,14 @@
+# PR_26172_OWNER_015 Instruction Compliance Checklist
+
+- [x] Read `docs_build/dev/PROJECT_INSTRUCTIONS.md`.
+- [x] Read `docs_build/dev/PROJECT_MULTI_PC.txt`.
+- [x] OWNER override documented by user.
+- [x] Started stacked PR015 from PR014 branch.
+- [x] Preserved existing ProjectInstructions content.
+- [x] Added or clarified documentation only.
+- [x] Did not commit directly to `main`.
+- [x] Did not merge any PR.
+- [x] Did not delete protected instructions.
+- [x] Ran docs/static validation.
+- [x] Documented skipped validation lanes.
+- [x] Created repo-structured delta ZIP.
diff --git a/...ER_015-nato-team-registry-and-codex-execution-method-manual-validation-notes.md b/...ER_015-nato-team-registry-and-codex-execution-method-manual-validation-notes.md
@@ -0,0 +1,11 @@
+# PR_26172_OWNER_015 Manual Validation Notes
+
+- Verified `TEAM_ASSIGNMENTS.md` retains existing team assignment content.
+- Verified Team Name Registry includes Team Alfa through Team Zulu plus Team OWNER.
+- Verified official NATO spellings are used: Alfa, Juliett, X-ray.
+- Verified Preferred Codex Execution Method describes a single Codex session with multiple sequential PRs.
+- Verified each PR still requires one clear purpose, its own branch, commit, push, and draft PR.
+- Verified direct commits to `main` remain prohibited.
+- Verified merges still require explicit owner approval.
+- Verified dependent unmerged PRs must be stacked or require owner approval for the dependency model.
+- Verified hard stops remain for conflicts, dirty worktree, scope mismatch, missing assignment, or protected instruction deletion.
diff --git a/...dev/reports/PR_26172_OWNER_015-nato-team-registry-and-codex-execution-method.md b/...dev/reports/PR_26172_OWNER_015-nato-team-registry-and-codex-execution-method.md
@@ -0,0 +1,31 @@
+# PR_26172_OWNER_015-nato-team-registry-and-codex-execution-method
+
+## Scope
+
+Update ProjectInstructions team naming and Codex execution governance in:
+
+- `docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md`
+
+## Changes
+
+- Added the Team Name Registry using official NATO spelling for Alfa, Juliett, and X-ray.
+- Added Team OWNER to the registry.
+- Added the Preferred Codex Execution Method section.
+- Documented the preferred single-session sequential PR model.
+- Preserved one-purpose-per-PR, own-branch, draft-PR, no-direct-main, no-merge-without-owner-approval, stacking/dependency, and hard-stop rules.
+
+## Validation
+
+- `git diff --check`
+- `git diff --cached --check`
+- Markdown/text review
+- Targeted text verification for official NATO spellings and OWNER governance wording
+
+## Skipped Lanes
+
+- Playwright skipped: documentation-only scope.
+- Samples skipped: documentation-only scope.
+
+## Package
+
+- `tmp/PR_26172_OWNER_015-nato-team-registry-and-codex-execution-method_delta.zip`
diff --git a/docs_build/dev/reports/codex_changed_files.txt b/docs_build/dev/reports/codex_changed_files.txt
@@ -1,6 +1,6 @@
-docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md
-docs_build/dev/reports/PR_26172_OWNER_014-owner-team-start-command-instruction-compliance-checklist.md
-docs_build/dev/reports/PR_26172_OWNER_014-owner-team-start-command-manual-validation-notes.md
-docs_build/dev/reports/PR_26172_OWNER_014-owner-team-start-command.md
+docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md
+docs_build/dev/reports/PR_26172_OWNER_015-nato-team-registry-and-codex-execution-method-instruction-compliance-checklist.md
+docs_build/dev/reports/PR_26172_OWNER_015-nato-team-registry-and-codex-execution-method-manual-validation-notes.md
+docs_build/dev/reports/PR_26172_OWNER_015-nato-team-registry-and-codex-execution-method.md
 docs_build/dev/reports/codex_changed_files.txt
 docs_build/dev/reports/codex_review.diff
diff --git a/docs_build/dev/reports/codex_review.diff b/docs_build/dev/reports/codex_review.diff
@@ -1 +1,59 @@
+diff --git a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md
+index 3408c96f2..ce04c904b 100644
+--- a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md
++++ b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md
+@@ -37,3 +37,54 @@ Status: Available
+ Active assignment: none.
 
+ Active branch: none.
++
++## Team Name Registry
++
++- Team Alfa
++- Team Bravo
++- Team Charlie
++- Team Delta
++- Team Echo
++- Team Foxtrot
++- Team Golf
++- Team Hotel
++- Team India
++- Team Juliett
++- Team Kilo
++- Team Lima
++- Team Mike
++- Team November
++- Team Oscar
++- Team Papa
++- Team Quebec
++- Team Romeo
++- Team Sierra
++- Team Tango
++- Team Uniform
++- Team Victor
++- Team Whiskey
++- Team X-ray
++- Team Yankee
++- Team Zulu
++- Team OWNER
++
++## Preferred Codex Execution Method
++
++Preferred execution model:
++Single Codex session with multiple sequential PRs.
++
++Purpose:
++Reduce back-and-forth between owner and Codex while keeping PRs reviewable and scoped.
++
++Rules:
++- One Codex session may execute multiple sequential PRs.
++- Each PR must still have one clear purpose.
++- Each PR must create its own branch.
++- Each PR must be committed, pushed, and opened as a draft PR.
++- Do not commit directly to main.
++- Do not merge without explicit owner approval.
++- If later PRs depend on earlier unmerged PRs, Codex must either:
++  - stack the dependent PRs, or
++  - stop and request owner approval for the dependency model.
++- Codex should reduce chit-chat by planning the full sequence before starting.
++- Codex must still hard-stop for conflicts, dirty worktree, scope mismatch, missing assignment, or protected instruction deletion.