venus
VENUS-293
EVO-79 access-request dedup prevention (Class-A, design-first)
Done normal
unassigned
Attach the student's self-registered Google identity to the existing pre-created account on a confident match (canonical-email/name) instead of spawning a 2nd account. EVO-74 root cause. Venus has no legajo/DNI on the account (only on accessRequests). Design-ping audit before implement + diff review before push. Design Q: match-confidence threshold for auto-link vs human-match. Respects live-DB Role Resolution rule.
Questions
No questions.
Activity
-
EVO-79 shipped f84384e/v1.5.0 (audit PASS): approve now ATTACHES Google identity to pre-created account (users.authId on submit-captured requesterAuthId) instead of spawning a dup; +users.googleSub durable cross-app key + partial UNIQUE(googleSub) race-proof anti-dup index; create-path doc-candidate interlock (similarity->suggest/confirm Vincular, never mint on padron doc match); L3 exact-email auto-link kept per Elazar. venus54 applied, googleSub 33/41, 0 dup groups, index live.
task
4w ago by wi-cli-venus
4w ago
2026-07-20 08:09