Skip to content

fix(federation): normalize vector clocks and tighten promotion scoring#130

Merged
Fail-Safe merged 1 commit into
nextfrom
normalize-vclock-promotion-scoring
Jun 17, 2026
Merged

fix(federation): normalize vector clocks and tighten promotion scoring#130
Fail-Safe merged 1 commit into
nextfrom
normalize-vclock-promotion-scoring

Conversation

@Fail-Safe

Copy link
Copy Markdown
Owner

Summary

  • Normalize live vector clocks so legacy display-name buckets are pruned from current federation state, event emission, merge, and conflict comparison paths.
  • Tighten short-to-mid consolidation scoring so one-source provenance traces do not promote from passive search hits alone.
  • Add regression coverage for legacy vector-clock cleanup and one-source promotion scoring.

Root Cause

Older federation state could carry pre-cortex-ID vector-clock buckets keyed by display names. Those buckets were inert but kept propagating through merges and status output. Separately, one-source session-summary-shaped traces could still cross the short-to-mid threshold through passive search-hit activity even though single-source lineage credit was already gated off.

Validation

  • go build ./...
  • go test ./...
  • go vet ./...
  • go test -race ./...
  • Hermes MCP smoke test: list, create, recall, and search all passed in a test cortex.

@Fail-Safe Fail-Safe marked this pull request as ready for review June 17, 2026 18:55
@Fail-Safe Fail-Safe merged commit fc74e2c into next Jun 17, 2026
1 check 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