From hackathon to AI-901

Hackathon ↔ AI-901 Bridge

November 28 tentative is not the end. Each hackathon artifact maps to a Cohort 3 (Semester 2) AI-901 lab. This page shows the bridge so teams know what to keep and what to rebuild.

Six Bridges

Team project setup

Hackathon team assignment becomes the model for Cohort 3 (Semester 2) Foundry project groups.

Nov 28 hackathon

Each team uses one Foundry project (fdry-koicatiu-teamXX)

Cohort 3 (Semester 2) AI-901

Same project is reused for Cohort 3 (Semester 2) mini-labs and the team prototype sprint

Model call basics

The same endpoint, deployment, prompt, and .env pattern reappears in AI-901 labs.

Nov 28 hackathon

Hackathon teams call gpt-4o-mini or the assigned model from Python using AzureOpenAI client

Cohort 3 (Semester 2) AI-901

AI-901 Lab 2 (Model Deployment) reuses the same code as the entry point

Prompt engineering

Hackathon teams iterate on system prompts; Cohort 3 (Semester 2) students treat prompts as code artifacts (versioned, tested).

Nov 28 hackathon

System prompt lives in prompts/system.md, tested against demo questions

Cohort 3 (Semester 2) AI-901

Same prompts/system.md format used for AI-901 Lab 3 single-agent prototype

Grounding & retrieval

Hackathon RAG demos seed the Cohort 3 (Semester 2) deeper RAG work: indexing, evaluation, citations.

Nov 28 hackathon

Optional RAG sample with 3-5 public docs (TIU FAQ, syllabus)

Cohort 3 (Semester 2) AI-901

AI-901 Lab 4 (RAG) formalizes upload, retrieval, citation, evaluation

Responsible AI

Hackathon safety checks become lab checks for hallucination, privacy, cost, prompt injection.

Nov 28 hackathon

Risk register section in team README (5 lines)

Cohort 3 (Semester 2) AI-901

AI-901 Lab 5 (Responsible AI) expands risk register into a full review

Prototype to portfolio

Working hackathon demos can be refined into Cohort 3 (Semester 2) projects or portfolio artifacts.

Nov 28 hackathon

Demo + slide + README + screenshot/video backup

Cohort 3 (Semester 2) AI-901

Project sprint week 4 converts a hackathon sample into a polished prototype

Milestone Timeline tentative

7/1 Recruitment opened

Applications opened for Cohort 3 (Semester 2). English CV required.

9/7 Cohort 3 Foundry start

Teams get accounts and one Foundry project (fdry-koicatiu-teamXX).

9/14 Lab week 1

Lab 1 - Foundry project setup. Returning hackathon participants act as peer guides.

10/12 Lab week 3

Lab 3 - single-agent prototype. Teams pick a real project they will keep.

11/9 Lab week 4

Lab 4 - RAG. Teams convert their hackathon sample into a grounded version.

11/28 Hackathon D-day + Industry Day

Cohort 3 (Fall) completion ceremony. Demo + slide + README submitted. Internship MOU signing.

12/1 Results & reporting

Operations team consolidates cost, completion, and certification (Exam Round 2) results for project reporting. Internship placements follow in early December.

What to keep after 11/28

  • Your team Foundry project - do not delete
  • Your GitHub repo (from the sample template) with prompts and code
  • The risk register section in your README
  • Demo screenshots and the final slide
  • Tutor feedback notes from the dry run