Week 1

This week sets out what you build, how it is assessed, and how your team gets its repository. Most of the work in week 1 happens between the two classes: you install the tools, create your accounts, and form your team.

Before the first class

Nothing. Come as you are.

The first class

The course launch lecture. It states what you build and what counts as real, then how the semester is marked and how teams work.

• What you build. A working system that someone outside the room uses. Real means four things: a real client who wants the problem solved, a real database whose information is still there tomorrow, a real address anyone can open, and real use by your client before the end of the semester.
• It must be worth building. Someone is measurably better off — money saved, time saved, or a better decision — and the system has a plausible next life: it could be sold to a business or adopted by a public organisation.
• The stack, and why the two tools get different work. You plan in Gemini Enterprise and build in Antigravity, with GitHub holding the files and the history and Supabase holding the database and the sign-ins. Gemini Enterprise lives in a browser and cannot reach your files. Antigravity runs on your laptop, can read and write those files, and can act without asking you first. That difference is the reason the work splits the way it does.
• The accounts model. Your KU account signs you in to both Google products. GitHub is one account per student. Supabase is one account per team, shared.
• What a sprint is. A fixed stretch of work — two weeks here — that ends with something that actually runs and is presented to the room. Not a plan for later.
• The six phases, and how the course is marked. Six deliveries, not one ending, and none of the deadlines move. The marks are 65 group and 35 individual, with no final examination. The weights and the exact dates are on the deliverables page.
• The AI posture. AI use is expected, not permitted. There is no manual track and no AI track, and one rubric for everyone. You must be able to explain your own work.
• The repository is the evidence. One repository per team. Every story is labelled with its owner, nobody merges their own work, and every pull request declares AI use. Activity that is not visible in the repository did not happen.
• Teams and roles. You form your own teams, and each team divides the same set of standing roles between its members, plus a Phase Lead who rotates.

Slides

• Course launch

Before the second class

This is the heaviest part of week 1, and none of it can be done on the morning of the class. Work through it in order. The full instructions, with the security prompts on both platforms and a troubleshooting table, are on the setup guide.

Install the software

• Antigravity — the entry named Antigravity 2.0. Further down the same download page there is an older entry called "Antigravity IDE". That is not the one used in this course. Check the name before you download.
• GitHub Desktop, installed alongside it.

Create the accounts

• KU account. Already yours. It signs you in to both Gemini Enterprise and Antigravity. Do not create a personal Gmail account for this course.
• GitHub — one account per student. Create yours, then copy your username from your profile page rather than typing it from memory. Your GitHub username goes on the roster workbook, and that is how the instructor creates your team's repository.
• Supabase — one account per team, shared. Decide who creates it, then make sure every member can sign in. It is free, it works in Kuwait, and it does not ask for a payment card.

Form a team

• 4 to 6 people per team. No more than six teams in total.
• Settle it before the second class, not during it.
• If you cannot find a team, tell the instructor and you will be placed. Organise early rather than being the last group of three still looking.

Bring to the second class

• Your laptop, charged, and its charger. The room is short of outlets.
• Antigravity and GitHub Desktop installed and signed in.
• Your GitHub username, written down, and logins reachable from that laptop.
• Some free disk space.

The second class

The setup session. Every installation is verified on your own laptop, so the software has to be installed when you arrive. Teams are confirmed in the room, and each team settles how it will work for the rest of the semester.

• Every installation is checked, on each student's own machine.
• Teams are confirmed.
• Each member takes a standing role — Client Lead, Design Lead, Data Lead, Build Lead, and at five and six members the Quality and FinOps responsibilities.
• The team decides the whole six-phase Phase Lead rotation, not one phase at a time.
• The roster workbook is filled in: one row per member, the roles the team has chosen, and all six phase leads.
• The Phase 1 Lead emails the completed workbook to mo.almarzouq@ku.edu.kw before leaving the room. One email per team, not one per student. The instructor then creates the team repository, and all work for the rest of the semester happens there.

A team still short of members sends the workbook anyway and names the gap in the email.

Reference for this session

• Team roles — what each role owns and what it produces.
• Setup guide — the checklist the session works through.

Due this week

The completed team roster workbook, emailed before you leave the second class. Until it arrives the team has no repository, so nothing else in the course can start.

Phase 1 itself — a formed team, a verified environment, and a proposal the instructor accepts — is due at the end of week 2. See the deliverables page for the exact dates.

Read

No readings are set for week 1. The reading starts in week 2.

Use

• Setup guide — the software, the accounts, and what to bring.
• Team roster workbook (.xlsx) — your members, their standing roles, and the phase-lead rotation.
• Team roles — what each role owns.