ced4568andClaude Sonnet 5
f695b7c95d
- root-01-m00-welcome-to-root: program overview + Lab-lifecycle orientation (disposable Labs, permanent progress, hints, reset/recreate, help-requests). - One short intro-lesson activity for each of the three bare practice-bank modules (root-06-m01, root-07-m01, root-10-m02), explaining what the bank is and why it has no per-scenario teaching of its own — the minimum real authoring needed for genuine self-paced readiness without reclassifying them optional (see the curriculum migrations). Co-Authored-By: Claude Sonnet 5 <[email protected]>
32 lines
1.2 KiB
Markdown
32 lines
1.2 KiB
Markdown
# Knowledge Check: Welcome to ROOT_
|
|
|
|
---
|
|
|
|
**1. If your Lab environment is recreated, what happens to a file you saved inside it, and
|
|
what happens to your completed Labs so far?**
|
|
|
|
*Answer:* The file disappears — nothing inside the Lab persists across a recreation. Your
|
|
completed Labs and course progress are unaffected — those are stored on RootNode's servers, not
|
|
in the Lab, and survive regardless of what happens to any Lab environment.
|
|
|
|
**2. A Lab task fails your validation check. What should that tell you?**
|
|
|
|
*Answer:* Specifically what isn't correct yet, based on the real current state of your
|
|
environment — it's diagnostic information to act on, not a penalty.
|
|
|
|
**3. Name one thing to try before assuming a Lab is "just broken."**
|
|
|
|
*Answer:* Check the available hints (revealed one at a time), and if the environment itself
|
|
genuinely seems broken rather than the task being hard, use Reset Scenario & Environment to
|
|
rebuild it cleanly.
|
|
|
|
---
|
|
|
|
## Instructor Notes
|
|
|
|
**Facilitation:** This is a good moment to actually demonstrate a Lab reset live if you have
|
|
time — students remember "I saw it happen and nothing bad occurred" far better than being told
|
|
it's safe.
|
|
|
|
**Approximate timing:** 3 minutes.
|