Repository navigation
Accept risk-control body output against body and record contracts - #50
Closed
lanyue-llk wants to merge 2 commits into
Closed
lanyue-llk wants to merge 2 commits into
lanyue-llk wants to merge 2 commits into
Conversation
Contributor
Author
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.
Risk-control body extraction currently fails when registered navigation, login or footer text is missing, even when the independent body and record requirements are satisfied. The compiler now marks stable text as diagnostic for the 97 cases with body or composite contracts; the three anchor-only cases retain mandatory text.
The shared scorer supports an explicit
stable_text_roleon body-text contracts and rejects a diagnostic role without a body or composite gate. Anchor matches and misses remain inspectable. Record counts, same-record fields, real links, blocked pages, forbidden content and body sufficiency remain required. Existing contracts without the role retain their behavior, including historical heading requirements. English guidance follows the corrected scope. Historical profiles, certificates, calls and published scores remain unchanged.Validation: 241 tests and 654 regression subtests pass. Positive and negative controls cover full body without page-shell text, incomplete body, complete and incomplete records, placeholder links, request failure, joint body/record requirements, identity, blocked pages, minimum length, anchor-only fallback and the compiler policy across all 100 frozen cases. The original main scorer reproduces the body/list false rejections before the fix.
Offline impact: all 2,782 retained response artifacts were hash-verified. For the matched-version comparison, the scorer at
4b91f6bc8ef9d27e8d7824d6ea0c66cb3ee292a1matches the saved scoring-source hash exactly; baseline recalculation reproduces all saved risk-control verdicts. Only this policy changes in the after calculation. Other task families retain their saved metrics.The separate Moli 1.1.16 retained subset changes from 73/202 to 99/202; its risk-control portion changes from 21/72 to 47/72. All 26 flips satisfy the independently recalculated body/record contracts and fail solely on stable anchors before the correction. These are subset results, not a new full-cohort score.
Current main has older extraction rules than the retained scorer. A separate main-based analysis yields nine six-method flips and one subset flip, with 28 and 17 pre-existing baseline verdict differences respectively. These differences are kept separate from the matched-version policy impact above.
Paired regression IDs, independent contract authorities, input/output hashes, exact changed attempts and reproducible policy patch are bound by
research/risk-control-body-scope-revision.json; generated evidence stays outside Git. No browser implementation changes or provider calls.