Update README to define zlh-grind as GPT execution workspace
This commit is contained in:
parent
9aa445c00c
commit
a86f7d8150
28
README.md
28
README.md
@ -1,3 +1,29 @@
|
|||||||
# zlh-grind
|
# zlh-grind
|
||||||
|
|
||||||
The daily GPT grind
|
**GPT Execution Workspace for ZeroLagHub**
|
||||||
|
|
||||||
|
This repository is dedicated exclusively to **GPT-driven implementation work**.
|
||||||
|
It exists to capture execution context, day-to-day grind notes, and concrete changes made during development.
|
||||||
|
|
||||||
|
## What This Repo Is For
|
||||||
|
- Daily GPT work logs
|
||||||
|
- Session handovers
|
||||||
|
- Implementation notes and scratchpads
|
||||||
|
- Tracking *what was changed, when, and why*
|
||||||
|
|
||||||
|
## What This Repo Is NOT
|
||||||
|
- ❌ Architecture decisions
|
||||||
|
- ❌ Cross-project source of truth
|
||||||
|
- ❌ Product or strategy documentation
|
||||||
|
|
||||||
|
All canonical architecture, decisions, and references live in:
|
||||||
|
**`jester/knowledge-base`**
|
||||||
|
|
||||||
|
## Working Rules
|
||||||
|
- This repo may be messy, iterative, and practical
|
||||||
|
- Prefer clarity over polish
|
||||||
|
- Reference canonical docs instead of duplicating them
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
If it happened during hands-on GPT execution, it belongs here.
|
||||||
Loading…
Reference in New Issue
Block a user