Skip to content

Commit 8a39f5a

Browse files
author
DavidQ
committed
- Consolidated active dev workflow docs and moved durable architecture content
- Added archive structure for start_of_day
1 parent aa014c6 commit 8a39f5a

6 files changed

Lines changed: 223 additions & 0 deletions

File tree

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
MODEL: GPT-5.4-codex
2+
REASONING: high
3+
4+
COMMAND:
5+
Follow PLAN_PR -> BUILD_PR -> APPLY_PR
6+
7+
- Docs-first unless BUILD/APPLY
8+
- No engine core changes
9+
- One PR per purpose
10+
- Keep integration sample-level
11+
- Package to <project folder>/tmp/*.zip
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# CURRENT STATE
2+
3+
## Working Systems
4+
- Dev Console (interactive)
5+
- Debug Overlay HUD (canvas)
6+
- Combo key input system
7+
- Scene loader + hot reload
8+
9+
## Integration
10+
- MultiSystemDemoScene.js
11+
12+
## Status
13+
Stable and validated
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# NEXT STEPS
2+
3+
## Recommended Next PR
4+
PLAN_PR_DEV_CONSOLE_COMMAND_PACKS
5+
6+
## Goals
7+
- structured commands (scene.*, render.*, entity.*)
8+
- better output formatting
9+
- scalable command system
Lines changed: 112 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,112 @@
1+
# RULES OF ENGAGEMENT
2+
3+
## 1. Workflow (MANDATORY)
4+
Always follow:
5+
6+
PLAN_PR → BUILD_PR → APPLY_PR
7+
8+
- Do not skip steps
9+
- One PR per purpose
10+
- Docs-first unless explicitly BUILD/APPLY
11+
12+
---
13+
14+
## 2. Responsibilities
15+
16+
### ChatGPT
17+
- Designs, plans, and produces PR bundles (ZIP)
18+
- NEVER writes implementation code unless explicitly asked
19+
- Focuses on architecture, structure, and correctness
20+
21+
### Codex
22+
- Writes ALL implementation code
23+
- Executes BUILD_PR and APPLY_PR
24+
- Modifies repo files
25+
26+
---
27+
28+
## 3. Repo Constraints
29+
30+
- No engine core changes unless explicitly approved
31+
- Prefer sample-level integration
32+
- Avoid tight coupling between engine and tools
33+
- Normalize toward GameBase-style architecture
34+
35+
---
36+
37+
## 4. File & Output Rules
38+
39+
- All PR outputs must be packaged as ZIP
40+
- Output path:
41+
<project>/tmp/<ZIP_NAME>.zip
42+
43+
- ZIP must:
44+
- Preserve repo-relative structure
45+
- Include ONLY files relevant to the PR
46+
- Contain NO build artifacts or unrelated files
47+
48+
---
49+
50+
## 5. Documentation Rules
51+
52+
- PR docs → docs/pr/
53+
- Dev commands → docs/dev/codex_commands.md
54+
- Commit comment → docs/dev/commit_comment.txt (NO HEADER)
55+
- Reports → docs/dev/reports/
56+
57+
---
58+
59+
## 6. Architecture Principles
60+
61+
- Tools → Contracts → Runtime → Debug → Visual
62+
- Clear separation of concerns
63+
- No duplication of runtime logic
64+
- Reuse existing systems before creating new ones
65+
66+
---
67+
68+
## 7. Debug System Rules
69+
70+
- Debug features must be:
71+
- isolated
72+
- toggleable
73+
- non-invasive
74+
75+
- Input must not conflict with browser or gameplay
76+
- Debug UI must render AFTER gameplay
77+
78+
---
79+
80+
## 8. Codex Execution Rules
81+
82+
All Codex commands must include:
83+
84+
MODEL: GPT-5.x-codex
85+
REASONING: high
86+
87+
Must specify:
88+
- files to create/update
89+
- constraints
90+
- packaging path
91+
92+
---
93+
94+
## 9. Quality Bar
95+
96+
Every PR must:
97+
- be minimal and surgical
98+
- avoid breaking runtime
99+
- avoid duplication
100+
- be easy to validate
101+
102+
---
103+
104+
## 10. Session Continuity
105+
106+
Always use:
107+
- SESSION_CONTEXT.md
108+
- CURRENT_STATE.md
109+
- NEXT_STEPS.md
110+
- RULES_OF_ENGAGEMENT.md
111+
112+
to resume work
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
# SESSION CONTEXT
2+
3+
## Project
4+
HTML-JavaScript-Gaming
5+
6+
## Architecture
7+
TOOLS → CONTRACT → RUNTIME → DEBUG → VISUAL
8+
9+
## Systems Built
10+
- Render pipeline contracts
11+
- Runtime scene loader + hot reload
12+
- Dev console runtime
13+
- Canvas HUD
14+
- Interactive console UI
15+
16+
## Rules
17+
- Docs-first workflow
18+
- Codex writes code
19+
- No engine pollution
20+
- Sample-level integration only
Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
Toolbox Aid
2+
David Quesenberry
3+
04/05/2026
4+
BUILD_PR_START_OF_DAY_PACK.md
5+
6+
# BUILD PR
7+
Start Of Day Pack
8+
9+
## Objective
10+
Create a standardized dev/docs/start_of_day folder containing only the essential files needed to resume work in ChatGPT and Codex sessions.
11+
12+
## Scope
13+
- Create docs/dev/start_of_day/
14+
- Place curated minimal files for session bootstrap
15+
- Remove duplication and noise
16+
- Keep files lightweight and copy/paste friendly
17+
18+
## Required Files
19+
20+
docs/dev/start_of_day/
21+
- SESSION_CONTEXT.md
22+
- CODEX_SESSION_PROMPT.md
23+
- CURRENT_STATE.md
24+
- NEXT_STEPS.md
25+
26+
## File Definitions
27+
28+
### SESSION_CONTEXT.md
29+
- Project overview
30+
- Architecture summary
31+
- Key constraints (docs-first, no engine pollution, etc.)
32+
33+
### CODEX_SESSION_PROMPT.md
34+
- Copy/paste ready Codex command template
35+
- Includes model + reasoning + command format
36+
37+
### CURRENT_STATE.md
38+
- What has been completed
39+
- Current active systems (console, HUD, runtime, etc.)
40+
41+
### NEXT_STEPS.md
42+
- Current next PR
43+
- Short task list
44+
45+
## Constraints
46+
- No runtime/code changes
47+
- Docs only
48+
- No duplication of large PR history
49+
- Keep under 200 lines per file
50+
51+
## Acceptance Criteria
52+
- Folder exists and is clean
53+
- Files are minimal and useful
54+
- Can restart ChatGPT session with SESSION_CONTEXT.md
55+
- Can restart Codex session with CODEX_SESSION_PROMPT.md
56+
57+
## Output
58+
<project folder>/tmp/BUILD_PR_START_OF_DAY_PACK_delta.zip

0 commit comments

Comments
 (0)