This lab is a welcome whose substance is the setup — and it ends, like every lab in this course will, with a green check. Nothing here is a box you tick: the finale is your machine proving it can run the whole loop before you write a line of code. Fifteen minutes cold; about two if your tools are already in place.
The promise
The machine boots without you. Twenty-four labs from here, it boots because of you: pixels from your own 64-bit kernel in the first hour, then the CPU, the memory, the time, the privilege boundary and the disk — until your shell runs your programs, from your filesystem, at ring 3. Everything is built, and graded by booting what you built.
How a lab is graded
You read and decide here; you build in your terminal.
sboot testgrades your work on your own machine, as often as you like. It is how you find out what to fix.sboot submitrecords the official result with us — the same checks, our computation. It comes back with a link to your code review — written by the course's AI reviewer over your diff; reading that page and pressing Complete on it is what finishes a lab and opens the next.
Your code stays yours
The folder sboot start unpacks is yours — plain files and, if git is on your
machine, a local git repo you can push anywhere, or nowhere. We hold no GitHub credential and never touch your
remote repo: gh, git and sboot only ever run on your machine. sboot submit uploads your source and
what your test run printed; what we keep afterwards is the verdict — your progress
record — and the diff your code review was written on, not a copy of your repo.
The course's own tests and grader are not in that folder, so publishing it publishes your kernel and nothing else.
New machine, months from now? Install sboot, run sboot login, then
sboot resume with your folder's path or your repo's address. It fetches what a
fresh copy is missing and runs this lab again: the same proof it gives you today.