OWNER 010 document Codex bootstrap architecture

Author: ToolboxAid

dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.md

@@ -1,6 +1,8 @@
 # Project Instructions Operating System
 
-Read `README.txt` first.
+Bootstrap entry point: request this `PROJECT_INSTRUCTIONS.md` file directly.
+
+`README.txt` is supporting context loaded through this index; wrappers must not require users to specify it separately.
 
 This file is the root index for the append-first Project Instructions operating system under `dev/build/ProjectInstructions/`.
 
@@ -10,10 +12,24 @@ This file is the root index for the append-first Project Instructions operating
 
 Historical Project Instructions material outside this folder is deprecated reference material only and must not be used as an active source of governance.
 
+## Required Bootstrap Entry
+
+Only this file, `dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.md`, is requested directly by the Codex Start-of-Day bootstrap.
+
+All other active documents are loaded indirectly through references from this file.
+
+Required indirect sources:
+- Project state: `dev/build/ProjectInstructions/PROJECT_STATE.md`
+- Repository folder placement SSoT: `dev/build/ProjectInstructions/addendums/canonical_repository_structure.md`
+- Codex bootstrap architecture: `dev/build/ProjectInstructions/addendums/codex_start_of_day_bootstrap.md`
+- Team instructions and backlog: `dev/build/ProjectInstructions/team_assignments/` and `dev/build/ProjectInstructions/backlog/BACKLOG_MASTER.md`
+
 ## Purpose
 
 The Project Instructions operating system provides additive governance for:
 
+- Codex start-of-day bootstrap loading
+- project state ownership
 - backlog ownership
 - team assignments
 - multi-team branch and scope rules
@@ -42,6 +58,12 @@ Existing Project Instructions outside `dev/build/ProjectInstructions/` remain pr
 - Retained reference material belongs under the repository root `dev/archive/` tree, not under `dev/build/dev/`.
 - History snapshots belong under `dev/archive/legacy-docs-build/ProjectInstructions/history/`.
 
+## Single Source Of Truth Files
+
+- `PROJECT_INSTRUCTIONS.md` owns the active Project Instructions entry point, index, and referenced load graph.
+- `PROJECT_STATE.md` owns current repository/team state metadata used by bootstrap summaries.
+- `addendums/canonical_repository_structure.md` owns repository folder placement and file-placement rules.
+
 ## Recognized Project Reference Files
 
 `dev/build/ProjectInstructions/addendums/project_reference_files.md` defines additional valid project instruction/reference files that must be included in future Project Instructions reviews when present in `ProjectInstructions.zip`, the active project instruction directory, or the root archive reference tree.
@@ -64,6 +86,7 @@ Existing Project Instructions outside `dev/build/ProjectInstructions/` remain pr
 
 When active guidance overlaps, use these canonical owner documents:
 
+- Codex Start-of-Day bootstrap architecture and loading rules: `dev/build/ProjectInstructions/addendums/codex_start_of_day_bootstrap.md`
 - Workflow and Product Owner testable completion: `dev/build/ProjectInstructions/addendums/pr_workflow.md`
 - START / WORK / END lifecycle, branch gates, mandatory hard stops, and EOD main lock: `dev/build/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`
 - Repository folder placement, directory ownership, final root standard, final `src/` layer standard, final `dev/` workspace standard, and restructure boundaries: `dev/build/ProjectInstructions/addendums/canonical_repository_structure.md`
@@ -93,6 +116,10 @@ Other active addendums may summarize these rules, but they must point back to th
 
 `dev/build/ProjectInstructions/addendums/no_mock_repository_runtime_source.md` defines the Browser → API → Database product-data rule and mock repository technical debt boundary.
 
+## Codex Bootstrap Governance
+
+`dev/build/ProjectInstructions/addendums/codex_start_of_day_bootstrap.md` defines Bootstrap Phrases, Bootstrap Responsibilities, Wrapper Responsibilities, Standard Bootstrap Report, loading rules, SSoT ownership, and the future wrapper direction for the phrase `Use Latest Project Instructions`.
+
 ## Standards
 
 Active contract, model, and platform standards live under:

dev/build/ProjectInstructions/PROJECT_STATE.md

@@ -0,0 +1,32 @@
+# Project State
+
+Status: Active
+
+Owner: OWNER
+
+Version: 2026-06-27.PR_26179_OWNER_010
+
+## Purpose
+
+`PROJECT_STATE.md` is the single source of truth for current repository and team state metadata used by Codex Start-of-Day bootstrap summaries.
+
+## Ownership
+
+- `PROJECT_INSTRUCTIONS.md` owns the Project Instructions entry point and referenced load graph.
+- `PROJECT_STATE.md` owns current project state metadata.
+- `addendums/canonical_repository_structure.md` owns repository folder placement and file-placement rules.
+
+## Current State Fields
+
+Wrappers and Codex bootstrap summaries may report:
+
+- Project State Version
+- Repository Version
+- Team
+- Branch
+- Worktree
+- Backlog Loaded
+- Additional Documents Loaded
+- Next Recommended PR
+
+This file documents the state contract only. It does not implement wrapper behavior.

dev/build/ProjectInstructions/README.txt

@@ -1,4 +1,6 @@
-Read this file first.
+Supporting context for `PROJECT_INSTRUCTIONS.md`.
+
+Codex Start-of-Day wrappers request `PROJECT_INSTRUCTIONS.md` directly. This README is loaded indirectly through that entry point.
 
 Folder purpose:
 This folder is the only active Project Instructions source for Game Foundry Studio. It organizes active governance, backlog, team assignment, standards, deprecation, and history material under `dev/build/ProjectInstructions/`.
@@ -32,7 +34,7 @@ Do not rewrite history snapshots after creation unless the owner explicitly appr
 
 READ THIS FIRST
 
-1. Read `dev/build/ProjectInstructions/README.txt` before making changes.
+1. Use `dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.md` as the only direct bootstrap entry point.
 2. Treat `dev/build/ProjectInstructions/` as the only active Project Instructions source.
 3. Historical Project Instructions files outside this folder are deprecated references only and must not be used as active sources.
 4. Team ownership must be respected.
@@ -49,6 +51,7 @@ Addendum index:
 - Documentation Ownership: dev/build/ProjectInstructions/addendums/documentation_ownership.md
 - Canonical Repository Structure: dev/build/ProjectInstructions/addendums/canonical_repository_structure.md
 - Repository Directory Standard (superseded pointer): dev/build/ProjectInstructions/addendums/repository_directory_standard.md
+- Codex Start-of-Day Bootstrap: dev/build/ProjectInstructions/addendums/codex_start_of_day_bootstrap.md
 - Team Backlog, SOD, And EOD Standard: dev/build/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md
 - Single Source and EOD Main Lock: dev/build/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md
 - Test Structure Standardization: dev/build/ProjectInstructions/addendums/test_structure_standardization.md

dev/build/ProjectInstructions/addendums/codex_project_instructions_startup.md

@@ -6,12 +6,14 @@ Ensure Codex uses the current approved governance before making repository chang
 
 ## Startup Requirement
 
-Before performing work, Codex must review and use:
+Before performing work, Codex must request the latest Project Instructions through the single direct entry point:
 
 ```text
-dev/build/ProjectInstructions/
+dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.md
 ```
 
+All other Project Instructions documents are loaded indirectly through references from `PROJECT_INSTRUCTIONS.md`.
+
 Codex must use this as the only active source of truth for:
 - Governance rules
 - Repository standards
@@ -21,6 +23,12 @@ Codex must use this as the only active source of truth for:
 - Execution modes
 - Artifact requirements
 
+The Codex Start-of-Day bootstrap architecture is defined in:
+
+```text
+dev/build/ProjectInstructions/addendums/codex_start_of_day_bootstrap.md
+```
+
 ## Branch Lifecycle Start Gate
 
 Codex must follow the canonical lifecycle in:

dev/build/ProjectInstructions/addendums/codex_start_of_day_bootstrap.md

@@ -0,0 +1,129 @@
+# Codex Start-of-Day Bootstrap
+
+Status: Approved
+
+Owner: OWNER
+
+## Purpose
+
+Define the Codex Start-of-Day bootstrap architecture for loading the latest Project Instructions, project state, team context, and branch/worktree status before implementation begins.
+
+This document is documentation and wrapper/bootstrap design only. It does not implement wrapper behavior.
+
+## Bootstrap Phrase
+
+A Bootstrap Phrase is a short user-facing phrase that asks the wrapper to resolve the latest Project Instructions and team state before launching Codex.
+
+Examples:
+
+- Owner Start of Day
+- Team Alpha Start of Day
+- Team Bravo Start of Day
+- Team Charlie Start of Day
+- Team Gamma Start of Day
+
+Team name note:
+- `Team Alpha Start of Day` is accepted as a user phrase alias for the canonical Team Alfa lane.
+- Historical Team Gamma phrases may be understood for archived/historical context, but active assignment routing follows the current team registry.
+
+## Bootstrap Responsibilities
+
+The bootstrap loads:
+
+- Latest Project Instructions SSoT
+- `PROJECT_STATE.md`
+- Canonical Repository Structure
+- Team instructions
+- Team backlog
+- Current team status
+- Current branch
+- Worktree status
+
+The bootstrap must not create branches, commit files, move files, or run implementation work by itself.
+
+## Wrapper Responsibilities
+
+The wrapper performs:
+
+- Branch verification
+- Worktree verification
+- Bootstrap loading
+- Version reporting
+- Start-of-day summary
+- Launch Codex with the resolved instruction set
+
+The wrapper must not modify runtime code, production pages, or existing wrapper scripts as part of this architecture definition.
+
+## Standard Bootstrap Report
+
+```text
+Bootstrap
+----------
+Project Instructions Version:
+Project State Version:
+Repository Version:
+Team:
+Branch:
+Worktree:
+Backlog Loaded:
+Additional Documents Loaded:
+Next Recommended PR:
+```
+
+## Loading Rules
+
+Only `PROJECT_INSTRUCTIONS.md` is requested directly.
+
+All other documents are loaded indirectly through references from `PROJECT_INSTRUCTIONS.md`.
+
+`PROJECT_INSTRUCTIONS.md` is the only required entry point for Codex Start-of-Day bootstrap loading.
+
+The bootstrap load graph begins at:
+
+```text
+dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.md
+```
+
+## Single Source Of Truth
+
+`PROJECT_INSTRUCTIONS.md` owns:
+
+- Active Project Instructions entry point
+- Project Instructions index
+- Referenced load graph
+- Canonical governance owner links
+
+`PROJECT_STATE.md` owns:
+
+- Current project state metadata
+- Project State Version
+- Repository/team summary fields used by bootstrap reporting
+
+`canonical_repository_structure.md` owns:
+
+- Repository folder placement
+- Valid top-level folders
+- Valid dev workspace folders
+- File-placement rules
+- Invalid legacy path rules
+
+## Future Direction
+
+Future wrappers should understand:
+
+```text
+Use Latest Project Instructions
+```
+
+without requiring users to specify file paths.
+
+When this phrase is used, the wrapper should resolve `PROJECT_INSTRUCTIONS.md`, follow its references, load current project state and team context, report versions, verify branch/worktree status, and launch Codex with the resolved instruction set.
+
+## Validation
+
+Bootstrap architecture changes are documentation-governance changes unless explicitly scoped otherwise.
+
+Required validation for this design-only layer:
+
+- Documentation review
+- `git diff --check`