From a6cb03076247076007846365f5651714982193f9 Mon Sep 17 00:00:00 2001
From: jester <admin@zerolaghub.com>
Date: Sat, 20 Dec 2025 23:19:26 +0000
Subject: [PATCH] Update CONSTRAINTS.md - Add operational constraints for
 single base template architecture and agent change implications

---
 CONSTRAINTS.md | 23 ++++++++++-------------
 1 file changed, 10 insertions(+), 13 deletions(-)

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