magardeyash/minorproject

1. Overall shape

VentureLens is a Next.js 15 App Router application built around three user roles: Founder, Employee/Contributor, and Admin. The app is organized into route groups and dashboards rather than a single generic UI, so the architecture is primarily role-segmented.

2. Public and authentication boundary

The public entry points are the landing page and the auth flows under app/(auth). Separate login/register pages exist for founder, employee, and admin, backed by shared auth UI components in components/auth. This keeps unauthenticated access isolated from dashboard functionality.

3. Role-based application shells

Each major area has its own layout: app/dashboard/founder, app/dashboard/employee, and app/admin/dashboard. These layouts likely provide navigation, access control, and shared shell chrome through components like DashboardShell and Sidebar. The result is a clean boundary between presentation shell and role-specific content pages.

4. Core business domains

The repo centers on three domain objects:

- Ideas: startup concepts submitted and managed by founders

- Applications: contributors applying to ideas and founders reviewing applicants

- Users/Roles: identity, role assignment, and profile data

These are reflected in lib/db/ideas.ts, lib/db/applications.ts, lib/db/users.ts, and lib/db/roles.ts, plus server actions in actions/*.ts.

5. Mutation layer: Server Actions

The actions/ directory is the main write path for the app. It contains role-specific mutations for auth, ideas, applications, profiles, nav state, roles, and admin operations. This suggests most create/update flows are handled through server actions rather than client-side API calls, keeping form submissions and validation close to the server.

6. Read/API layer

The app/api/ routes are reserved for infrastructure and async services rather than ordinary CRUD pages:

- api/auth/[...nextauth] for NextAuth

- api/ai/evaluate and api/ai/team-suggestions for AI-powered scoring/suggestions

- api/db/init, api/db/migrate, api/db/seed-admin for database setup and admin bootstrapping

This separates operational endpoints from the user-facing dashboards.

7. AI subsystem

The AI layer is isolated in lib/ai/evaluate.ts and exposed through API routes. The UI includes EvaluationReport, ScoreBreakdownChart, and VentureScoreGauge, which indicates the app computes and displays venture viability / team-fit scores for ideas. AI output appears to support founder decision-making and possibly team building.

8. Data access and persistence

lib/db.ts and the domain-specific DB modules form the data access boundary to a Neon PostgreSQL database. The presence of migration and seed routes plus scripts/migrate.mjs implies the app manages schema lifecycle programmatically. This means the architecture has a distinct persistence layer, not just ad hoc queries from components.

9. Authentication and authorization

Authentication is handled by NextAuth.js v5, configured via auth.ts and auth.config.ts, with TypeScript augmentation in next-auth.d.ts. Authorization is enforced through lib/auth/guards.ts and middleware.ts, which likely prevent cross-role dashboard access and gate protected routes. This is a major architectural boundary: identity is centralized, but access is role-specific.

10. Dashboard feature areas

- Founder dashboard: create/edit ideas, view applicants, build teams, inspect scores, manage profile

- Employee dashboard: browse ideas, apply, track applications, manage profile

- Admin dashboard: moderate ideas, manage users, inspect platform state

Shared UI components in components/dashboard power tables, forms, badges, cards, and evaluation visuals across these workflows.

11. Shared UI and composition

components/ui, components/landing, and components/dashboard indicate a layered component strategy: reusable low-level inputs, marketing pages, and role-specific app widgets. This reduces duplication while keeping domain UIs separate from common primitives.

12. Operational and deployment concerns

The project is configured for Vercel deployment and uses standard Next.js tooling plus Tailwind CSS, PostCSS, and TypeScript. Database initialization is exposed as a route, so the app’s runtime depends on environment-provided DATABASE_URL and AUTH_SECRET, with setup partially automated through routes and scripts.

13. What an architecture diagram should emphasize

The key diagram boundaries are:

- Public site vs authenticated dashboards

- Role-based dashboards vs shared UI

- Server actions for mutations vs API routes for auth/AI/ops

- Application logic vs DB access layer

- AuthN/AuthZ layer guarding all protected routes

- AI scoring subsystem feeding founder-facing decision UIs