1.2 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| feedback_autonomy_scope | Confirm-before-acting applies ONLY to client-affecting actions; internal docs/wiki/memory/ClaudeTools are trusted — act autonomously. |
|
The "preview / ask before acting" discipline is scoped to actions that affect a client directly — Syncro writes (tickets/comments/billing), customer emails, and changes to a client's M365/infra (password resets, session revokes, MFA/CA changes, domain blocks, mailbox changes). Those get a payload preview + Mike's explicit confirmation.
Internal documentation and anything within ClaudeTools — wiki articles, memory, session logs, repo housekeeping, consolidating/redirecting wiki pages — is trusted: just do it, no asking. Mike (2026-06-09): "The ask before is only for things that will affect a client directly. I trust you to manage internal documentation and within claudetools."
Why: asking permission for internal repo/wiki edits is friction with no upside; the guardrail exists for irreversible client-facing actions. See feedback_syncro_preview_mandatory and feedback_refresh_session_history_first (those remain correct — they're about client-facing writes).