Skip to content

Add three-way critic closing line (keep finding labels) - #1

Open
shagghiesuperstar wants to merge 1 commit into
Da7-Tech:mainfrom
shagghiesuperstar:feat/critic-three-way-verdict
Open

Add three-way critic closing line (keep finding labels)#1
shagghiesuperstar wants to merge 1 commit into
Da7-Tech:mainfrom
shagghiesuperstar:feat/critic-three-way-verdict

Conversation

@shagghiesuperstar

Copy link
Copy Markdown

What this changes
Adds a required three-way closing line on the critic report (AGREE | DISAGREE_EVIDENCE | DISAGREE_CONCERN) without replacing the existing per-dispute finding labels (confirmed, refuted-with-evidence, unresolved, duplicate, out-of-scope).

Why
A critic that only triages findings can still rubber-stamp a thin review or cave to a citation-free rebuttal (false consensus). The three-way close is the review-audit contract from arXiv:2608.18167 section 4.4. Finding labels stay for each dispute.

Checks

  • python3 -B -m scripts.check_package passes
  • python3 -B -m unittest discover -s tests passes (122 tests)
  • Skill text change: F07 assertion and SF-21 mapping updated
  • No new files; review/inventory.json unchanged
  • No personal names, contact details, local paths, credentials, or transcripts

Notes for the reviewer
This is instruction text plus a package test that the tokens exist. It is not a measured F1 claim on the SureForge eval kit. Version left at 1.0.0 for the maintainer to bump.

The critic still classifies each dispute with confirmed / refuted-with-evidence / unresolved / duplicate / out-of-scope. The report must then end with exactly one of AGREE, DISAGREE_EVIDENCE, or DISAGREE_CONCERN so a citation-free rubber-stamp cannot pass as a complete critic pass. Source: arXiv:2608.18167 section 4.4.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant