Triage

The description states that Triage is a local-first AI student desk. It ingests academic communication from multiple sources including:

• Pasted notices
• Uploaded text files
• Gmail messages
• Google Classroom announcements/coursework
• Simulated WhatsApp-style messages

It classifies each item into one of three categories:

• Obligation (deadlines, registrations, forms, mandatory notices)
• Study Material (question banks, unit notes)
• Noise (messages not requiring action or study)

For obligations, it extracts deadlines and groups them by urgency (Immediate, This Week, Later). For study material, it compares question-bank and unit-note content to produce a ranked study outline. It includes an Approval Drawer, where students must manually approve actions before any external submission.

The system is built using:

• Backend: Python/FastAPI
• Frontend: HTML/CSS/JavaScript (React-like)
• Database: SQLite
• Integrations: Gmail API, Google Classroom API, Google OAuth
• AI model: OpenAI Codex (structured JSON outputs)

Not evidenced: whether Triage has moved beyond the demo stage or is being used by students.

The author positions Triage as a student attention management tool inspired by medical triage practices. It aims to reduce cognitive load by sorting academic chaos into clear next steps.

Key claims:

• “Triage uses Codex to sort scattered WhatsApp, email, and Classroom chaos into a clear Action queue and a ranked Study plan.”
• “You approve every action; it never decides alone.”
• “It treats student attention as limited and valuable.”

These are self-reported claims about intent and design philosophy. The description does not state whether Triage has been adopted or validated by students.

Inferences:

• The tool is designed to be human-in-the-loop, with no external automation.
• It emphasizes control and transparency over AI autonomy.

The self-reported target customer is a student navigating academic communication across multiple platforms. The author states:

“I wanted to build something that treats student attention as limited and valuable.”

This suggests the tool is aimed at students who are overwhelmed by scattered, time-sensitive messages and need help prioritizing.

Not evidenced:

• Whether Triage has been tested with actual students.
• If there is a defined ICP beyond "student."
• No mention of age range, academic level, or institutional context.

The description does not provide any information about:

• Revenue model
• Pricing structure
• Monetization strategy
• Customer acquisition plan

Not evidenced: Any business model or pricing evidence.

The project is built as a web application with:

• Backend: Python/FastAPI
• Frontend: Custom HTML/CSS/JavaScript (React-like)
• Database: SQLite
• AI integration: OpenAI Codex API with structured JSON outputs
• OAuth integrations: Gmail and Google Classroom (read-only, local setup)
• Deployment: Vercel (frontend), Railway (backend), local demo path

Not evidenced:

• Whether it is deployed for production use.
• If there are plans or progress toward multi-user support.
• No evidence of scalability, performance metrics, or infrastructure beyond the demo.

The description states that this is a hackathon submission (OpenAI 2026). It includes:

• A working end-to-end flow
• Structured AI classification
• Human-in-the-loop design
• Simulated WhatsApp data
• Local OAuth workflow

However, there is no evidence of:

• Customer usage or adoption
• Revenue or monetization
• Product traction beyond the demo
• Any form of market validation

Not evidenced: Traction or maturity signals.

The description does not mention any competitors. It is unclear whether Triage is positioned against existing student productivity tools, academic communication platforms, or AI triage systems.

Not evidenced: Competitive landscape or positioning relative to other tools.

• Demo-only status: The product is described as a demo with no evidence of production use.
• No external automation: While the design is intentional, it may limit utility for users seeking more automation.
• Simulated data: WhatsApp integration is simulated, not live — this could be a red flag for future development.
• Local-first architecture: May hinder scalability or user experience in multi-user environments.
• No revenue model or monetization strategy reported.

Inferences:

• The tool may struggle to scale beyond the demo without significant rework.
• Lack of traction or customer feedback makes it hard to assess real-world utility.

1. Has Triage been tested with actual students? What was their feedback?
2. Are there any plans for production deployment or multi-user support?
3. How does the team plan to monetize this tool, if at all?
4. What are the technical limitations of the current architecture that would prevent scaling?
5. Is there a roadmap for integrating real WhatsApp or other messaging platforms?
6. What is the long-term vision for Triage beyond the demo?