feat(claude): the search-first rule applies to agents too, not just to you - #89
Merged
Merged
Conversation
…o you I asked another session three questions. Two were answered in its repository's own docs, and the third I asked in terms its design notes explicitly reject — `broker.md` says outright "this is how an `Unknown` closes without a human", and `state-space.md` argues a structured result, not an exit code plus prose. The rule was already here. I applied it to questions put to Matt and not to questions put to a peer, which is the same waste dressed as collaboration — it costs another agent's time instead of his, and the answer was on disk either way. Also adds: name the files searched. A question that lists where you looked is one he can correct; one that does not is one he has to re-derive. Claude-Session: https://claude.ai/code/session_01VUd2Wv3nkSBpWgYBK6yhfh
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
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.
The Questions section already says "Read the documentation, code, config and git history before asking". I applied it to questions put to Matt and not to questions put to another agent.
What that cost
I asked the dev-tools session three questions for the broker UAT case list. Then, told to search properly, I did:
devtoolargv forms, and which cross the wiredocs/design/devtool-vcs.md— "devtool git commitanddevtool git pushroute to different crates; routing lives in the multiplexer";README.md; andbroker.md's three-call table naming which step is-networkand which-localUnknownbecomes determinatedocs/design/broker.md: "Status — back: the last Decision the ledger recorded against that nonce. This is how anUnknowncloses without a human [measured,dev#522]", plus whypushechoes the noncedocs/problem/state-space.mdargues a structured result, calling exit-code-plus-prose the common convention and Bad. I asked about exit codes; the design's answer is theDecisionTwo I should not have asked. The third inverted itself once I read the note.
Why it matters more between agents, not less
Asking Matt something the docs answer wastes his time, and he notices. Asking a peer agent wastes a session's time and produces a confident answer anyway, so nothing corrects it — the waste is invisible and it reads like collaboration.
The rule
The last line is the cheap one. A question that says where it looked is one you can correct in a sentence; one that does not is one you have to re-derive from scratch.
./tests/test.sh quickpasses.https://claude.ai/code/session_01VUd2Wv3nkSBpWgYBK6yhfh