fix(intake): deterministic quarantine in the gold harness + Jev gold-set baseline #15
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/jev-gold-shortcircuit-and-baseline"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Two related changes to the content-intake Jev gold benchmark.
scripts/jev-classify.py goldcomputed the deterministic safety verdict withrun_pre_safety_filter()but called Jev first, so a secret-bearing candidate (gold-08) was refused by the shared evaluator's secret scan and raised instead of emitting the verdict the filter had already decided. It now short-circuitsaction_override == "quarantine"toreject+quarantinewith no model call. Non-quarantine overrides (requires_redaction) still reach Jev unchanged.content-intake/jev-gold-baseline/.Results (three runs per phase)
gold-07(archivevs referenceaccept),gold-09(accept_with_editsvs referencereject). Both are action judgment; site routing is correct.gold-08now scores correctly (deterministicreject+quarantine) instead of erroring.Gates
python3 scripts/check-site-boundaries.py— PASSpython3 scripts/verify-links.py— PASSsh scripts/check-secrets.sh— cleansh scripts/run-tests.sh— 31 tests OK (1 skipped)python3 -m py_compile scripts/jev-classify.py— OKCaveats
umbrella-pilot/REVIEW.md).jev-latest, 1 attempt per call, callerpi-gold-benchmark. Cost not returned by the gateway.Policy note for the operator
AGENTS.mdstates generated evidence belongs under the ignoredreports/directory and that generated reports must not be written into trackedcontent-intake/paths. This PR trackscontent-intake/jev-gold-baseline/to match the existing tracked Jev evidence directories (recon-path-consistency/,classify-wiki-fix/). Flagging the tension so the operator can reconcile the rule with current practice.