Entity resolution via HydraMem pack: aliases and provenance, no embedding merges #9

Open
opened 2026-09-02 07:53:48 +00:00 by larandar · 1 comment
Owner

Proposal

Resolve repository, component, campaign, person, service, policy, and deliverable identities through HydraMem; preserve aliases and provenance. Entities never merge merely because embeddings rank them close (docs/handoff.md §Fact pipeline 2).

Design

Resolution is an entity/alias lookup with bounded graph neighborhood; misses become typed missing-predicate facts (consumed by #8), not guesses.

Tasks

  • alias-aware resolver over #2 packs
  • unresolved identity → typed predicate-miss fact

Requirement scenario

GIVEN a fixture naming jostoph-rs and Jostoph under one known alias set, WHEN resolution runs, THEN both land on the same entity id with provenance; an unknown name yields a miss fact, never a nearest-neighbor merge.

## Proposal Resolve repository, component, campaign, person, service, policy, and deliverable identities through HydraMem; preserve aliases and provenance. Entities never merge merely because embeddings rank them close (`docs/handoff.md` §Fact pipeline 2). ## Design Resolution is an entity/alias lookup with bounded graph neighborhood; misses become typed missing-predicate facts (consumed by #8), not guesses. ## Tasks - [ ] alias-aware resolver over #2 packs - [ ] unresolved identity → typed predicate-miss fact ## Requirement scenario GIVEN a fixture naming `jostoph-rs` and `Jostoph` under one known alias set, WHEN resolution runs, THEN both land on the same entity id with provenance; an unknown name yields a miss fact, never a nearest-neighbor merge.
Author
Owner

Entity resolution via HydraMem pack: aliases and provenance, no embedding merges

State: open · Labels: Kind/Feature · Comments: 0

Rendered by CurryComb slice 1 projection v1. The body will be replaced by rule-derived content in Slice 3.

<!-- currycomb:refinement:v1 repo=Ting/CurryComb issue=9 --> # Entity resolution via HydraMem pack: aliases and provenance, no embedding merges State: `open` · Labels: Kind/Feature · Comments: 0 _Rendered by CurryComb slice 1 projection v1. The body will be replaced by rule-derived content in Slice 3._
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
Ting/CurryComb#9
No description provided.