Docs / system notes
How this actually works
Read the material in the open. Enrol when you want the platform to remember the work you do.
01 / learner path
For learners
The short version
Reading and enrolment
Published course material can be opened without an account. Reading a lesson and seeing what an activity asks are separate from recording work. Enrolment is required before the service accepts a submission or writes lesson progress. Submitting work does require an active enrolment. Enrolment is only available for a published offering.
The four kinds of work
| Type | What the platform does | Progress effect |
|---|---|---|
| Multiple choice | Checks the selected option ids against the author’s correct options in process. | A fully correct answer can complete the activity and award its points once. |
| Written response | Uses the author’s rubric when one exists. Marking checks that awarded evidence is quoted from the learner’s own answer; without a rubric, the attempt waits for a person. | A fully marked answer can complete the activity and award its points once. |
| Project submission | Records the submitted work against the artifact types requested by the author. It is left for a person to mark. | Recording the attempt alone does not award automatic progress points. |
| Code run | Supports starter code for runnable work. Language challenges run in the service’s sandbox; a challenge submission is checked by its verifier. | A passing language exercise awards its points once; trying a run is not itself a progress award. |
Progress and points
Progress is scoped to the learner’s active enrolment and lesson. A progress row keeps the completed activity ids and points for that lesson. Passing the same activity again does not add its points a second time. Submitting work or writing progress is refused when the enrolment is not active; re-enrolling reactivates the existing enrolment.
learner + enrolment + lesson
├─ completed activity ids
├─ lesson complete flag
└─ points earned so farPractice challenges
The Challenges panel surfaces runnable language exercises from enrolled courses. Running code requires a signed-in session and checks the code without recording progress. Submitting an exercise requires an active enrolment; a passing verifier result records the exercise and awards its points once. Draft code is kept locally so an unfinished attempt can survive a refresh.
Offline
Installing Let’s Go puts it on your home screen and keeps lessons you have already opened readable without a connection. It does not fetch a whole course in advance, and it does not accept submitted work while you are offline: those still need a live connection to the service that marks or verifies them.