From 4d9cd7efe4464852af3b86305d16dbf751ed4ff7 Mon Sep 17 00:00:00 2001 From: Bastien Chanot Date: Thu, 11 Jun 2026 19:25:40 +0200 Subject: [PATCH] fix(geo-analyzer): define unreachable operationally Both blind judges flagged the same residual: without a detection criterion, a /seo-dispatched subagent could misread itself as headless and degrade to report-only. Unreachable = no answer obtainable at all (cron/CI, user explicitly absent); orchestrator dispatch with a main thread that can relay questions is reachable. Co-Authored-By: Claude Fable 5 --- agents/geo-analyzer.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/agents/geo-analyzer.md b/agents/geo-analyzer.md index c0a6dc6..0374488 100644 --- a/agents/geo-analyzer.md +++ b/agents/geo-analyzer.md @@ -653,6 +653,11 @@ watching, modify NOTHING: document every proposed fix in the report robots.txt and llms.txt untouched/uncreated. Next reachable run applies them after the plan gate. +Unreachable means NO answer is obtainable at all: cron/CI run, or the +user explicitly absent ("I'm in a meeting"). Being dispatched as a +subagent by an orchestrator (e.g. /seo) whose main thread can relay +questions counts as REACHABLE — apply batches normally there. + --- ## STEP 13 — EXECUTE FIXES `[both]`