devi-sivakumar-ds/finsight

Purpose and entry points

FinSight is an Expo/React Native research prototype for accessible, voice-first mock check deposits. The participant app starts at App.tsx, which mounts navigation in src/navigation/AppNavigator.tsx. Its companion operator system is a browser dashboard served by wizard-dashboard/server.js, with UI assets in wizard-dashboard/public/.

Study-mode control boundary

The app is explicitly configured for research-stage Wizard of Oz control in src/config/studyMode.ts. In this mode, the mobile client owns rendering, speech, feedback, navigation, and local deposit state; a human operator decides ambiguous conversational, capture, OCR, and confirmation outcomes. This separates interaction evaluation from unreliable autonomous perception or language decisions.

Mobile deposit workflow

The principal task is a staged navigation flow: home/onboarding, deposit overview and privacy, account selection, check preparation/capture, OCR review, amount entry, confirmation, then success or recovery. The deposit-specific navigator is src/navigation/DepositNavigator.tsx; representative stateful stages are src/screens/CheckCaptureScreen.tsx, src/screens/OCRProcessingScreen.tsx, and src/screens/ConfirmationScreen.tsx. src/screens/ErrorScreen.tsx provides a recovery boundary rather than silently failing.

Wizard command and synchronization loop

The app-side WebSocket client in src/services/wizardClient.ts connects to the relay and exchanges structured session, state, and event messages. src/services/wizardExecutor.ts maps received operator commands into app actions, while src/services/wizardState.ts maintains the reportable session/deposit snapshot. Shared protocol/state contracts live in src/types/wizard.ts and command definitions in src/utils/wizardCommands.ts. This continuous app-to-dashboard state reporting is the main anti-drift mechanism.

Operator dashboard and relay infrastructure

wizard-dashboard/server.js hosts the dashboard, relays WebSocket traffic between operator and app clients, and persists local session logs. The operator-facing dashboard is a lightweight browser application rooted at wizard-dashboard/public/index.html with behavior in wizard-dashboard/public/app.js. The mobile app therefore requires reachability to the dashboard server; Android USB workflows use scripts/wizard-android-usb.sh to reverse the relevant local ports.

Interaction-feedback services

Voice is a cross-cutting runtime layer: src/contexts/VoiceSettingsContext.tsx provides user settings, and src/hooks/useAlwaysOnVoice.ts / src/hooks/useTTS.ts integrate continuous interaction and spoken output. Service boundaries isolate platform or simulated capabilities: src/services/ttsService.ts, src/services/sttService.ts, and src/services/hapticsService.ts. Capture feedback is similarly encapsulated in src/services/captureSoundService.ts and src/components/VisualMic.tsx.

Autonomous-capability seams and mock domain backend

The codebase retains separable automation seams for future/non-WoZ operation: camera/snapshot guidance in src/services/geometryDetection.ts and src/services/snapshotAnalysis.ts, OCR simulation/extraction in src/services/ocrService.ts, and intent handling in src/services/intentService.ts. Banking actions are intentionally non-production and pass through src/services/mockBankingAPI.ts; account choices are local fixture data in src/data/accountProfiles.ts. No real banking integration is indicated.