Repository navigation
fix(dream): refine runs the rewrite guard; cluster joins at 0.75; abstractions get real names (1.11.0) - #145
Merged
Merged
Conversation
…tractions get real names (1.11.0) An attended dream on 1.10.0 passed the signature gate while refine did two damaging rewrites (#85): a paper summary that joined an unrelated memory at 0.712 was appended to it and the memory lost its subject ("Virgil's memoir-agent idea"), and another memory lost "(v0.8.1)". Only hindsight ran checkRewrite, and the number check missed version strings. Refine now runs the guard with a growth limit. The guard also refuses dropped named entities and a lost opening subject, and compares entities by whole word, case-insensitively. Cluster's join floor rises to 0.75 (the legitimate join in that run scored 0.797), configurable per namespace. An abstraction with no label line is named by deriveName instead of its first clause cut short. Measured on a copy of the same store with this build: the paper became its own memory, the version-dropping rewrite was declined, 0 damaged rows, 0 belief rows to audit, abstraction names are concept labels. Refs #85 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Why
#85. In an attended dream on 1.10.0, the signature gate reported clean while refine made two damaging rewrites:
Only hindsight called
checkRewrite. Its number check also missed version strings, because\bsees no boundary betweenvand0.What
checkRewritewith a newlimitGrowthoption: a definition that grows past max(1.4×, +300 chars) is declined. Declined rewrites keep the old definition, write no belief row, and are counted inphases.refine.declined.cluster_threshold.dreamand auto-consolidation now pass it through. A wrong join hands refine unrelated text; a missed join only mints a separate memory.deriveName, the way create names memories, instead of clipping its first clause.dreamConsolidatenow reportsphases.hindsight.declined. It was counted but left out of the result.Verification
Not in this PR
Both are filed separately.
Closes #85
🤖 Generated with Claude Code