Behavision

Files

Suriyakumarvijayanayagam 3598d8e9c0 The shop PC's avatar had the same V1 collision

Fixed on the web arrivals feed and not here, which is the failure this
codebase already warns about: two surfaces disagreeing about one fact.
Taking the first letter of each word of "Visitor 13" gives "V1" - and so
do "Visitor 10" and "Visitor 15", so three different customers wear the
same badge and it reads as the V-1 reference for a fourth.

Shows the number itself, same rule as the web app. customerRef, not
ref: React reserves that prop name and it would never arrive.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HViLj9gYNRtSr7YVZmW5sn

2026-09-07 12:45:38 +05:30

dist

The shop PC's avatar had the same V1 collision

2026-09-07 12:45:38 +05:30

src

The shop PC's avatar had the same V1 collision

2026-09-07 12:45:38 +05:30

index.html

Behavision: face recognition for retail, edge to head office

2026-09-04 11:14:18 +05:30

package-lock.json

Behavision: face recognition for retail, edge to head office