PART I
Warm-up
Reconnect with a useful idea before starting instructions and observable results. In one or two sentences, describe the input, output or host boundary from the previous exercise that this lesson builds on. If you are arriving directly, skim the worked example first; there is no locked prerequisite.
A rough note is enough. You can revise it after the example.
PART II
Instruction & guided example
Make an evidence card another learner can audit
A useful demonstration contains the rule, inputs, intermediate reasoning and expected result. This is stronger than stating “works.” Because the public school has no WillowScript runtime, your card should be labelled a hand prediction and say which host behavior was assumed.
For a ticket subtotal of 300 cents and a 40-cent fee, main asks add(300,40). Bind a = 300 and b = 40; evaluate 340; return 340 through main. The evidence card reads: purpose = total cents; input = (300,40); expected = 340 cents; observation channel = host reads main’s return; execution = not performed.
A screenshot of syntax highlighting is not execution evidence. A check that only says “same as the program” also fails to supply an independent expectation. Document the arithmetic first so a later real toolchain run can be compared against something other than its own output.
Worked reasoning and supplied artifact
fnc add(a: i32, b: i32) -> i32 {
return a + b;
}
fnc main() -> i32 {
return add(300, 40);
}Illustrative example from the proposed WillowScript design. The language and WUIX/WMATH/WDB/WAUDIO/WTMP services are not implemented in the supplied source. This site has no interpreter, VM or native host and does not execute or certify the snippet.
Walk through the example, one line at a time
fnc add(a: i32, b: i32) -> i32 {Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return a + b;Evaluate the following expression using the current values, then send its result to the caller. Explain the value; do not confuse it with printed output.
}Close the nested block or value begun earlier. Match it to its opening boundary to keep the structure readable.
fnc main() -> i32 {Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return add(300, 40);Evaluate the following expression using the current values, then send its result to the caller. Explain the value; do not confuse it with printed output.
}Close the nested block or value begun earlier. Match it to its opening boundary to keep the structure readable.
Try the guided change
Write the worked evidence card, then add a zero-fee case and note the invariant total = subtotal when fee is zero.
- Write the supplied inputs and initial state before following the example.
- Reconstruct each intermediate calculation or host decision, then compare with the worked artifact.
- Explain why the contrasting alternative fails before attempting the changed inputs in Part IV.
PART III
Take a breather
Step back after the guided example. Look away from the screen, stretch, or reread your prediction. This is an optional learning pause, not a timer or an assessment gate.
When you return, try to name the lesson’s key idea without copying its wording. If that feels difficult, return to Part II and trace one line rather than restarting the entire lesson.
PART IV
Independent practice
Project context: Snack-shop calculator. Build a small, understandable change around instructions and observable results.
Submit a paper demonstration for a 180-cent snack and 120-cent drink. Include a negative-input question without pretending a stock or currency validation policy already exists. Identify one question a real host contract would need to settle.
What to produce
Source, two fully traced cases, a unit statement, a hand-prediction label and one unresolved policy question.
- State the intended behavior in a sentence before editing.
- Use only source-backed syntax and the host services whose contract you have been given.
- Record a normal case and a boundary or unavailable-resource case.
- Label hand predictions separately from anything actually measured in a supplied toolchain.
Syntax colors are a reading aid, not a compiler. The line you are editing stays uncolored until you move to a different line; capitalization is never changed. Drafts stay on this browser and code is not executed.
Need a hint?
For a ticket subtotal of 300 cents and a 40-cent fee, main asks add(300,40). Bind a = 300 and b = 40; evaluate 340; return 340 through main. The evidence card reads: purpose = total cents; input = (300,40); expected = 340 cents; observation channel = host reads main’s return; execution = not performed.
A screenshot of syntax highlighting is not execution evidence. A check that only says “same as the program” also fails to supply an independent expectation. Document the arithmetic first so a later real toolchain run can be compared against something other than its own output.
Original learning-path task and reference
In a media review console, demonstrate instructions and observable results. Submit source, acceptance cases, and an explanation proving the section objective. Include .ws source and a host-resource contract; compare at least one normal case and one edge case.
fnc add(a: i32, b: i32) -> i32 {
return a + b;
}
fnc main() -> i32 {
return add(2, 3);
}Where the original task needs a host API that is not supplied here, write the contract and predictions. Do not invent a runtime result.
PART V
Self-check
Use this check to notice what to revisit. It does not award a private course grade, block another page or claim to verify compiled code. Every answer has a learning explanation.
You may keep exploring even if you are unsure. Use the hint, compare the trace, and revise your explanation.
PART VI
Recap & small task
Bring the idea back to the mod feature you are building. A useful recap connects the mechanism to a decision you can make in your own code.
- Make an evidence card another learner can audit
- A useful demonstration contains the rule, inputs, intermediate reasoning and expected result. This is stronger than stating “works.” Because the public school has no WillowScript runtime, your card should be labelled a hand prediction and say which host behavior was assumed.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Summarize the difference between an expectation and an observed result in one sentence.
This marks your personal practice record only. It is not a certification or an official workspace assessment.