Start here: this week

Start here: this week

Week 3 runs four one-hour classes, Monday to Thursday, and the capstone presentation on Friday 2 October. Everything you need this week is in this unit. You should not have to go back to unit 0 or unit 2.

Two things to finish, and they are separate

The final assignment The Gecko capstone
What it is your research agent, answering from six documents your own store on devnet, and a buyer agent that buys from it through Gecko
How it is judged privately, on a question set, for a signed certificate the six-minute presentation on Friday
Where you build it my-final-assignment, made with uv run bootcamp final new ../my-final-assignment my-gecko-buyer, cloned from the capstone repository
Start with the final assignment tutorial the Gecko capstone, then step by step, with your agent

What is graded, and how to score all of it: everything that is graded: the 15 marked items on the track, with a link to each, and the final assignment.

Every day

  1. Before class: git pull, then uv sync --extra projects --extra agents.
  2. In class: open the session's follow-along; the table at its top says what fits in the hour.
  3. After class: the follow-along's "Keep going on your own" section lists what to finish, and the capstone's project for the day is in its repository.
  4. Stuck? Ask the course from your assistant (below). It answers from these pages and names the page, so you can check.

Your assistant, and the course

Background for sessions 12 and 13

Sessions 12 and 13 build on the week-0 MCP course. It is listed here, in unit 3, so you do not have to go back for it: topic 9, your first MCP server, topic 10, resources, prompts and the LLM, and topic 11, databases, APIs and third-party servers. Topic 11 is not session 11's assignment. Session 11's exercises are ch11-e1 to ch11-e3, in the session 11 notebook. The week-0 topics are w09 to w11.

The week at a glance lists every session and what each one adds.

Handing work in

Session exercises go in from your course folder, as always. Handing work in has the command, and what to do when a pull request has no checks or never merges.