Skip to content

worker: an echo that changes a claim is kept as a pending update - #82

Merged
vu1n merged 1 commit into
mainfrom
claude/project-thread-ftmghv
Nov 6, 2026
Merged

vu1n merged 1 commit into
mainfrom
claude/project-thread-ftmghv

Conversation

@vu1n

@vu1n vu1n commented Nov 6, 2026

Copy link
Copy Markdown
Owner

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.
  • Under an accepted survivor, such an echo counts as an update even though promotion bumped the survivor's updated_at (matched on created_at). It promotes like any update, once it recurs (e.g. two other sessions rate it used).
  • A plain copy is still superseded. Recurrence credit is unchanged: the echo itself still counts for nothing.

Verification

  • npm test: 370 pass; new test in test/confirm.test.ts walks copy dropped → change kept → original confirmed and accepted with the change pending → two used ratings promote the change. Dropping either half of the rule fails it.
  • npm run typecheck clean; featuremap.py check 0 broken pointers.

Merging deploys to kypp.vu1n.dev.


Generated by Claude Code

@vu1n vu1n self-assigned this Nov 6, 2026
@vu1n
vu1n merged commit a0be82a into main Nov 6, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant