What to submit
Four required items, three optional. Templates included so you do not have to invent the structure. Submit through your tutor on D-day; do not email the operations team directly.
Problem · User · Architecture · Demo · Impact. One topic per slide. No text-heavy slides.
Template
Title (team name + project) · Problem (1 sentence + user quote) · Architecture (one diagram) · Demo (screenshot + URL) · Impact (next 4 weeks + cost-per-user)
A live demo URL, a notebook, or a Foundry-playground link. Must execute a real model call during the 3-minute pitch.
Template
URL or QR code on slide 4. Backup screenshot and 30-second video saved in repo /demo/.
Setup steps, team roles, Azure resources used, 5-line risk register. Under 200 lines.
Template
Project name · 1-sentence pitch · setup steps · architecture sketch · Azure resources · risk register · team members
One screenshot of the working flow, plus one 30-90 second screen recording. Saved in repo /demo/.
Template
/demo/screenshot.png and /demo/recording.mp4
Public or invite-only. Secrets removed. README points to /demo and explains the run command.
Azure App Service or a static deployed page. Operations team will rotate keys after the event.
A 1-line "we used X Azure credit for the event" note in the README. Bonus for transparency.
Copy this skeleton into your slide tool. Each slide should hit one beat. The 3-minute pitch maps 1:1 to these slides.
# Slide 1 — Title
- Team name
- Project name
- One-line tagline
- Names of 4 members
# Slide 2 — Problem
- The problem in one sentence
- Who suffers (specific user, not "everyone")
- One quote or stat from a real conversation
# Slide 3 — Architecture
- One diagram, 5 boxes max
- Box labels: User → UI → API → Foundry → (optional) AI Search
- Note: which Azure services touch the user
# Slide 4 — Demo
- One screenshot of the working response
- QR code or short URL to the live demo
- "Backup video available" note if live is risky
# Slide 5 — Impact + Next Steps
- Who benefits and how many of them
- Estimated cost per user per month
- Three next-week actions if we keep buildingDrop this README.md into your repo and replace the bracketed values. Keep it under 200 lines.
# Project Name
> One-sentence pitch — what does this do and for whom?
## Team
- Team XX · Tutor: [Tutor Name]
- Members: [Name 1], [Name 2], [Name 3], [Name 4]
## Setup
```bash
git clone <repo>
cd <repo>
cp .env.example .env
# fill .env with values from your tutor
pip install -r requirements.txt
python app.py
```
## Architecture
[ Short paragraph or ASCII diagram. 5 nodes max. ]
## Azure resources
- Foundry project: fdry-koicatiu-teamXX
- Model deployment: gpt-4o-mini
- App Service slot: app-koicatiu-teamXX (B1)
## Risk register
- Prompt injection — system prompt forbids tool calls outside scope.
- Hallucination — answers cite the source document; out-of-scope queries refuse.
- Privacy — only public documents in the index; no student records.
- Cost — capped at <team_cap> KRW; idle App Service stopped after demo.
- Mitigation owner — [Member name] monitors all four.
## Demo
- demo/screenshot.png — main flow screenshot
- demo/recording.mp4 — 30-second screen capture