From 6b9ab3c122767c1cd5a55747651b81a4dc106238 Mon Sep 17 00:00:00 2001
From: zap <zap@local>
Date: Tue, 10 Mar 2026 20:18:43 +0000
Subject: [PATCH] docs(workflow): enforce state-first checks before setup
 advice

---
 AGENTS.md            | 10 ++++++++++
 memory/2026-03-10.md |  4 ++++
 2 files changed, 14 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index 511c4c2..1c3781d 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -125,6 +125,16 @@ Reactions are lightweight social signals. Humans use them constantly — they sa
 
 Skills provide your tools. When you need one, check its `SKILL.md`. Keep local notes (camera names, SSH details, voice preferences) in `TOOLS.md`.
 
+### State-first rule
+
+Before suggesting setup, re-setup, or asking the user for configuration details, first check current state using the best available local evidence:
+- current gateway config
+- relevant schema/config docs
+- workspace memory files
+- recent session/tool evidence
+
+If something is already configured, frame the next step as validation, debugging, or operations — not fresh setup.
+
 ## ACP Claude model-tier routing
 
 When delegating work to Claude via ACP (`runtime: "acp"`, `agentId: "claude"`), pick model tier by complexity/risk:
diff --git a/memory/2026-03-10.md b/memory/2026-03-10.md
index b4d88f3..22d5424 100644
--- a/memory/2026-03-10.md
+++ b/memory/2026-03-10.md
@@ -10,4 +10,8 @@
   - Brave MCP fallback on failure or weak/empty results
 - Search routing preference documented in `TOOLS.md`.
 
+## Execution lesson
+- I missed that Telegram was already set up and incorrectly asked setup-style follow-up questions instead of checking current state first.
+- New rule: before suggesting setup/re-setup, first inspect current config, memory, and recent evidence; if already configured, treat it as ops/validation/debugging.
+
 Source: workspace changes + gateway config patch on 2026-03-10.