⚠️ Note on this project: FACU was my first full-stack MVP. I built it during my early learning stages to solve a real connection problem among students at my university. The code here represents my baseline (heavy on rapid, unstructured prototyping—aka "vibe coding"—and fast iteration). I keep it public as a log of my evolution toward the cleaner, standard-driven architecture I apply in my current projects.

📌 The Problem

In massive public universities, schedule and class transfers rely on manual bureaucratic processes, political intermediaries (Student Unions), and legacy monolithic systems. This creates severe bottlenecks, weeks of delay, and unnecessary burnout for students.

🚀 The Solution

FACU is a Minimum Viable Product (MVP) proposing a decentralized architecture. It cuts out the human middleman by matching student needs through a relational database algorithm. If Student A needs the night shift and Student B needs the morning shift, the system makes an automatic cross-match in milliseconds.

⚙️ Core Features

Automated Matching: Optimized SQL queries (cross JOINs) to pair inverse requests instantly.

Data Integrity: Strict database constraints (CHECK, ON DELETE CASCADE) to prevent redundancies and logical errors.

Closed Authentication: System restricted exclusively to institutional emails (@mi.unc.edu.ar).

Mobile-First Design: Responsive UI built for quick, seamless use in the university hallways.

🗄️ Database Architecture

The core system relies on PostgreSQL to guarantee transaction consistency. The main schema includes:

alumnos (Students): Institutional identity and validation.

materias (Subjects): Normalized catalog to prevent typos in requests.

solicitudes_intercambio (Transfer Requests): The transactional engine handling states (Pending, Match_Found, Completed).

🗺️ Roadmap

[ ] Build the REST API / Connect to Supabase.

[ ] Refactor frontend into modular interactive components (React).

[ ] Integrate AI (Gemma API) for natural language processing of user requests.