Skip to content

PR_26172_OWNER_034-canonical-project-source-of-truth #249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ToolboxAid merged 1 commit into from
Jun 28, 2026
Merged

PR_26172_OWNER_034-canonical-project-source-of-truth #249

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 34 additions & 1 deletion dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,42 @@

Codex and future wrappers must request this file directly. All other Project Instructions documents are loaded indirectly through the references below.

## Canonical Source Rule

The repository is the canonical source of truth for project rules.

Codex, ChatGPT, wrappers, and team operators must use the current repository documentation under `dev/build/ProjectInstructions/` as authority for active rules. Prior chat history, remembered conversation context, generated reports, archived documents, local notes, or stale external instructions must not override repository documentation.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep referenced docs authoritative

This sentence limits active-rule authority to docs under dev/build/ProjectInstructions/, but the same file still requires loading referenced docs outside that tree, such as dev/build/database/ for DB, DDL, DML, seed, or API persistence work. For those tasks, a wrapper following the new top-level rule can ignore the referenced database documentation because it is outside the declared authority boundary; include all referenced active docs in the canonical source scope or move the references inside it.

Useful? React with 👍 / 👎.


If current chat instructions conflict with repository documentation, Codex must follow the active repository documentation or HARD STOP and request OWNER direction.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Do not demote current task instructions

When the Owner gives task-specific instructions in the current prompt that intentionally narrow a run, such as review-only work or not generating a PR, this rule tells Codex to follow repository docs or hard-stop instead of obeying the live instruction. The stated purpose is to avoid stale history, but including current chat instructions makes valid one-off directions impossible unless the repo docs already say the same thing; limit this override to prior or stale context.

Useful? React with 👍 / 👎.


## Canonical Team Naming

Canonical active teams:

- Owner
- Alfa
- Bravo
- Charlie
- Golf
Comment on lines +21 to +25

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep the canonical team set consistent

This list is now the authoritative active-team list, but the same required Project Instructions still mark Delta as canonical: PROJECT_STATE.md still includes Delta in active_teams, and standards/CODEX_WORKFLOW_COMMANDS.md still allows Start of Day Delta and says active names include Delta. Any Delta workflow now hits contradictory governance about whether Delta is active; either include Delta here or update the other active docs in this PR.

Useful? React with 👍 / 👎.


Official NATO spellings:

```text
Alfa, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliett, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, Xray, Yankee, Zulu.
```

Rules:

- Use official NATO spelling for all team names.
- Do not use `Alpha`, `Beta`, or `Gamma` for active teams.
- Deprecated or historical names must not be used for active team routing, new work ownership, or current governance.
- Historical PR names, branch names, and references may remain unchanged when they are already merged or clearly referenced as history.
- New branches, PRs, reports, and documentation must use canonical team names.
- Repository documentation overrides prior conversations.

## Current Version/Date

- Project Instructions Version: 2026-06-28.PR_26179_OWNER_010
- Project Instructions Version: 2026-06-28.PR_26172_OWNER_034

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep the instruction version aligned

Changing this metadata to PR_26172 makes PROJECT_INSTRUCTIONS.md disagree with the required PROJECT_STATE.md, which still records project_instructions_version and latest_owner_pr as PR_26179_OWNER_010. Start-of-Day reporting loads both files and reports both versions, so wrappers/operators now see a regressed and inconsistent instruction version; keep this line at the current project-state version or update PROJECT_STATE.md consistently.

Useful? React with 👍 / 👎.

- Date: 2026-06-28
- Owner: OWNER

Expand Down
27 changes: 27 additions & 0 deletions dev/reports/PR_26172_OWNER_034-canonical-project-source-of-truth.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# PR_26172_OWNER_034-canonical-project-source-of-truth

## Purpose

Make repository documentation the canonical source of truth for project rules so Codex and ChatGPT do not rely on stale conversation history.

## Summary

- Added a Canonical Source Rule near the top of `PROJECT_INSTRUCTIONS.md`.
- Documented that active repository documentation overrides prior chat history, generated reports, archive material, local notes, and stale external instructions.
- Added canonical active teams: Owner, Alfa, Bravo, Charlie, and Golf.
- Added official NATO spelling guidance.
- Documented that Alpha, Beta, and Gamma must not be used for active teams.
- Preserved historical PR/branch/reference names when clearly historical.

## Scope Boundary

- Documentation/governance only.
- Runtime code was not modified.
- Bootstrap files were not modified.
- No `PROJECT_MULTI_PC.txt` file was created or restored.

## Validation

- `git diff --check`: PASS
- `npm run validate:canonical-structure`: PASS
- Deprecated active-team-name scan in `dev/build/ProjectInstructions/`: PASS with only intentional prohibition/historical non-team phrase matches.
14 changes: 14 additions & 0 deletions ...s/PR_26172_OWNER_034-canonical-project-source-of-truth_requirement-checklist.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# PR_26172_OWNER_034 Requirement Checklist

| Requirement | Result | Evidence |
| --- | --- | --- |
| Update `PROJECT_INSTRUCTIONS.md`. | PASS | Updated `dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.md`. |
| Add clear Canonical Source Rule near the top. | PASS | Added `Canonical Source Rule` section after Purpose. |
| Add canonical NATO team naming. | PASS | Added canonical active teams and official NATO spelling list. |
| Deprecated/historical names must not be used for active teams. | PASS | Added explicit active-team prohibition for Alpha, Beta, and Gamma. |
| Prior chat history must not override repository documentation. | PASS | Added repository documentation override rule. |
| Historical PR names may remain unchanged. | PASS | Added historical PR/branch/reference exception. |
| New branches, PRs, reports, and documentation must use canonical names. | PASS | Added new-artifact naming rule. |
| Do not modify runtime code. | PASS | Only Project Instructions and generated reports changed. |
| Do not modify bootstrap files. | PASS | No `dev/bootstrap/` files changed. |
| Do not recreate or add `PROJECT_MULTI_PC.txt`. | PASS | File was not created. |
15 changes: 15 additions & 0 deletions ...ports/PR_26172_OWNER_034-canonical-project-source-of-truth_validation-report.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# PR_26172_OWNER_034 Validation Report

| Lane | Command | Result |
| --- | --- | --- |
| Diff whitespace | `git diff --check` | PASS |
| Canonical structure | `npm run validate:canonical-structure` | PASS, 0 blocking violations |
| Deprecated active-team names | `rg -n "\b(Alpha|Beta|Gamma)\b" dev\build\ProjectInstructions` | PASS with intentional matches only |

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use a rerunnable validation path

In the repo's normal bash environment, the recorded command treats the backslashes in dev\build\ProjectInstructions as escapes and rg receives devbuildProjectInstructions, which exits with “No such file or directory” rather than running the scan this report marks as PASS. Anyone rechecking this validation on Linux/macOS will get a failure; record the portable dev/build/ProjectInstructions path or explicitly identify a Windows-only shell.

Useful? React with 👍 / 👎.


## Deprecated Name Scan Notes

Intentional matches:
- `PROJECT_INSTRUCTIONS.md` contains the new rule: `Do not use Alpha, Beta, or Gamma for active teams.`
- Existing governance docs contain the non-team historical phrase `Alfa/Beta/User isolation framework`, already marked as a non-team phrase that should not be rewritten unless explicitly scoped.

No active team ownership/routing references to Alpha, Beta, or Gamma were found in governance docs.
7 changes: 1 addition & 6 deletions dev/reports/codex_changed_files.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1 @@
PR_26179_OWNER_012-gitignore-env-simplification
Updated: 2026-06-28T03:47:16Z
Branch: PR_26179_OWNER_012-gitignore-env-simplification

Changed files:
M .gitignore
dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.md

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge List the full branch delta in changed files

This required changed-file report now contains only PROJECT_INSTRUCTIONS.md, but the commit also adds the PR report/checklist/validation files and updates codex_review.diff plus this file. Consumers that use this artifact to verify the final branch delta will miss most of the committed changes and status evidence; regenerate the report from the actual git status/diff output or list every changed file.

Useful? React with 👍 / 👎.

60 changes: 46 additions & 14 deletions dev/reports/codex_review.diff
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,15 +1,47 @@
diff --git a/.gitignore b/.gitignore
index 3ac762a04..1207a12fc 100644
--- a/.gitignore
+++ b/.gitignore
@@ -48,8 +48,8 @@ docs/dev/reports/playwright_v8_coverage_report.txt
*.mp4
*.mkv
diff --git a/dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.md b/dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.md
index 5b1b8f9a6..c6f5c5744 100644
--- a/dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.md
+++ b/dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.md
@@ -6,9 +6,42 @@

Comment on lines +5 to 6

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Regenerate the review diff as a valid patch

The stored .diff is not a valid unified diff because blank context lines were written without the required leading space, starting immediately after this hunk header; git apply --check dev/reports/codex_review.diff reports corrupt patch at line 48. Since the completion contract requires a diff artifact when changes occur, this evidence cannot be mechanically verified or applied; regenerate it from git diff without stripping line prefixes.

Useful? React with 👍 / 👎.

-.env
-.env.*
+# Environment files
+.env*
!.env.example
!.env.sample
!.env.template
Codex and future wrappers must request this file directly. All other Project Instructions documents are loaded indirectly through the references below.

+## Canonical Source Rule
+
+The repository is the canonical source of truth for project rules.
+
+Codex, ChatGPT, wrappers, and team operators must use the current repository documentation under `dev/build/ProjectInstructions/` as authority for active rules. Prior chat history, remembered conversation context, generated reports, archived documents, local notes, or stale external instructions must not override repository documentation.
+
+If current chat instructions conflict with repository documentation, Codex must follow the active repository documentation or HARD STOP and request OWNER direction.
+
+## Canonical Team Naming
+
+Canonical active teams:
+
+- Owner
+- Alfa
+- Bravo
+- Charlie
+- Golf
+
+Official NATO spellings:
+
+```text
+Alfa, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliett, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, Xray, Yankee, Zulu.
+```
+
+Rules:
+
+- Use official NATO spelling for all team names.
+- Do not use `Alpha`, `Beta`, or `Gamma` for active teams.
+- Deprecated or historical names must not be used for active team routing, new work ownership, or current governance.
+- Historical PR names, branch names, and references may remain unchanged when they are already merged or clearly referenced as history.
+- New branches, PRs, reports, and documentation must use canonical team names.
+- Repository documentation overrides prior conversations.
+
## Current Version/Date

-- Project Instructions Version: 2026-06-28.PR_26179_OWNER_010
+- Project Instructions Version: 2026-06-28.PR_26172_OWNER_034
- Date: 2026-06-28
- Owner: OWNER
Loading