From 354aba338467c489bb65683ee726b60253bd8339 Mon Sep 17 00:00:00 2001 From: fredericrous Date: Wed, 7 Oct 2026 19:07:16 +0200 Subject: [PATCH] docs(claude): route via relais in any repo relais sets up an unconfigured repository itself on the first run (its onboard and trust tools ask the person), so the routing rule no longer waits for relais.toml and a grant. The contract comes from the plan or the request, never from questions to the person. Co-Authored-By: Claude Opus 5.5 --- dot_claude/CLAUDE.md.tmpl | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/dot_claude/CLAUDE.md.tmpl b/dot_claude/CLAUDE.md.tmpl index 0ae6feb..1843995 100644 --- a/dot_claude/CLAUDE.md.tmpl +++ b/dot_claude/CLAUDE.md.tmpl @@ -295,13 +295,16 @@ only the person may overrule a `rework`. ## Relais routing -In a repo with `relais.toml` and a trust grant, route bounded -implementation and inspection tasks through relais (the plugin's -`/relais` skill) without being asked: one objective, a write scope, and -acceptance a command can verify. Keep design, multi-repo, ops and -exploratory work in the session, and say in one line which path a task -took. `needs_decision` is the person's call unless the request already -answers it. +Route bounded implementation and inspection tasks through relais (the +plugin's `relais` skill) without being asked, in any repository: one +objective, a write scope, and acceptance a command can verify. Write the +contract from the approved plan or the request; never ask the person for +its fields. A repository that is not set up yet is set up by relais itself +on that first run: its onboard and trust tools ask the person, and a +*Not now* means doing the task in the session. Keep design, multi-repo, +ops and exploratory work in the session, and say in one line which path a +task took. `needs_decision` is the person's call unless the request +already answers it. ## Security