2026-10-06 | O9X associate-attendance V1 architecture. Desired user flow remains intentionally simple: mobile number plus last four Aadhaar digits for initial login, selfie match against stored picture, one-device binding, and server-side GPS/geofence check-in on ordinary Android/iPhone browsers. Architectural direction: keep this as a separate lightweight Cloudflare attendance/identity service so the main ERP stays simpler; Supabase remains the master employee source, minimal associate data syncs to the service, existing R2 photos are reused, and attendance flows back to O9X through an API. Face matching is 1:1 verification, not broad identification; liveness is a separate control; embeddings are model-specific/versioned data. Further refinement: Aadhaar-derived data is a weak routine authenticator and should be treated mainly as onboarding/recovery context, while ongoing trust should come from possession/device binding, biometric verification and location.