About the Project

Sejong Pulse is a student-focused platform for Sejong University that blends a campus social feed, discovery and matching, messaging, AI guidance, and operational tooling into a single product surface.

Goal

The product aims to help students connect with people, navigate campus life, ask questions, and participate in real-time campus activity without needing to bounce across several disconnected tools.

Target Audience

Students signing in with their Sejong credentials and using the app for feed, discovery, messaging, and support.
Product engineers building the frontend, backend, and supporting service integrations.
Operators who maintain the Supabase schema, recommendation services, background workers, and deployment environments.

Core Product Areas

Area	Purpose	Primary routes
Authentication and onboarding	Sign in with Sejong credentials, create a profile, and bootstrap a campus identity	`/login`, `/onboarding`
Pulse feed	Publish short posts, browse media, like, comment, and search	`/pulse`, `/pulse/[id]`
Discovery and matching	Explore students, map/gallery views, and match flows	`/discovery`, `/discovery/map`, `/discovery/gallery`, `/discovery/match`
Messaging and calls	Direct chat, channels, and LiveKit-backed calls	`/messages/chats`, `/messages/channels`, `/messages/chats/[id]/call`
AI advisor	Ask academic or campus questions through the chat surface	`/advisor`
Settings and operations	Manage privacy, appearance, billing, FAQs, and moderation	`/settings`, `/moderation`, `/notifications`

Repository Layout

Path	Responsibility
`stitch/frontend`	Next.js App Router application, shared UI components, client SDK wiring, and deployment config for Netlify
`stitch/backend`	FastAPI application, controllers, service layer, workers, migrations, and operational scripts
`stitch/backend/knowledge`	Structured academic and campus data used by the advisor and search flows
`stitch/backend/migrations`	Incremental SQL migrations for Supabase/Postgres
`stitch/docker-compose.gorse.yml`	Local recommendation stack with Gorse, Redis, and Postgres
`stitch/docker-compose.livekit.yml`	Local LiveKit server for calls and media sessions
`stitch/*.md` and prototype folders	Architecture references, design explorations, and stitched UI concepts
`experiments/sejong_portal_agent`	Separate experimental portal-agent work, not part of the primary production runtime

Design Direction

The repository also contains non-runtime prototype folders such as splash_auth, onboarding, global_feed, flash_chats, and thread_conversation. These are useful for documenting intent and product direction even when the final runtime implementation lives elsewhere in the codebase.