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
{{ message }}
Repository navigation
Commit e28724f
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: dev/build/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md
+7-11Lines changed: 7 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,19 +97,15 @@ Optional:
97
97
98
98
Generated non-report artifacts must live under `dev/workspace/`.
99
99
100
-
## Tracked Report Governance
100
+
## Codex Reports
101
101
102
-
`dev/reports/` is an authoritative repository report location and is tracked by Git.
103
-
104
-
Rules:
105
-
106
-
- Any changes to `dev/reports/` generated during a PR are expected to be included in that PR.
107
-
- A clean `main` means the latest report files have been committed and merged.
108
-
- Do not delete report files only to make the worktree clean.
102
+
-`dev/reports/` contains the authoritative Codex reports for the repository.
103
+
- Reports committed to `main` are the official record.
104
+
- Reports generated during a PR are expected to be committed as part of that PR.
105
+
- Once merged into `main`, those report versions become the canonical repository history.
106
+
- Do not delete report files solely to obtain a clean worktree.
109
107
- Do not add `dev/reports/` to `.gitignore`.
110
-
- Do not move reports outside the repository.
111
-
- Continue using `dev/reports/` for reports and `dev/workspace/zips/` for ZIPs.
112
-
- Generated post-merge closeout reports should either be committed in a follow-up governance/report PR or avoided on `main` when no commit is intended.
108
+
- Continue storing ZIPs under `dev/workspace/zips/`.
Copy file name to clipboardExpand all lines: dev/build/ProjectInstructions/addendums/pr_workflow.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ Closed gates:
105
105
- PR merged and changes pushed.
106
106
- Current branch is `main`.
107
107
-`main` includes the merge commit or recorded final commit.
108
-
- Worktree clean, including tracked`dev/reports/` updates committed and merged.
108
+
- Worktree clean, including intended`dev/reports/` updates committed and merged.
109
109
- Local/origin sync is `0/0`.
110
110
- No untracked files.
111
111
- Branch disposition is recorded as `retained`.
@@ -132,7 +132,7 @@ Closed gates:
132
132
- If OWNER decision is required, stop and report.
133
133
- Every PR lifecycle state must satisfy the Codex Completion Contract when Codex executes work for that state.
134
134
- ZIP artifacts belong under `dev/workspace/zips/` and must not replace required reports under `dev/reports/`.
135
-
-Generated reports under `dev/reports/`are tracked source for the PR. Do not delete report files only to make the worktree clean, do not ignore`dev/reports/`, and do not move reports outside the repository.
135
+
-Reports generated during a PR are expected to be committed as part of that PR. Do not delete report files solely to obtain a clean worktree, and do not add`dev/reports/` to `.gitignore`.
136
136
- Stacked PR chains produce one final outcome ZIP per attempted PR and stop before later PRs after failure or hard stop.
Copy file name to clipboardExpand all lines: dev/build/ProjectInstructions/repository/canonical_repository_structure.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,7 @@ Dev workspace ownership:
62
62
- dev/archive/ owns historical reference material only.
63
63
- dev/build/ owns active Project Instructions, architecture, database DDL/DML/seed docs, standards, backlog, PR planning, and governance.
64
64
- dev/config/ owns development-only runner and tooling configuration.
65
-
- dev/reports/ owns active and historical generated reports. Report files under `dev/reports/` are authoritative tracked repository source and must not be deleted only to make the worktree clean.
65
+
- dev/reports/ owns authoritative Codex reports for the repository. Reports committed to `main` are the official record.
66
66
- dev/scripts/ owns development-only scripts and runners.
67
67
- dev/templates/ owns reusable development templates.
68
68
- dev/tests/ owns non-deployable test suites.
@@ -110,7 +110,7 @@ These legacy transition buckets may remain until explicit migration PRs move the
110
110
- New development follows the canonical structure.
111
111
- New deployable `src/` work follows `src/web/`, `src/api-runtime/`, or `src/runtime/`.
112
112
- New non-deployable work belongs under `dev/`.
113
-
- Required reports belong under flat tracked `dev/reports/`.
113
+
- Required reports belong under flat `dev/reports/`.
114
114
- Required ZIPs belong under `dev/workspace/zips/`; generated temporary artifacts belong under `dev/workspace/tmp/`.
Confirm the policy says tracked report files are expected PR source, and that post-merge closeout reports should be committed in a follow-up governance/report PR or avoided on `main` when no commit is intended.
11
+
Confirm the policy says `dev/reports/` contains authoritative Codex reports, reports committed to `main` are the official record, and PR-generated reports are expected to be committed as part of that PR.
Copy file name to clipboardExpand all lines: dev/reports/PR_26179_OWNER_036-reports-are-tracked-source_report.md
+12-10Lines changed: 12 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@
2
2
3
3
## Summary
4
4
5
-
This governance PR clarifies that `dev/reports/`is authoritative tracked repository source. Codex-generated reports are expected to be committed with the PR that generated them, and generated post-merge closeout reports should be committed through a follow-up governance/report PR or avoided on `main` when no commit is intended.
5
+
This governance PR clarifies that `dev/reports/`contains the authoritative Codex reports for the repository and that reports committed to `main` are the official record. Reports generated during a PR are expected to be committed as part of that PR, while repository authority remains the report state committed to `main`.
6
6
7
7
## Scope
8
8
9
9
- Updated Codex artifact/reporting governance.
10
10
- Updated canonical repository structure wording for `dev/reports/`.
11
-
- Updated PR workflow clean-main guidance for tracked reports.
11
+
- Updated PR workflow clean-main guidance for intended report updates.
12
12
- Preserved the existing PR277 post-merge closeout report artifacts instead of deleting them.
13
13
- No runtime code changes.
14
14
- No auth changes.
@@ -17,15 +17,17 @@ This governance PR clarifies that `dev/reports/` is authoritative tracked reposi
17
17
18
18
## Policy Added
19
19
20
-
-`dev/reports/` is authoritative and tracked by Git.
21
-
- Any changes to `dev/reports/` generated during a PR are expected to be included in that PR.
22
-
- A clean `main` means the latest report files have been committed and merged.
23
-
- Do not delete report files only to make the worktree clean.
20
+
-`dev/reports/` contains the authoritative Codex reports for the repository.
21
+
- Reports committed to `main` are the official record.
22
+
- Reports generated during a PR are expected to be committed as part of that PR.
23
+
- Once merged into `main`, those report versions become the canonical repository history.
24
+
- Do not delete report files solely to obtain a clean worktree.
24
25
- Do not add `dev/reports/` to `.gitignore`.
25
-
- Do not move reports outside the repository.
26
-
- Continue using `dev/reports/` for reports and `dev/workspace/zips/` for ZIPs.
27
-
- Generated post-merge closeout reports should either be committed in a follow-up governance/report PR or avoided on `main` if no commit is intended.
26
+
- Continue storing ZIPs under `dev/workspace/zips/`.
28
27
29
28
## Validation
30
29
31
-
Pending at report creation; final results are recorded in the validation report.
0 commit comments