Document the no-loop / opt-out behavior (README + site FAQ)#14
Merged
Conversation
Explains what happens when no loop covers a task (pass-through by default, ask under --strict, ask inside a matched loop, exit 2 from `docket match`) and how to keep docket out of something (it never executes; engagement is opt-in per surface). README gets a "When there's no loop" section; the docs site FAQ gets two entries. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Uc3rGARtDBoXkqMFgppaP4
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Writes down what docket does when no loop covers a task, and how to keep docket out of something — the questions a new user asks right after install.
README gains a "When there's no loop — or you want docket to stay out" section with a by-surface table:
--strictdocket matchDocs site FAQ gains two entries: "What happens when no loop covers the task?" and "How do I keep docket out of something?"
The through-line: retrieval fails open to the human, the warrant fails closed; docket never executes, so engagement is opt-in per surface. Docs-only; 118 tests green.
🤖 Generated with Claude Code
Generated by Claude Code