PR_26179_OWNER_010-canonical-project-folder-instructions#245
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5411ad71c9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - dev/scripts/ | ||
| - dev/templates/ | ||
| - dev/tests/ | ||
| - dev/tools/ | ||
| - dev/workspace/ |
There was a problem hiding this comment.
Keep dev/deploy as a valid dev workspace folder
This canonical list omits dev/deploy/, but the repository still contains active local deployment config at dev/deploy/docker-compose.override.yml and the previous directory standard explicitly assigned dev/deploy/ to development-only deployment assets. Because PROJECT_INSTRUCTIONS.md now hard-stops when a requested path does not fit this SSoT, any future change to that existing deployment config would be blocked as non-canonical even though no file move was included in this PR.
Useful? React with 👍 / 👎.
| - Continue | ||
| - Follow Project Instructions | ||
| - Next PR |
There was a problem hiding this comment.
Define the routed execution aliases
These aliases are still routed through CODEX_WORKFLOW_COMMANDS.md, but that new SSoT only defines Start of Day plus PLAN_PR/BUILD_PR/APPLY_PR, while the old execution-mode tables were replaced with pointers. In requests that contain Continue, Follow Project Instructions, or Next PR, Codex now has no command behavior to resolve and will fall into the invalid-command hard stop instead of the execution-mode behavior this section promises.
Useful? React with 👍 / 👎.
|
|
||
| Start of Day may recommend the next execution phase, but it must not execute that phase. | ||
|
|
||
| Start of Day must satisfy the Codex Completion Contract in `dev/build/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md`. Because Start of Day is read-only discovery, its ZIP outcome is review-only unless another outcome is explicitly documented. |
There was a problem hiding this comment.
Exempt read-only Start of Day from report writes
Start of Day is forbidden from modifying repository files, but this line also requires the full Completion Contract; that contract requires reports under dev/reports/, which are tracked repo files. A normal Start of Day on clean main therefore either dirties the worktree just to produce the required report or violates the new contract, so the read-only phase needs an explicit no-write/review-only exception.
Useful? React with 👍 / 👎.
PR_26179_OWNER_010-canonical-project-folder-instructions
Updated: 2026-06-28T01:49:46Z
Team: OWNER
Branch: PR_26179_OWNER_010-canonical-project-folder-instructions
Scope: Documentation/governance only. No files moved. No runtime behavior, wrapper script, or production page changes.
SSoT Decision
dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.mdis the only direct Codex bootstrap entry point.Bootstrap loads supporting Project Instructions indirectly through references from
PROJECT_INSTRUCTIONS.md.Single source ownership:
PROJECT_INSTRUCTIONS.md: active entry point, index, and referenced load graph.PROJECT_STATE.md: current project/repository/team state metadata for bootstrap summaries.addendums/canonical_repository_structure.md: repository folder placement and file-placement rules.Summary
PROJECT_STATE.mdas the project state SSoT document.addendums/codex_start_of_day_bootstrap.mdto define bootstrap phrases, responsibilities, wrapper responsibilities, standard bootstrap report, loading rules, SSoT ownership, and future wrapper direction.PROJECT_INSTRUCTIONS.md,README.txt, andcodex_project_instructions_startup.mdso wrappers request onlyPROJECT_INSTRUCTIONS.mddirectly.Changed Files
Documentation Review Evidence
Validation
Blockers
None.