You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs_build/dev/PROJECT_INSTRUCTIONS.md
+58-4Lines changed: 58 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1999,7 +1999,7 @@ Required workflow:
1999
1999
10. Create Pull Request automatically.
2000
2000
11. Resolve merge conflicts if encountered.
2001
2001
12. Re-run validation after conflict resolution.
2002
-
13. Merge PR.
2002
+
13. Merge PR only after explicit owner/EOD approval.
2003
2003
14. Return to main.
2004
2004
15. Pull latest main.
2005
2005
16. Continue to next approved PR.
@@ -2008,8 +2008,8 @@ Rules:
2008
2008
- Do not ask the user if a PR should be created.
2009
2009
- Do not ask the user if a branch should be pushed.
2010
2010
- Treat PR creation as required.
2011
-
- Treat branch push as required.
2012
-
- Treat merge as required after validation passes.
2011
+
- Treat branch push as required for scoped PR branch publishing.
2012
+
- Treat merge as required only after validation passes and explicit owner/EOD approval is provided.
2013
2013
- If GitHub prompts `Would you like to create a Pull Request?`, answer YES automatically.
2014
2014
- If merge conflicts occur:
2015
2015
- preserve latest main
@@ -2031,9 +2031,63 @@ Stable promotion and merge approval are owner-controlled.
2031
2031
2032
2032
Rules:
2033
2033
- Codex may prepare scoped changes, reports, validation evidence, ZIP artifacts, branches, and PRs.
2034
-
- Codex must not merge a PR or mark a workstream stable without explicit approval from the assigned Team Alphaor Team Beta owner.
2034
+
- Codex must not merge a PR or mark a workstream stable without explicit approval from the assigned Team Alpha, Team Beta, or Team Gamma owner.
2035
2035
- Master Control may recommend sequencing or assignment, but affected workstream owners control stable and merge approval.
2036
2036
- This targeted section supersedes older automatic-merge wording when approval ownership is in question.
2037
+
- EOD merge and EOD push actions are owner-controlled and require explicit approval.
2038
+
2039
+
## SEQUENTIAL CODEX QUEUE MODE
2040
+
2041
+
Team Gamma may use Sequential Codex Queue Mode for governance, diagnostics, admin, recovery, and instruction-hardening work.
2042
+
2043
+
Sequential Codex Queue Mode means Codex receives one queue command containing multiple ordered PR scopes.
2044
+
2045
+
Each queued PR must still have:
2046
+
- exact PR name
2047
+
- TEAM token
2048
+
- branch name
2049
+
- exact scope
2050
+
- validation scope
2051
+
- required reports
2052
+
- manual validation notes
2053
+
- ZIP requirement
2054
+
2055
+
Rules:
2056
+
- A queue command is not itself a PR unless explicitly named as one.
2057
+
- Missing exact scope for any queued PR is a hard stop for that PR only.
2058
+
- Codex may continue to the next queued PR only if the next PR has exact scope and does not depend on the stopped PR.
2059
+
- Codex must not create empty ZIPs or package partial PRs.
2060
+
- EOD merge/push is owner-controlled and requires explicit approval.
2061
+
- This section supersedes older wording that implies every PR must be independently prompted when Master Control provides a fully scoped sequential queue.
- Exact scope: audit active repository documentation and runtime references for SQLite deprecation status; document existing SQLite references as legacy technical debt only; do not add SQLite services, DDL, seed data, or runtime persistence.
- Validation scope: docs/static validation only, including `git diff --check` and targeted SQLite reference review; do not run Playwright; do not run samples.
- Exact scope: document the Admin system-health foundation contract for diagnostics ownership, visible failure reporting, and Postgres-first health checks; do not implement admin UI, runtime APIs, auth behavior, or database migrations.
- Validation scope: docs/static validation only, including `git diff --check` and targeted ownership wording review; do not run Playwright; do not run samples.
- Validation scope: docs/static validation only, including `git diff --check` and targeted Postgres/R2 diagnostics wording review; do not run Playwright; do not run samples.
Copy file name to clipboardExpand all lines: docs_build/dev/PROJECT_MULTI_PC.txt
+28Lines changed: 28 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -524,6 +524,34 @@ Governance, recovery, diagnostics, and instruction-hardening PRs:
524
524
- Must document TEAM ownership compliance in the PR report.
525
525
- Recovery reports must include TEAM ownership.
526
526
527
+
Team Gamma Sequential Codex Queue Mode:
528
+
- Team Gamma may use Sequential Codex Queue Mode for governance, diagnostics, admin, recovery, and instruction-hardening work.
529
+
- Sequential Codex Queue Mode means Codex receives one queue command containing multiple ordered PR scopes.
530
+
- Each queued PR must still have exact PR name, TEAM token, branch name, exact scope, validation scope, required reports, manual validation notes, and ZIP requirement.
531
+
- A queue command is not itself a PR unless explicitly named as one.
532
+
- Missing exact scope for any queued PR is a hard stop for that PR only.
533
+
- Codex may continue to the next queued PR only if the next PR has exact scope and does not depend on the stopped PR.
534
+
- Codex must not create empty ZIPs or package partial PRs.
535
+
- EOD merge/push is owner-controlled and requires explicit approval.
536
+
- This section supersedes older wording that implies every PR must be independently prompted when Master Control provides a fully scoped sequential queue.
- Exact scope: audit active repository documentation and runtime references for SQLite deprecation status; document existing SQLite references as legacy technical debt only; do not add SQLite services, DDL, seed data, or runtime persistence.
542
+
- Validation scope: docs/static validation only; do not run Playwright; do not run samples.
- Exact scope: document the Admin system-health foundation contract for diagnostics ownership, visible failure reporting, and Postgres-first health checks; do not implement admin UI, runtime APIs, auth behavior, or database migrations.
547
+
- Validation scope: docs/static validation only; do not run Playwright; do not run samples.
-`rg -n "Merge PR only after explicit owner/EOD approval|Treat merge as required only after validation passes and explicit owner/EOD approval is provided|EOD merge/push is owner-controlled and requires explicit approval|Codex must not merge a PR or mark a workstream stable without explicit approval" docs_build/dev/PROJECT_INSTRUCTIONS.md docs_build/dev/PROJECT_MULTI_PC.txt` - PASS.
56
+
57
+
Skipped lanes:
58
+
- Playwright: SKIP. Docs/workflow-only PR with no UI, tool runtime, toolState, or workspace behavior changes.
59
+
- Samples: SKIP. Docs/workflow-only PR with no sample loader, sample JSON, or sample runtime changes.
60
+
- Runtime, integration, and engine: SKIP. No runtime, handoff, shared parser, or engine behavior changed.
61
+
62
+
## Git Workflow
63
+
64
+
- Current branch: `pr/26171-GAMMA-004-sequential-gamma-queue-governance`.
65
+
- Created branch: `pr/26171-GAMMA-004-sequential-gamma-queue-governance`.
66
+
- Push result: pending final publish.
67
+
- PR URL: pending final publish.
68
+
- Merge result: not merged; EOD approval required.
0 commit comments