Rullst AcademyRullst Academy/Lesson
Applications with Rullst I · Lesson 14 / 14

Mission: an application with your decisions

Now the reference becomes a starting point for a different problem.

Learning paths24 min

Let's discover together

  1. 1

    Choose another fictional context: expeditions, small repairs or experiments. Write a three-action contract and a boundary. Renaming and recoloring are not enough: change an observable rule such as priority range, sorting or a pending-task filter.

  2. 2

    In PROJECT.md record changes to interface, server, tests and data. If changing schema, use a new test database and explain migration needed for old data. Add at least one positive test, one boundary/failure test and a case absent from the example.

  3. 3

    Deliver a README with versions, commands, active file, results, recovery rehearsal and limits. Check keyboard, messages, literal text and a narrow screen. Ask someone else to follow it without you doing the steps; record confusion. If no reviewer is available, mark external review pending.

  4. 4

    The Rullst Academy editor stores one file in this browser; your account stores completion and XP. The ZIP is the original template without your edits. The GitHub button sends only the confirmed file. To publish the entire app, use Git manually with .gitignore, excluding databases, backups and secrets. GitHub is optional.

  5. 5

    After a break, explain a request’s journey without copying the README and try a new variation. Declare help from people or AI and what you checked. Passing the assessment records exercise understanding; it does not prove authorship, local execution or professional independence.

Your application workbench

The kit includes a complete app to investigate and modify. The excerpt below explains this step; the editor contains the indicated file. Rullst Academy does not compile or run this server in your browser.

File to study and modify

PROJECT.md

Contract → implementation → positive/negative tests
→ recovery rehearsal → README → peer feedback
→ another problem after a break

Extract the kit to a new folder and open a terminal beside Cargo.toml. Use Rust 1.96+; the first build may download dependencies and take time. Then open http://127.0.0.1:3010. Stop with Ctrl+C and run again after editing.

cargo test --locked
cargo run --locked
My files and GitHub

Download your draft and replace the indicated file in your extracted copy. The editor saves one file in this browser; your account saves assessments and XP. The ZIP excludes your edits. GitHub sends only the confirmed file; use Git manually for the whole app, excluding databases, backups and secrets.

Official links and next step

✦
YOUR MISSION

Deliver an original variation with tests, recovery, instructions and review.

Now it's your turn

Discovery workshop

Decide before running

Deliver an original variation with tests, recovery, instructions and review.
Build your answers and check when you are ready.
A moment to understand

Which conclusion follows from completing this assessment?

I need a hint

Building requires integration and explaining choices. The platform does not observe your computer or certify independence through a quiz; document execution, variation and review.

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

Deliver your modified app and PROJECT.md with a new rule, original tests, recovery and feedback. Explain one failure you fixed and one remaining limitation. After a break, solve a different variation and record the help needed.

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

Deliver your modified app and PROJECT.md with a new rule, original tests, recovery and feedback. Explain one failure you fixed and one remaining limitation. After a break, solve a different variation and record the help needed.

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.