arunkumar30102006/shareholder-voting-platform

Purpose and runtime

Vote India Secure is a Vite/React TypeScript single-page e-voting platform for Indian listed companies. It serves public marketing/compliance pages plus separate company-admin and shareholder voting portals. Browser entry is src/main.tsx; application composition and route registry are src/App.tsx; Vercel is the intended frontend host (vercel.json).

Frontend application shell and routing

src/App.tsx connects routed pages for public, company, shareholder, voting, analytics, and legal experiences. Shared navigation, SEO, error containment, and theme/UI layers are centered in:

• src/components/layout/Navbar.tsx

• src/components/layout/GlobalErrorBoundary.tsx

• src/components/layout/SEO.tsx

Marketing pages are distinct from authenticated workflows, providing a clear public-to-portal boundary:

• src/pages/Index.tsx

• src/pages/CompanyLogin.tsx

• src/pages/ShareholderLogin.tsx

Identity, roles, and tenant isolation

Supabase provides authentication and PostgreSQL persistence. The company-admin route guard enforces portal access before protected admin workflows:

• src/components/auth/ProtectedAdminRoute.tsx

• src/integrations/supabase/client.ts

• supabase/migrations/20260302000000_security_advisor_fixes.sql

Database RLS is a primary security boundary between companies, their administrators, and shareholders. Vote-specific RLS and secured summary behavior are represented by:

• supabase/migrations/20251221125500_fix_votes_rls.sql

• supabase/migrations/20260225141500_secure_vote_summary.sql

Company voting lifecycle

Company users register and authenticate, then manage voting events, resolutions, shareholders, and results through dedicated page-level workflows:

• src/pages/CompanyRegister.tsx

• src/pages/CompanyDashboard.tsx

• src/pages/VotingManagement.tsx

The data model evolves through SQL migrations for sessions, meeting dates, weighted voting, and vote aggregation:

• supabase/migrations/20260121000000_add_meeting_dates.sql

• supabase/migrations/20260328000000_weighted_voting_system.sql

• supabase/migrations/20260224060000_fix_votes_aggregation.sql

Shareholder ballot and audit flow

Shareholders log in, receive/verify OTP credentials, view their active ballot/dashboard, and submit votes through the frontend voting API. The vote path and integrity-oriented utilities are:

• src/pages/VotingDashboard.tsx

• src/components/voting/VotingCard.tsx

• src/services/api/voting.ts

Cryptographic/verification concepts are isolated in client libraries and supporting database optimization scripts:

• src/lib/merkle.ts

• src/lib/blockchain.ts

• supabase/merkle_storage.sql

Email OTP dispatch and validation occur server-side through Supabase Edge Functions, keeping provider secrets outside the browser:

• supabase/functions/send-email-otp/index.ts

• supabase/functions/verify-email-otp/index.ts

• supabase/functions/send-shareholder-otp-email/index.ts

Analytics, feedback, and AI services

Administrative and shareholder reporting use dashboard components; feedback is captured for sentiment analysis:

• src/components/company/AdminVotingResults.tsx

• src/components/dashboard/VotingAnalytics.tsx

• src/components/ai/ShareholderFeedbackForm.tsx

AI requests cross a browser-to-Edge-Function boundary. ai-ops integrates Groq/Gemini-backed summarization, chat, and sentiment capabilities; translation is separately exposed:

• src/components/ai/DocumentSummarizer.tsx

• src/components/ai/VoteAssistant.tsx

• supabase/functions/ai-ops/index.ts

• supabase/functions/translate-text/index.ts

External integrations and operational functions

Supabase Edge Functions are the backend execution layer (Deno), handling AI, transactional email through Resend, contact/feedback delivery, invitations, account deletion, and payment order creation. Cashfree payment UI connects to its server-side order function:

• src/components/payment/CashfreeGateway.tsx

• supabase/functions/create-payment-order/index.ts

• supabase/functions/send-contact-message/index.ts

Localization is client-side i18next, with translation content and a resolution-translation persistence layer:

• src/i18n/config.ts

• src/i18n/locales/en.json

• supabase/migrations/20260304192000_create_resolution_translations.sql