Repository navigation
worker: an echo that changes a claim is kept as a pending update - #82
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.
Requested by Vu · project thread
Follow-up to #80. An echo (a re-claim of a subject the session was shown) that ranked below the original was superseded, so its correction was lost; in production several echoes were longer, corrected versions.
Contract
planGroup: an unstamped candidate, same authority, written after the survivor, whose content differs (whitespace aside), is a pending update (echoUpdate). It's kept, not superseded, in a candidate group and through the survivor's promotion.updated_at(matched oncreated_at). It promotes like any update, once it recurs (e.g. two other sessions rate itused).Verification
npm test: 370 pass; new test intest/confirm.test.tswalks copy dropped → change kept → original confirmed and accepted with the change pending → twousedratings promote the change. Dropping either half of the rule fails it.npm run typecheckclean;featuremap.py check0 broken pointers.Merging deploys to kypp.vu1n.dev.
Generated by Claude Code