Rullst AcademyRullst Academy/Lesson
From application to release with Rullst · Lesson 12 / 12

My verifiable handoff

Now you hand over a small application with instructions, an understood failure and demonstrated recovery. Your work is stronger when its limits are clear.

Learning paths45 min

Let's discover together

  1. 1

    Choose a small adaptation for a fictional task, such as changing the main text to an experiment organizer. Explain its audience and what changed. Preserve validation rules and schema in this project.

  2. 2

    Without copying predicted results as observations, run tests, build, restart with data, isolated diagnosis and restoration to another file. Complete REPORT.md with actual commands and outcomes.

  3. 3

    Invite someone to follow the instructions or repeat them in a new folder. Fix one confusing instruction. Public sharing is optional; minors follow caregiver guidance and do not share account data.

  4. 4

    Mark Podman, Quadlet and Caddy executed only if you actually rehearsed them in the stated environment. Otherwise submit analysis and the next prerequisite. No cloud account, card or domain is required for the local path.

  5. 5

    Academy progress and badge record corrected site exercises; they do not certify that we ran your server or validated a real deployment. Your report and demonstration are separate evidence.

  6. 6

    The final ZIP combines Rust source using Rullst 12.1.1, comments in your chosen language, lockfile, tests and guides. Read the comments and compare them with your report. List protections still needed before using real data.

From reasoning to execution

The core path runs on your computer with fictional data. Podman, Quadlet and Caddy are optional extensions; no domain purchase or cloud subscription is needed. This lab is not ready for public writes.

Read the steps before running anything. The commands below are a reference; README.md explains your OS syntax and LAB.md contains the sequence. The site does not run these commands for you.

cargo test --locked
cargo build --release --locked
cargo run --locked -- verify restored-01.db
My evidence record

Adapt the board to a fictional lab and deliver REPORT.md with a failure you fixed, two identified versions and isolated restoration. Request independent reproduction and record the improvement made after feedback. Declare unexecuted extensions and what public use still needs.

Separate prediction, execution and observed result. Record “not executed” when the environment is missing. Site progress does not validate real deployment or grant professional certification.

My files and GitHub

Official links and next step

✦
YOUR MISSION

Collect your own execution, diagnosis, update and restoration evidence, distinguishing analysis from completed practice.

Now it's your turn

Discovery workshop

Decide using evidence

The handoff reports local tests, but Quadlet was not executed. The site badge was earned.
Build your answers and check when you are ready.
A moment to understand

Which handoff best supports what you learned?

I need a hint

A good handoff distinguishes what was predicted, executed, observed and not yet tested. Completing site exercises is not an audit of your environment.

Loading your journey…

How can I tell what I learned?

Use the objectives and challenge below for reflection or a conversation with someone who can help. This is guided self-assessment: it sends no answers, awards no XP and does not automatically verify independence.

In Building, integrate a small original solution, test an unseen variation, record limits and seek review when possible. Reproducing the example is a start; explaining and adapting develops independence.

Your transfer challenge

Adapt the board to a fictional lab and deliver REPORT.md with a failure you fixed, two identified versions and isolated restoration. Request independent reproduction and record the improvement made after feedback. Declare unexecuted extensions and what public use still needs.

Keep evidence: prediction, attempt, result, an original change and what you still cannot explain. Seek feedback when possible; if studying alone, return later without copying and compare attempts.

Try again another time

After a break, explain the idea without opening the solution and try a different example. Compare with your first attempt: what can you do independently, and where do you need a hint? You may write, speak or draw; choose a way to check the same idea. Record help received, including AI, and revisit the part you need. There is no universal deadline or extra XP for this record.

Completions and XP record Rullst Academy assessments. An introductory track can help everyday life and prepare further study; alone it does not prove complete mastery or professional readiness. Level indicates depth, not age.

Take it with you

Adapt the board to a fictional lab and deliver REPORT.md with a failure you fixed, two identified versions and isolated restoration. Request independent reproduction and record the improvement made after feedback. Declare unexecuted extensions and what public use still needs.

At your own pace

My files and GitHub

Every lesson can become your own record: code, notes or a practice plan. Saving a file to GitHub is optional and does not change your XP.

Student guide

The editor and downloads open when this lesson is available to your account. Check access below or return to the track map.

Checking your access to this lesson…

Rullstpetbot

AI can make mistakes. Check the lesson material.