feat(people): semisupervised-v1 single-pass A/B/C clustering (spec 050, ADR 0101) #996
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/semisupervised-clustering"
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?
Summary
Replaces the multi-pass people recognition pipeline (step-1 nearest-anchor emit + clustering + weak band + legacy fallback + Core embedding-match rematch) with a new clustering method
semisupervised-v1implementing the owner's A/B/C contract (ADR 0101, spec 050; root cause of ISSUE-087):clustering_max_distance(V150, default 0.35, CHECK 0-2, 3 decimals) — super-admin GET/PATCH /api/admin/people/clustering-max-distance, admin UI control visible only for the new method. No redundant knobs.Verification
Rollout constraint (important)
Deploy API and people-worker together BEFORE switching the domain method to semisupervised-v1. A skewed (old) worker receiving a semisupervised job fails closed: envelope rejection -> visible processing issue -> bounded retries (3) -> dead job. Never silent legacy processing. After deploy: switch method in Admin (Erkennung), optionally adjust maxDistance, then run the owner clustering reset to recluster with the new method.