Hackathon 2: To-Do Application Development Stages
📌 The Hackathon 2 project requires building a To-Do Console App in Python initially, which serves as the foundation for the MVP (Minimum Viable Product).
👩‍💻 The core MVP features (MVP 1) must include: Add, Delete, Update, View, and Mark as Complete functionality.
📈 The project evolves through phases (MVP 1 to MVP 3), adding complexity from essential features to intermediate enhancements (like categorization/priorities and filtering/searching) and finally to advanced features (like recurring tasks and reminders).

Three-Tier Architecture (3T) for Web Applications
🌐 Phase 2 mandates a full-stack web application based on a Three-Tier Architecture (3T): Client Tier (Frontend/UI), Application Tier (Backend/Business Logic/API), and Database Tier.
🔗 The Application Tier (Backend) uses FastAPI to expose functions via REST API over the HTTP protocol, allowing the Client Tier to interact with it.
💾 The Database Tier uses Neon (a managed PostgreSQL service) connected via an SQL Model (Python classes) for data validation, sanitization, and persistence, protecting the database from direct client access.

AI Agent Structure: Skills and Sub-Agents
⚙️ For advanced development, the focus shifts to creating reusable components: Skills and Sub-Agents (like Front-End Developer, Back-End Developer, etc.) using a framework like DotClot.
🛠️ Skills (e.g., FastAPI creation, SQL Model usage) should be developed first, potentially starting with a "Skill Creator" skill, and then assigned to specific Sub-Agents via YAML configuration in the `.clot` file.
🚀 Utilizing pre-built Skills and Sub-Agents allows for rapid project development; Phase 1 projects could be completed in under 3 hours with limited token usage.

Key Points & Insights
➡️ Always build the essential MVP version first; submit it, and then update the same project to intermediate or advanced levels for further submissions.
➡️ Localhost (127.0.0.1) acts as a loopback interface during local development, simulating external network calls within the same machine via the network card's interface.
➡️ The Application Tier is stateless by default using REST APIs; developers must explicitly build stateful features (like ongoing chat sessions) using mechanisms like sockets or Event Streaming (SSE).

📸 Video summarized with SummaryTube.com on Dec 23, 2025, 19:20 UTC