Repository navigation
fix(docscout): make completeness judgments opt-in per extractor - #79
Merged
Merged
Conversation
added 7 commits
November 11, 2026 01:07
A constrained decoder only admits the verdict strings, but the prompt did not name supported or not_supported, so the model chose among labels it could not see: a replayed batch returned not_supported for every value while each reason said the quote states the value. The prompt now names each verdict and completeness label with its meaning, built from the same constants as the schema.
Merged
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.
Verify adds an opt-in per-field support judgment and completeness judgment for text and list fields.
stages.verify.check_completenessdefaults off. Existing configurations retain the support prompt, schema, model requests, call count, verification outcomes, summaries and persisted results.When enabled, the request includes the full field contract and source passages. Complete, incomplete and unknown remain distinct in current and stored results and in the Test and Runs views. If the enhanced contract or any optional source context cannot fit, or optional source acquisition fails, Verify sends the existing support request for all fields in that call and leaves completeness unknown. The policy adds input tokens without an extra model call.
Validation uses the official v0.3.59a runtime and refreshed dependencies:
Configuration and result fields are optional and additive. Existing data needs no migration. The change preserves the informational field codes and scoped-absence behavior on main.