jester/zlh-grind
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

Update CONSTRAINTS.md - Add operational constraints for single base template architecture and agent change implications

Browse Source
This commit is contained in:
jester 2025-12-20 23:19:26 +00:00
parent c6daf21a52
commit a6cb030762
1 changed files with 10 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
CONSTRAINTS.md
View File

@ -1,18 +1,15 @@
# Constraints – zlh-grind # Constraints – zlh-grind
This repository is strictly for **GPT execution work**. This repository is strictly for **GPT execution context + logs**.
## Hard Rules Non-negotiables:
- Do NOT make architecture decisions here - Do NOT refactor code here
- Do NOT invent missing system facts
- Do NOT redefine system boundaries - Do NOT redefine system boundaries
- Do NOT duplicate canonical documentation - Do NOT duplicate canonical docs from upstream repos
## Source of Truth Operational constraints (ZeroLagHub specific):
All architecture, decisions, and authoritative docs live in: - We are using **one base template** (`AGENT_TEMPLATE_VMID`) by design.
- `jester/knowledge-base` - In current workflow, updating zlh-agent implies building + copying binary into the template container:
- **agent change == template promotion**
## Role Split - Prefer API-side wire compatibility fixes over agent/template changes unless we intentionally schedule a template rev.
- Claude: architecture, decisions, control-plane changes
- GPT: execution, implementation, logging, reasoning
If a change might affect architecture, stop and defer.