Hardened the optional LLM extraction path
This commit is contained in:
parent
1881daea32
commit
cdaeefd4b2
3 changed files with 44 additions and 1 deletions
|
|
@ -126,6 +126,8 @@ Application code can inject an `LLMCandidateExtractor` into `RegistryService`.
|
|||
When an extractor is present and returns candidates, analysis stores those
|
||||
reviewable candidates; when it returns no candidates, the deterministic
|
||||
heuristic generator remains the fallback.
|
||||
If extraction fails, the failure is recorded as a review decision and analysis
|
||||
continues with deterministic candidates.
|
||||
|
||||
The FastAPI settings object also accepts `llm_provider` and `llm_model`. By
|
||||
default `llm_provider` is unset, so analysis is fully offline and deterministic.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue