@@ -11,7 +11,7 @@ Naming governance
1111Workflow governance
1212Environment strategy
1313PR sequencing
14- Merge approval
14+ Stable and merge approval
1515
1616It should never build code and never own implementation details.
1717
@@ -22,12 +22,12 @@ Requirements
2222Acceptance Criteria
2323Dependencies
2424Priority
25- Owner (PC/Laptop )
25+ Owner (Team Alpha / Team Beta )
2626Recommended Workstream Split
2727
2828Instead of arbitrary splits, split by Creator journey.
2929
30- PC — Creator Journey
30+ Team Alpha — Creator Journey
3131
3232Owns:
3333
@@ -57,7 +57,7 @@ Reason:
5757
5858These tools are heavily connected.
5959
60- Laptop — Content Creation
60+ Team Beta — Content Creation
6161
6262Owns:
6363
@@ -85,7 +85,7 @@ These tools share asset pipelines and publishing workflows.
8585
8686Messages Tool Placement
8787
88- I would move Messages to Laptop ownership.
88+ I would move Messages to Team Beta ownership.
8989
9090Reason:
9191
@@ -191,7 +191,7 @@ Immediate Queue
191191
192192If we start using Master Control today, my queue would be:
193193
194- PC
194+ Team Alpha
195195PR_26171_001-game-journey-completion-model
196196
197197Scope:
@@ -205,7 +205,7 @@ Sounds [17]
205205
206206This solves the "xxx%" problem.
207207
208- Laptop
208+ Team Beta
209209PR_26171_002-messages-tool-foundation
210210
211211Scope:
@@ -282,7 +282,7 @@ Not developer.
282282
283283---
284284
285- ## PC Chat
285+ ## Team Alpha Chat
286286
287287Give it ownership of a workstream.
288288
@@ -309,7 +309,7 @@ it keeps building in that area.
309309
310310---
311311
312- ## Laptop Chat
312+ ## Team Beta Chat
313313
314314Give it a different workstream.
315315
@@ -371,13 +371,13 @@ So I'd keep IST mostly as infrastructure work and focus development on tool comp
371371Master Control should assign ownership:
372372
373373```text
374- PC
374+ Team Alpha
375375 Game Journey
376376 Game Hub
377377 Publish
378378 Share
379379
380- Laptop
380+ Team Beta
381381 Audio
382382 MIDI
383383 Events
@@ -405,7 +405,7 @@ feature/game-hub
405405feature/progress-tracking
406406```
407407
408- Never have both PCs working in the same tool at the same time.
408+ Never have both teams working in the same tool at the same time.
409409
410410---
411411
@@ -418,19 +418,19 @@ For example, in Master Control you can ask:
418418```text
419419Given everything we know about GFS:
420420
421- What should PC build next?
422- What should Laptop build next?
421+ What should Team Alpha build next?
422+ What should Team Beta build next?
423423
424424Generate the next PR for each.
425425```
426426
427427Then Master Control outputs:
428428
429429```text
430- PC :
430+ Team Alpha :
431431PR_26171_002-game-hub-progress
432432
433- Laptop :
433+ Team Beta :
434434PR_26171_003-messages-tool-mvp
435435```
436436
@@ -457,17 +457,17 @@ Codex must read this file before every PR execution.
457457
458458Machine parity:
459459
460- PC / Environment 1:
460+ Team Alpha / Environment 1:
461461- Uses even-numbered PR sequence values.
462462- Example: `PR_26171_064-*`.
463463
464- Laptop / Environment 2:
464+ Team Beta / Environment 2:
465465- Uses odd-numbered PR sequence values.
466466- Example: `PR_26171_063-*`.
467467
468468Owner map:
469469
470- PC / Environment 1 owns Creator Journey work:
470+ Team Alpha / Environment 1 owns Creator Journey work:
471471- Game Journey
472472- Game Hub
473473- Idea
@@ -483,7 +483,7 @@ PC / Environment 1 owns Creator Journey work:
483483- Game Design
484484- Game Crew
485485
486- Laptop / Environment 2 owns Content Creation and asset/publishing work:
486+ Team Beta / Environment 2 owns Content Creation and asset/publishing work:
487487- Graphics
488488- Toolbox images
489489- Audio
@@ -501,8 +501,12 @@ Governance, recovery, diagnostics, and instruction-hardening PRs:
501501- Must not implement tool/runtime work from the opposite owner.
502502- Must document owner/parity compliance in the PR report.
503503
504+ Stable and merge approval:
505+ - Stable promotion and merge approval are controlled by the assigned Team Alpha or Team Beta owner.
506+ - Master Control may recommend sequencing, but Codex must not merge or mark stable without explicit owner approval for the affected workstream.
507+
504508Hard stop rules:
505509- If the PR number parity does not match the current machine, stop before changes.
506510- If the PR scope belongs to the other machine owner, stop before changes.
507- - If the PR crosses PC and Laptop ownership, stop and require Master Control to split or assign the work.
511+ - If the PR crosses Team Alpha and Team Beta ownership, stop and require Master Control to split or assign the work.
508512- If the requested implementation path conflicts with the active owner path, stop before changes.
0 commit comments