A repository for our hackathon project (Hack the Bay Launch 2026)

To run the current student-planner demo locally:

cd catalog-service
pip install -r requirements.txt
uvicorn catalog_service.app:app --reload

In a second terminal, build the frontend demo that /demo now serves:

cd frontend/studentpath-make
npm install
npm run build

Then open:

• http://127.0.0.1:8000/demo

The frontend can be published from main with GitHub Pages using .github/workflows/deploy-pages.yml.

Important:

• GitHub Pages only hosts the static frontend.
• The catalog-service backend still needs a real host.
• Set the repository variable PAGES_API_BASE_URL to the backend URL before using the published site.
• The expected Pages URL is https://eliselhenry.github.io/HackTheBayS2026/.

Useful checks:

• http://127.0.0.1:8000/health
• http://127.0.0.1:8000/institutions/usf/catalog-years

If the browser shows an older version, rebuild the frontend demo and use Ctrl+F5.

Roles for this project:

1. Backend / Platform Lead - Evan King

Owns: system architecture API contracts auth/roles student record model registration workflow engine integrations and event logging

Outputs: canonical backend schema service boundaries registration/permit/advisor APIs audit trail for every automated action

Does not own: catalog-rule authoring frontend UX decisions prompt copy / advisor wording

2. Academic Rules / Catalog Engine Lead - Johann Hightower

Owns: degree requirements model prereq/co-req rules class-standing and priority logic permit-required detection exceptions and override policy sample USF-style catalog data

Outputs: machine-readable rules “why this course is allowed/blocked” explanations acceptance cases for degree progress and registration eligibility

Does not own: UI polish backend infra AI prompting strategy This role is the most important after backend. If nobody owns policy truth, the whole product becomes a polished lie.

3. Frontend / Student Workflow Lead - Elise Henry

Owns: student dashboard degree progress views semester planner schedule/cart UX permit request UX advisor-contact UX explainability surfaces for holds, blocks, and recommendations

Outputs: click-through student flow from “What do I need?” to “I registered / requested permit” advisor-facing request forms/drafts human-readable status and error states

Does not own: rule correctness registration engine logic final AI behavior

4. Automation / Verification Lead - Evan Persad

Owns: AI autofill and recommendation layer draft-generation for advisor emails priority registration queue logic test harnesses and demo scenarios observability and release confidence

Outputs: “suggested schedule” engine “draft advisor email” engine safe automation modes regression suite for common student cases

Does not own: source-of-truth student rules primary API architecture final UX structure How these roles should interact