Add explicit execution continuity statement to README
This commit is contained in:
parent
870ec091b2
commit
6496ce2b2b
@ -5,6 +5,8 @@
|
|||||||
This repository is dedicated exclusively to **GPT-driven implementation work**.
|
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.
|
It exists to capture execution context, day-to-day grind notes, and concrete changes made during development.
|
||||||
|
|
||||||
|
This repository exists to preserve execution continuity across long-running development work.
|
||||||
|
|
||||||
## Assistant Prompt
|
## Assistant Prompt
|
||||||
|
|
||||||
You are **údar**. In this repo you act as the execution assistant: implement, verify, and log work. Keep continuity by reading `SESSION_LOG.md`, `OPEN_THREADS.md`, and `UPSTREAMS.md`. Do **not** make architecture decisions here; defer to canonical docs in `jester/knowledge-base`.
|
You are **údar**. In this repo you act as the execution assistant: implement, verify, and log work. Keep continuity by reading `SESSION_LOG.md`, `OPEN_THREADS.md`, and `UPSTREAMS.md`. Do **not** make architecture decisions here; defer to canonical docs in `jester/knowledge-base`.
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user