Repository navigation
Preserve complete memories with aggregate budgets - #422
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A complete 520-character memory was rejected after the earlier 240-to-512 change, and extraction silently discarded candidates beyond the first three. Preserve complete claims and original provenance while controlling work through aggregate budgets.
Remove note and structured-text character gates and candidate-count truncation. Keep previews explicitly separate from full reads. Add one request ingestion budget, explicit deferred outcomes, contiguous original-span selection, and whole-response evidence budgets that omit complete entries with visible gaps. Reuse the existing PostgreSQL, outbox, child chunks, and Qdrant design.
Existing installations must update the documented configuration keys and explicitly activate built-in extraction profile 8 if they have a pinned older profile. The shared reader contract is v6. No database migration or original rewrite is required.
Validation:
See the decision, migration instructions, and the report and public verifier. Private originals, full provider payloads, and answers are excluded from the public bundle.