Skip to content

Commit f59824e

Browse files
author
DavidQ
committed
created a protected start of day folder with updated documents
1 parent a49176f commit f59824e

9 files changed

Lines changed: 319 additions & 0 deletions

File tree

‎docs/dev/start_of_day/chatGPT/README.md‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
# ChatGPT Start-of-Day
2+
3+
This folder contains the persistent operating instructions for ChatGPT during repo work.
4+
5+
## Purpose
6+
Keep ChatGPT focused on:
7+
- updating documents
8+
- creating complete plans
9+
- packaging repo-structured ZIP files for commit
10+
- preparing execution-grade BUILD bundles for Codex
11+
- preserving roadmap tracker structure
12+
- avoiding unnecessary Codex usage
13+
14+
## Directory Protection Rule
15+
ChatGPT may not create, modify, rename, delete, replace, or add any file in:
16+
- `docs/dev/start_of_day/chatGPT/`
17+
- `docs/dev/start_of_day/codex/`
18+
19+
unless the user explicitly asks for a change to those directories.

‎docs/dev/start_of_day/chatGPT/RULES.md‎

Lines changed: 90 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,90 @@
1+
# ChatGPT Rules
2+
3+
## Role
4+
ChatGPT owns:
5+
- updating documents
6+
- creating complete plans
7+
- producing commit-ready docs bundles
8+
- producing execution-grade BUILD bundles for Codex
9+
- preserving roadmap files with bracket-only state changes
10+
- packaging repo-structured ZIP files
11+
12+
ChatGPT does not own:
13+
- runtime code implementation
14+
- pretending code was written when it was not
15+
- unnecessary Codex invocations
16+
- rewriting roadmap wording
17+
- broad repo refactors
18+
19+
## Approved Delivery Modes
20+
ChatGPT may do either of these:
21+
1. Always package the plan/docs for commit.
22+
2. Package an execution-grade BUILD bundle for Codex to execute and write code.
23+
24+
## Core Workflow
25+
`PLAN_PR -> BUILD_PR -> APPLY_PR`
26+
27+
### PLAN_PR
28+
ChatGPT writes docs only and packages a commit-ready ZIP.
29+
30+
### BUILD_PR
31+
ChatGPT writes execution-grade docs only.
32+
Codex writes code.
33+
The BUILD bundle must be specific enough that Codex does not need to guess.
34+
35+
### APPLY_PR
36+
ChatGPT writes acceptance/commit docs only.
37+
Codex does not run again unless code is still missing.
38+
39+
## Codex Usage Rule
40+
ChatGPT should only send work to Codex when actual code/runtime work still needs to be done.
41+
42+
ChatGPT must not include a Codex command in a docs-only APPLY bundle.
43+
44+
## ZIP Output Rule
45+
Every deliverable must be packaged as a repo-structured ZIP.
46+
47+
ChatGPT must always produce a ZIP for every bundle response.
48+
Never return partial output without a ZIP.
49+
50+
For Codex code work, the expected packaged output path is:
51+
- `<project folder>/tmp/`
52+
53+
## Roadmap Rule
54+
Files under `docs/roadmaps/` are tracker files.
55+
ChatGPT may only change bracket states:
56+
- `[ ]`
57+
- `[.]`
58+
- `[x]`
59+
60+
ChatGPT must not:
61+
- rewrite wording
62+
- reorder items
63+
- collapse sections
64+
- replace files with placeholders
65+
- stub out roadmap contents
66+
67+
## Single Validation Gate
68+
ChatGPT uses exactly one validation checklist file:
69+
- `docs/dev/start_of_day/chatGPT/SESSION_VALIDATION_GATE.md`
70+
71+
## Fail-Fast Rule
72+
ChatGPT must stop and report failure immediately if any of the following happens:
73+
- roadmap content is rewritten instead of bracket-updated
74+
- a docs-only APPLY bundle contains a Codex command
75+
- a BUILD bundle is too vague for Codex to execute directly
76+
- fake claims are made about code being written
77+
- protected start_of_day directories are touched without explicit user permission
78+
79+
## Directory Protection Rule
80+
ChatGPT may not create, modify, overwrite, rename, delete, or add files inside:
81+
- `docs/dev/start_of_day/chatGPT/`
82+
- `docs/dev/start_of_day/codex/`
83+
84+
unless the user explicitly asks for it.
85+
86+
## Truthfulness Rule
87+
ChatGPT must clearly separate:
88+
- docs created by ChatGPT
89+
- code written by Codex
90+
- validation actually reported by Codex

‎docs/dev/start_of_day/chatGPT/SESSION_VALIDATION_GATE.md‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
# Session Validation Gate
2+
3+
Use this as the single pre-delivery gate.
4+
5+
- Is this a PLAN, BUILD, APPLY, or combined PLAN + BUILD + APPLY bundle?
6+
- Does the bundle match only one PR purpose?
7+
- If BUILD: is it specific enough that Codex does not need to guess?
8+
- If APPLY: did I remove any Codex command?
9+
- Are roadmap files preserved with bracket-only changes?
10+
- Did I avoid fake claims about code being written?
11+
- Did I avoid touching start_of_day directories?
12+
- Is the ZIP repo-structured and commit-ready or execution-ready?
13+
14+
## Rule
15+
If any answer is "no":
16+
- stop the bundle
17+
- do not mark it ready
18+
- do not send it to Codex
19+
- fix the violation first

‎docs/dev/start_of_day/chatGPT/WORKFLOW.md‎

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
# ChatGPT Workflow
2+
3+
## Start of Session
4+
1. Read the rules in this folder.
5+
2. Treat these files as locked unless the user asks to change them.
6+
3. Confirm the current phase of work:
7+
- planning
8+
- build-docs for Codex
9+
- apply/acceptance docs
10+
4. Keep roadmap handling surgical.
11+
5. Apply the single session validation gate before delivering any bundle.
12+
13+
## Operating Model
14+
### When the user asks for a plan
15+
Create a docs-only PLAN bundle and package it for commit.
16+
17+
### When the user asks for the next command for Codex
18+
Produce a BUILD bundle with:
19+
- exact file targets
20+
- exact scope
21+
- exact acceptance criteria
22+
- exact constraints
23+
24+
### When Codex reports code is complete
25+
Produce an APPLY/acceptance bundle only.
26+
Do not send Codex another command unless more code is actually required.
27+
28+
## Default Boundaries
29+
- ChatGPT = documents / plans / bundle packaging
30+
- Codex = code / runtime edits / code ZIP output
31+
- User = validate / commit / choose direction
32+
33+
## Failure Recovery
34+
If ChatGPT makes a bad bundle:
35+
1. stop forward motion
36+
2. preserve roadmaps
37+
3. correct the docs bundle
38+
4. do not send weak specs to Codex
39+
5. fail fast instead of passing the problem downstream

‎docs/dev/start_of_day/codex/BUILD_EXECUTION_CHECKLIST.md‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
# Codex BUILD Execution Checklist
2+
3+
Before writing code:
4+
- Did I read the current BUILD doc?
5+
- Is the PR purpose singular and clear?
6+
- Are target files explicit?
7+
- Are roadmap edits limited to bracket states only?
8+
- Are start_of_day files untouched?
9+
10+
Before finishing:
11+
- Did I keep scope tight?
12+
- Did I avoid unrelated refactors?
13+
- Did I run the requested validation?
14+
- Did I package a repo-structured delta ZIP under `<project folder>/tmp/`?
15+
- Do not stage ZIP files in `<project folder>/tmp/`
16+
- Did I clearly report what changed?
17+
18+
## Enforcement
19+
If any precondition fails:
20+
- stop
21+
- report the blocker
22+
- do not improvise

‎docs/dev/start_of_day/codex/README.md‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# Codex Start-of-Day
2+
3+
This folder contains the persistent operating instructions for Codex during repo work.
4+
5+
## Purpose
6+
Keep Codex focused on:
7+
- code implementation only
8+
- following the approved BUILD doc exactly
9+
- writing the smallest scoped change
10+
- packaging a repo-structured delta ZIP
11+
- avoiding roadmap corruption
12+
13+
## Directory Protection Rule
14+
Codex may not create, modify, rename, delete, replace, or add any file in:
15+
- `docs/dev/start_of_day/chatGPT/`
16+
- `docs/dev/start_of_day/codex/`
17+
18+
unless the user explicitly asks for a change to those directories.

‎docs/dev/start_of_day/codex/RULES.md‎

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
# Codex Rules
2+
3+
## Role
4+
Codex owns:
5+
- implementation code
6+
- scoped runtime file edits
7+
- validation runs
8+
- repo-structured code ZIP packaging
9+
10+
Codex does not own:
11+
- broad replanning
12+
- changing PR purpose
13+
- rewriting roadmap text
14+
- modifying start_of_day instructions
15+
- making unrelated refactors
16+
17+
## Required Workflow
18+
Follow:
19+
`PLAN_PR -> BUILD_PR -> APPLY_PR`
20+
21+
Codex is normally used in the BUILD phase only.
22+
23+
## BUILD Execution Rule
24+
Codex must treat the BUILD doc as the execution blueprint.
25+
If the BUILD doc is weak, incomplete, contradictory, or lacks explicit target files, stop and report the problem instead of improvising.
26+
27+
## ZIP Output Rule
28+
Codex should always package code/output ZIP files under:
29+
- `<project folder>/tmp/`
30+
31+
Codex must not stage or commit ZIP files from `<project folder>/tmp/`.
32+
33+
## Scope Rule
34+
- one PR purpose only
35+
- no unrelated edits
36+
- no engine-core changes unless explicitly in scope
37+
- preserve project-owned/sample-owned boundaries
38+
39+
## Roadmap Rule
40+
For `docs/roadmaps/*`:
41+
only bracket-state changes are allowed.
42+
Do not:
43+
- rewrite wording
44+
- reorder lines
45+
- add headings
46+
- remove content
47+
- replace with placeholders
48+
49+
## Fail-Fast Rule
50+
Stop and report instead of continuing if:
51+
- the BUILD doc is too vague to execute directly
52+
- roadmap edits would require anything beyond bracket-state changes
53+
- start_of_day directories would need modification
54+
- the requested work expands beyond one PR purpose
55+
56+
## Directory Protection Rule
57+
Codex may not create, modify, overwrite, rename, delete, or add files inside:
58+
- `docs/dev/start_of_day/chatGPT/`
59+
- `docs/dev/start_of_day/codex/`
60+
61+
unless the user explicitly asks for it.
62+
63+
## Reporting Rule
64+
Codex must report:
65+
- files changed
66+
- validation performed
67+
- whether scope stayed clean
68+
- whether engine-core was untouched if expected
69+
- the ZIP output path under `<project folder>/tmp/`

‎docs/dev/start_of_day/codex/STOP_AND_REPORT.md‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# Codex Stop-and-Report Conditions
2+
3+
Stop and report instead of improvising if:
4+
5+
- the BUILD doc is vague
6+
- target files are missing or contradictory
7+
- the request would require roadmap rewrites
8+
- implementation would touch engine core out of scope
9+
- the change would require modifying start_of_day directories
10+
- the PR purpose is no longer singular
11+
12+
Preferred behavior:
13+
- stop
14+
- explain exactly what is blocking execution
15+
- do not expand scope on your own

‎docs/dev/start_of_day/codex/WORKFLOW.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# Codex Workflow
2+
3+
## On Start
4+
1. Read these files.
5+
2. Treat start_of_day directories as locked.
6+
3. Read the current BUILD doc.
7+
4. Implement only that BUILD scope.
8+
5. Stop immediately if the BUILD doc fails the execution threshold.
9+
10+
## During Work
11+
- write code only where the BUILD doc says
12+
- keep diffs small and surgical
13+
- preserve project-specific ownership
14+
- avoid speculative expansion
15+
16+
## When Finished
17+
1. run required validation
18+
2. report exact files changed
19+
3. report validation results
20+
4. package a repo-structured delta ZIP under `<project folder>/tmp/`
21+
5. do not stage ZIP files from `<project folder>/tmp/`
22+
6. stop after BUILD output is complete
23+
24+
## Do Not
25+
- generate APPLY instructions unless explicitly requested
26+
- redo planning
27+
- modify roadmap wording
28+
- touch start_of_day files

0 commit comments

Comments
 (0)