bchanot/claude
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(geo-analyzer): define unreachable operationally

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
Bastien Chanot 2026-06-11 19:25:40 +02:00
parent 225c4377da
commit 4d9cd7efe4
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
agents/geo-analyzer.md
View File

@ -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 robots.txt and llms.txt untouched/uncreated. Next reachable run applies
them after the plan gate. 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]` ## STEP 13 — EXECUTE FIXES `[both]`