The eval harness (.github/workflows/eval-harness.yml) runs automatically on PRs
that touch scoring / generation logic or the gold sets (see the Delta 3 path
filter in that workflow). Most PRs do not affect eval metrics — leave this
section as "No eval impact." if that applies.
If your change alters ranking / scoring / generation behavior and moves a gold-set metric:
Affected metric: <task>.<class>.<metric>
e.g. Affected metric: citation_extraction.aggregate.accuracy
(use class aggregate for the headline metric; otherwise the per-class name).
If a metric regresses (polarity-corrected signed_lift < -0.05, or any
zero-baseline metric changes), the gate blocks unless you add BOTH:
the acknowledgement token (on its own line):
[eval-regression-acknowledged] — for the CI deterministic gate, and/or[ranking-regression-acknowledged] — for scripts/check_ranking_lift.pyhttps://github.com/Imbad0202/academic-research-skills/issues/NNNNo eval impact.
If this PR adds a new <platform>/ directory, read the
Platform ports policy
and open a design issue first. Otherwise, leave this section as "Not a platform port."
Not a platform port.