Fix grounded assistant cross-domain responses
This commit is contained in:
@@ -1,3 +1,29 @@
|
||||
## Sprint 215 Grounded assistant cross-domain reliability (2026-07-16)
|
||||
|
||||
Changed:
|
||||
- Measured the exact live Mol assistant context at 12 current themes, 36
|
||||
semantic metrics, six temporal series and 17,302 compact JSON characters.
|
||||
- Increased the bounded output allowance to 1,200 tokens and instructed the
|
||||
local model to cover every explicitly listed theme, omit unrelated themes
|
||||
and avoid repeated limitations.
|
||||
- Kept `think=false`, deterministic temperature, the 16,384-token context and
|
||||
fail-closed rejection of `done_reason=length` unchanged.
|
||||
- Added the output limit to the editable Unraid template and aligned all
|
||||
deployment defaults and documentation.
|
||||
|
||||
Validation evidence:
|
||||
- A read-only live production-chain probe with the 1,200-token setting
|
||||
completed without truncation against the full persisted Mol context.
|
||||
- The focused assistant suite passed 14 tests.
|
||||
- The complete readiness gate passed 713 backend tests, backend compilation,
|
||||
105 documented API routes with three explicit binary/non-envelope routes,
|
||||
one Alembic head and the frontend TypeScript and production build.
|
||||
- Tower deployment and browser verification follow in this pass.
|
||||
|
||||
Next:
|
||||
- Deploy, rerun the exact six-theme Dutch question and verify the end-user
|
||||
response and responsive assistant UI in the browser.
|
||||
|
||||
## Sprint 213-214 Cross-domain thematic rasters and DOV soil map (2026-07-16)
|
||||
|
||||
Changed:
|
||||
|
||||
Reference in New Issue
Block a user