AllAbout Campus
- Role
- Team lead / four people
- When
- Sep 2026
- Stack
- React / TypeScript / Fastify / Steel / Playwright
- Status
- Hackathon demo
Why I built it
Course rules are scattered across calendars, department pages, announcements and discussions. Students need more than a fluent answer: they need to know which rule it comes from, whether it changed and what remains unknown.
Who it is for
The aim is to reduce the work of finding and comparing campus information while keeping uncertainty visible. A coverage receipt helps a student see the difference between a checked source and one the agent could not reach.
My contribution
Rui, Yilin, Ziqin and I built the hackathon demo. I set the plan, led backend work, implemented source routing, evidence extraction and coverage reporting, reviewed the frontend and presented the recorded demo.
Evidence pipeline
The question selects a source path. Browser content is captured, evidence is extracted and the answer returns citations alongside missing coverage. Quotations must occur in the captured text; university sources and community discussion are distinguished.
- RouteCourse / term / relevant source
- CollectBrowser content / supporting quotes
- AnswerCitations / coverage / unknowns
Choosing useful sources
An unrelated timetable source was weakening general course answers. We removed it consistently from routing, interface expectations and checks. The lesson was that a source should earn its place by answering the question, not simply by being available.
Interface
Where it stands
The repeatable demo uses clearly labelled fictional sources to show an updated deadline and an unresolved question. Public browsing and account-based sources have different access requirements; continued integration work is part of the project.