llm: golden-set eval — precision/recall gate #577
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Quality gate before corpus-wide fan-out.
Scope
stack llm eval)Acceptance
Spec:
docs/superpowers/specs/2026-07-16-llm-module-design.mdStatus audit (2026-08-13, repo-verified): NOT DONE. No golden-set eval harness in src/llm or tests (P35 not started).
Done — merged to main as
48bbc5f(commitsc354047,7000d27,c5e060a, 5b… spec). Results are recorded in the spec's Results section.tests/llm/golden_themes.yaml, 39 CMS-2026-2377 comments hand-labelled from their opening text —expected(must carry) andacceptable(allowed, not required). Smaller than the ~200 across ≥3 dockets the issue asked for; it is one docket and one reader, stated as such.llm.tageval: per-slug tp / fp (outside expected ∪ acceptable) / fn, micro precision/recall/F1, abstain rate;gate()= micro-F1 ≥ 0.70 and no theme with support ≥ 5 under 0.5 precision.stack llm eval-tags [--golden] [--live] [--limit] [--dump]— default scores what the last run stored on the items (no model calls, what CI can run),--livere-tags through the chain,--dumpwrites every shortlist score + verdict for offline sweeps. Exit 1 on gate failure. 18 unit + 2 CLI tests.