From 1da3f9028ba21712f2b446f8527a95337877ace0 Mon Sep 17 00:00:00 2001
From: Eddie Soehnel <edsoehnel@gmail.com>
Date: Sat, 21 Mar 2026 06:55:27 -0600
Subject: [PATCH] Update agents.md

added AI change rules for propagating docs when changes made
---
 specs/agents.md | 32 ++++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)

diff --git a/specs/agents.md b/specs/agents.md
index 4fb5264..3f88ef5 100644
--- a/specs/agents.md
+++ b/specs/agents.md
@@ -21,3 +21,35 @@ in specs folder. Ignore anything with "draft" in the name.  Pointy out workflow
 # Additional General Requirements
 
  Code is created in files.  Code is well documented and explains why the code exists, what it does, maintenance tips, gotchas if any.
+ 
+ ## Change Propagation Rules
+ 
+ When any of the following are modified:
+ - API responses
+ - data structures
+ - business logic
+ - system behavior
+ 
+ You must:
+ 
+ 1. Identify all affected layers:
+    - specs
+    - srv
+    - data-ops
+    - tests
+ 
+ 2. Update only the impacted sections, but in audit mode first. Do not edit yet until I review and give command to proceed with updates
+ 
+ 3. Maintain consistency across:
+    - schema definitions
+    - example data
+    - architecture documentation
+ 
+ 4. Add an entry to `specs/decisions.md` if the change alters:
+    - system behavior
+    - data contracts
+    - architectural assumptions
+ 
+ 5. Do not rewrite entire documents unless explicitly instructed
+ 
+ Consider writing a change audit template md file for above. 
\ No newline at end of file