cyuvarajsamynath-max/gridshare-

Purpose and Runtime Shape

GridShare is a Vite-built React single-page application for household/grid energy sharing and demand/anomaly experiences. The delivered repository contains the frontend plus a root Node server, but no backend/ Python service described in the README; any prediction API is therefore an external/deployment-time dependency rather than an included service.

Key runtime entry points: index.html, main.jsx, and server.js.

Frontend Bootstrap and Navigation

main.jsx mounts the React application into the HTML root and is the browser-side entry point. App.jsx is the application shell and likely owns route/page selection, while SPA fallback is supported for deployment by _redirects and vercel.json.

Primary boundary: browser navigation and UI state remain client-side; direct deep-link handling must be provided by static-host routing configuration.

Paths: main.jsx, App.jsx, index.html, _redirects, vercel.json.

User and Household Setup Flow

The product-facing flow is organized around authentication, household configuration, and a user dashboard. Login.jsx represents the access boundary, HouseSetup.jsx captures household context, and UserDashboard.jsx presents the operational energy-sharing view.

These components appear to form the core user journey: authenticate → define household/setup data → inspect or act through the dashboard. No persistence layer or identity provider is visible in the tree, so their backing data/control contracts need validation before extending them.

Paths: Login.jsx, HouseSetup.jsx, UserDashboard.jsx.

AI Anomaly/Prediction Feature

AI-related frontend behavior is split between presentation and decision logic. AIAnomalyDrawer.jsx provides the user-facing anomaly surface, while aiAnomalyEngine.js contains the corresponding computation/integration logic. config.js is the likely boundary for API URLs or feature settings.

Per the README, demand prediction should call a separately deployed Python REST API, configured through Vite environment variables such as VITE_PREDICTION_API_URL. That Python backend, model artifacts, and API schema are not present in this checkout. Treat calls from aiAnomalyEngine.js as an external-service boundary requiring error/loading handling and a stable request/response contract.

Paths: AIAnomalyDrawer.jsx, aiAnomalyEngine.js, config.js, .env.

Server and Deployment Boundary

server.js is the only included server-side executable and should be treated as the repository’s actual local/server runtime until inspected; it may serve built assets, proxy APIs, or provide application endpoints. The static SPA build/deployment path is also explicitly represented by Vercel configuration and redirect rules.

Production architecture is therefore likely: static Vite frontend on Vercel-compatible hosting, optionally a Node server, and a separately hosted prediction API. Do not assume the README’s Flask/FastAPI backend is deployable from this repository.

Paths: server.js, vercel.json, _redirects, vite.config.js.

Build and Styling Layer

Vite compiles the React frontend; the main global styling surfaces are index.css and App.css. The repository also includes generated-looking bundled assets (index-KwIaR4oR.js, index-CckidJvJ.css), which should not be treated as source architecture unless they are intentionally served directly.

Paths: vite.config.js, index.css, App.css, package.json.