Sharang ParnerkarandClaude Fable 5
30487e4d8f
CI / Check (push) Skipped
CI / Check (pull_request) Successful in 6m7s
CI / Detect Changes (pull_request) Skipped
CI / Deploy Agent (pull_request) Skipped
CI / Deploy Dashboard (pull_request) Skipped
CI / Deploy Docs (pull_request) Skipped
CI / Deploy MCP (pull_request) Skipped
The scale mechanism for the master-control corpus (which carries no CWE to LUT on): ControlIndex embeds each control's requirement text and returns the top-K nearest to a code region (cosine); SemanticControlChecker retrieves those K, judges each with the grounded judge, and grounds the verdicts -> control_refs. The region->control direction (vs the CWE-LUT's finding->control) is what scales to ~13.6k: the LLM only ever judges a handful of retrieved candidates, and every survivor is still anchored to real code by the grounding gate. Reuses judge + ground gate. Stub-tested (cosine ranking, retrieve->ground, ungrounded dropped). Not yet wired into the scan (needs the master-controls catalog live, breakpilot #129). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>