revert(search): restore baseline answer prompt (commit-policy regressed) - #72
Merged
Conversation
The commit-policy prompt (#71) was benchmarked and NET-REGRESSED: on the 50-q SimpleQA+FRAMES sample, overall accuracy fell 64%->48% and INCORRECT exploded 2->17 — forcing commits made the model confidently wrong on multi-hop chains and weak retrieval, destroying the near-zero-hallucination property that was crw's strongest asset. Reverting to the baseline prompt. The real accuracy lever is retrieval recall (get the right source into context), not prompt-forced commits — pursued next.
There was a problem hiding this comment.
Pull request overview
Reverts the /v1/search answer synthesis system prompt in crw-extract back to the pre-#71 “baseline” wording after benchmarking showed the commit-policy prompt increased confident-wrong answers and reduced overall accuracy.
Changes:
- Removes the “COMMIT to a specific answer” commit-policy instructions from the answer system prompt.
- Restores baseline guidance: abstain when sources don’t cover the query and write a neutral prose answer.
Comments suppressed due to low confidence (1)
crates/crw-extract/src/answer.rs:37
- The prompt rules still instruct the model to call a
cite_sourcestool, but this implementation actually requires the model to append an===CITATIONS===JSON block (see theaugmented_promptinstructions andparse_answer_and_citationssplitting on===CITATIONS===). Keeping tool-call wording here creates contradictory instructions within the same system prompt and can increase malformed outputs / citation parse failures. Consider updating this section to describe the===CITATIONS===block instead of a tool call.
- Write a direct, neutral answer in 3–6 sentences of plain prose.
- After producing the answer, you MUST call the `cite_sources` tool to
report which sources you used. Each citation gives a `source_id` (the
integer index of the source) and a `position` (a hint for ordering;
use the position the source had in the input list).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Benchmarked #71's commit-policy prompt on the 50-q SimpleQA+FRAMES sample: NET REGRESSION — overall 64%→48%, INCORRECT 2→17 (forcing commits caused confident-wrong on multi-hop + weak retrieval, destroying crw's near-zero-hallucination property). Revert to baseline. Real lever is retrieval recall, not prompt-forced commits.