Entity resolution via HydraMem pack: aliases and provenance, no embedding merges #9
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#29 Slice 3 — rules before models
Ting/CurryComb
Reference
Ting/CurryComb#9
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Requirement scenario
GIVEN a fixture naming
jostoph-rsandJostophunder 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.Entity resolution via HydraMem pack: aliases and provenance, no embedding merges
State:
open· Labels: Kind/Feature · Comments: 0Rendered by CurryComb slice 1 projection v1. The body will be replaced by rule-derived content in Slice 3.