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 f31fa61
Browse filesBrowse the repository at this point in the historyBrowse files
`docs_build/dev/ProjectInstructions/addendums/koti_layout_contract.md` defines the King of the Iceberg layout data contract.
58
58
59
+
`docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md` defines the Creator-facing stacked PR standard for tool MVP work.
60
+
59
61
## Single Source and Main Lock Governance
60
62
61
63
`docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md` defines the single active Project Instructions source, canonical START / WORK / END branch lifecycle, EOD main lock, next-day reset, team branch creation gate, daily synchronization baseline, and mandatory hard stops.
For tool MVPs, use one large Codex command, multiple focused stacked PRs, and one testable Creator outcome per PR.
128
+
129
+
Do not create one giant PR.
130
+
131
+
Do not stop after every small PR unless blocked by branch state, failed validation, missing source files, Project Instructions conflict, or an unresolved dependency from a prior PR.
132
+
133
+
Each tool MVP PR plan or template must include:
134
+
- Creator-testable outcome
135
+
- What Playwright tests
136
+
- What Mr. Q should manually test
137
+
- Whether the PR is part of a stacked MVP sequence
138
+
- Previous PR dependency
139
+
- Next PR dependency
140
+
141
+
Visible acceptance must be Creator-facing first. Architecture can be handled under the covers, but the PR purpose must be user-testable.
Define how Codex plans and executes Creator-facing tool MVP work without creating one giant PR or stopping after every small PR.
9
+
10
+
## Standard
11
+
12
+
For tool MVPs, use:
13
+
14
+
```text
15
+
One large Codex command -> multiple focused stacked PRs -> each PR has a testable Creator outcome.
16
+
```
17
+
18
+
## Rules
19
+
20
+
- Do not create one giant PR.
21
+
- Do not stop after every small PR unless blocked.
22
+
- Each PR must be independently scoped.
23
+
- Each PR must produce a Creator-testable outcome.
24
+
- Each PR must answer:
25
+
26
+
```text
27
+
What can Mr. Q test after applying this ZIP?
28
+
```
29
+
30
+
- Codex must continue through the stacked PR sequence unless blocked by:
31
+
- branch state
32
+
- failed validation
33
+
- missing source files
34
+
- Project Instructions conflict
35
+
- unresolved dependency from a prior PR
36
+
37
+
## Creator-Facing Acceptance
38
+
39
+
For tool MVP PR planning, visible acceptance must be Creator-facing first.
40
+
41
+
Architecture can be handled under the covers, but PR purpose must be user-testable.
42
+
43
+
Each tool MVP PR must state:
44
+
- Creator-testable outcome
45
+
- What Playwright tests
46
+
- What Mr. Q should manually test
47
+
- Whether the PR is part of a stacked MVP sequence
48
+
- Previous PR dependency
49
+
- Next PR dependency
50
+
51
+
## Hitboxes MVP Example Stack
52
+
53
+
Example Hitboxes MVP stack:
54
+
55
+
- PR 1: Creator can open the tool and choose a real/test object.
56
+
- PR 2: Creator can see the object and draw a rectangle hitbox.
57
+
- PR 3: Creator can move/resize/save/reload hitboxes.
58
+
- PR 4: Creator can test Object A vs Object B collision.
59
+
- PR 5: Creator can test speed/animation so fast objects do not skip collision.
60
+
- PR 6: Polish and regression coverage.
61
+
62
+
## Lifecycle Relationship
63
+
64
+
Tool MVP stacks are explicitly documented stacked PR chains.
65
+
66
+
Each PR in the stack still follows the canonical START / WORK / END lifecycle and must produce required reports and a repo-structured ZIP.
67
+
68
+
When OWNER gives one large Codex command for a tool MVP stack, Codex may continue from one completed PR to the next without stopping for a conversational checkpoint, unless a blocker listed in this standard occurs.
69
+
70
+
The final PR in the stack must perform normal closeout and stop all work after returning to synchronized main.
- Updated PR workflow governance so tool MVP PR plans/templates include Creator-testable outcome, Playwright test scope, Mr. Q manual test scope, stacked MVP sequence membership, and previous/next PR dependencies.
21
+
- Updated Codex artifact/reporting governance so every tool MVP PR report includes those same fields and answers what Mr. Q can test after applying the ZIP.
19
22
- Corrected project-instructions/** scope so the PR only adds a tiny deprecated pointer README there.
20
23
- Preserved project-instructions/addendums/** unchanged in the PR; unique current governance content is carried by docs_build/dev/ProjectInstructions/addendums/.
21
24
- Confirmed docs_build/dev root no longer contains active loose instruction, audit, contract, or PR files.
22
25
- No product/runtime, start_of_day, feature, or legacy SQLite file changes were made.
23
26
27
+
## Tool MVP Stacked PR Standard
28
+
29
+
Added governance:
30
+
- One large Codex command -> multiple focused stacked PRs -> each PR has a testable Creator outcome.
31
+
- No one giant PR.
32
+
- No stopping after every small PR unless blocked.
33
+
- Each PR is independently scoped and Creator-testable.
34
+
- Each PR answers: What can Mr. Q test after applying this ZIP?
35
+
- Codex continues through the stack unless blocked by branch state, failed validation, missing source files, Project Instructions conflict, or unresolved prior-PR dependency.
36
+
- Visible acceptance for tool MVP planning is Creator-facing first.
Copy file name to clipboardExpand all lines: docs_build/dev/reports/PR_26177_OWNER_007-project-instructions-single-source-eod-lock_branch-validation.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,7 @@ Status: PASS
6
6
- PASS: Branch is not main during WORK.
7
7
- PASS: Worktree changes are scoped to governance/docs cleanup, reports, and the required delta artifact.
8
8
- PASS: docs_build/dev root contains no loose files after moving PR docs, active addendums, and audit outputs.
9
+
- PASS: Tool MVP Stacked PR Standard was added under docs_build/dev/ProjectInstructions/addendums/.
9
10
- PASS: project-instructions/** is limited to a tiny deprecated pointer README in the PR diff.
0 commit comments