Handle repetitive Semantic Consolidator output loops
This commit is contained in:
@@ -375,6 +375,22 @@ extraction results into `meeting_protocol.md` for technical validation. The
|
||||
planned architecture separates Canonical Meeting Knowledge from the final Output
|
||||
Views documented in `output-views.md`.
|
||||
|
||||
## Semantic Consolidator failure handling
|
||||
|
||||
Semantic Consolidator V0 preserves every raw model response before parsing.
|
||||
Its normal path accepts parseable grouping JSON and leaves duplicate source-ID
|
||||
and missing-source-ID correction to the existing deterministic coverage
|
||||
repair.
|
||||
|
||||
An invalid or truncated response is not retried by default. One controlled
|
||||
retry is allowed only when deterministic inspection finds at least three
|
||||
consecutive complete groups with an identical structural signature:
|
||||
`canonical_text`, ordered `source_item_ids` and `merge_reason`. The retry keeps
|
||||
the same model, temperature, context window and generation limit and adds only
|
||||
an instruction not to emit an identical group more than once. Both attempts
|
||||
and the detected repetition metadata are preserved. If the retry also fails,
|
||||
the stage fails normally; it does not make another LLM call.
|
||||
|
||||
---
|
||||
|
||||
# Next Milestone
|
||||
|
||||
Reference in New Issue
Block a user