feat(cognition): forage-before-you-guess — make the working web hand a HABIT, not just an available tool#1944
Merged
Merged
Conversation
…a HABIT, not just an available tool The web tools now return real results (PR #1943), but a working tool she never reaches for is worthless. Her acting doctrine (`ACTING_BLOCK`) told her to write/run/read — but said nothing about the web, so she'd guess a library's API from a stale training memory instead of looking it up. That's exactly how a local model loses to a real dev workflow. Fix: one sentence in the acting doctrine — when she hits a library, API, error, or fact she's unsure of, SEARCH (`web/search`) and READ (`web/fetch`) the way a developer actually works; her training has a cutoff, the web doesn't; foraging then writing from what she found beats confidently shipping something wrong. Doctrine/PX, not output-steering — it names when the hand is for, same voice as the rest of the block. This is the edge canned agents don't have on real projects: she learns the current tool instead of hallucinating last year's API. [[active-acquisition-foraging]] [[px-persona-experience-tools-as-good-ux]] Co-Authored-By: Claude Opus 4.8 <[email protected]> Claude-Session: https://claude.ai/code/session_01LoTjvf5j3Ez13g6k8mRkFo
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 web tools now return real results (PR #1943), but a working tool she never reaches for is worthless. Her
acting doctrine (
ACTING_BLOCK) told her to write/run/read — but said nothing about the web, so she'd guess alibrary's API from a stale training memory instead of looking it up. That's exactly how a local model loses to
a real dev workflow.
Fix: one sentence in the acting doctrine — when she hits a library, API, error, or fact she's unsure of, SEARCH
(
web/search) and READ (web/fetch) the way a developer actually works; her training has a cutoff, the webdoesn't; foraging then writing from what she found beats confidently shipping something wrong. Doctrine/PX, not
output-steering — it names when the hand is for, same voice as the rest of the block.
This is the edge canned agents don't have on real projects: she learns the current tool instead of hallucinating
last year's API. [[active-acquisition-foraging]] [[px-persona-experience-tools-as-good-ux]]
Co-Authored-By: Claude Opus 4.8 [email protected]
Claude-Session: https://claude.ai/code/session_01LoTjvf5j3Ez13g6k8mRkFo