Walk in, find your team table
Team numbers are posted on each table. Sit with your 4 members.
June 20, 2026
June 20 opens with the completion ceremony (11:00); the hackathon working session and presentations run in the afternoon (from 14:00). What students do in the first 30 minutes of the afternoon session. What tutors do when things break. Time-stamped cadence the operations team uses to keep the day on rails.
Every student should hit "first model response" by T+30 minutes. If you are not at that point, ask your tutor immediately — do not wait until lunch.
Team numbers are posted on each table. Sit with your 4 members.
Use only the koicatiu.onmicrosoft.com account given by the operations team. Personal Microsoft accounts will not work.
Set up Microsoft Authenticator if asked. If the prompt loops, raise your hand — do not retry repeatedly.
https://ai.azure.com → workspace selector → fdry-koicatiu-teamXX. Confirm the model deployment is listed.
git clone https://github.com/halla-ai/hackathon-sample-2026 your-team-name && cd your-team-name
Run make dev-mock first to see the UI without Azure, then switch USE_MOCK=false.
Save a screenshot. This is the official "team is online" signal — send it to your tutor.
Six things break during hackathons. Each row shows the first 2 minutes (triage) and the next 5 minutes (escalation). Keep this open in another tab.
Triage (2 min)
Check that the student typed the full koicatiu.onmicrosoft.com address. Verify the temporary password from the operations export pack.
Escalation (5 min)
If still failing after 5 minutes, message the operations team in Tutors Telegram. They will reset the password from /admin/setup.
Triage (2 min)
Open the screen with the student. Confirm they see "Set up your authenticator" — not "Approve sign-in". The first sign-in must register, not approve.
Escalation (5 min)
If the student has no smartphone, request SMS fallback from operations.
Triage (2 min)
Confirm the team number. Open /admin/setup → search the student UPN → verify Foundry project assignment.
Escalation (5 min)
If missing, ops runs azure_foundry_project_provision.py for that team. Allow 5 minutes for propagation.
Triage (2 min)
Open /admin/credit → filter by team. Look for repeated calls, long prompts, or background loops.
Escalation (5 min)
Tell the team to stop the running script. If cost crossed 50% of team cap, message the operations team — they pause new deployments for that team only.
Triage (2 min)
Confirm the B1 slot status in /admin/teams. Check for a deploy lock or wrong region.
Escalation (5 min)
Keep the team in local dev mode. They can demo from their laptop if the B1 deploy never works.
Triage (2 min)
Trigger the demo backup (screenshot or video). All teams should have one ready.
Escalation (5 min)
No escalation needed — backup is the contract.
Stop App Service slots, log out of Azure, return name tags.
Operations team disables provisioning flag, archives password CSV to secure storage.
Cost reconciliation, tutor feedback, second-semester quota recalibration.