Instructions and observable results — Build the smallest useful slice

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.

Recall note

A rough note is enough. You can revise it after the example.

PART II

Instruction & guided example

Build one useful calculation before an interface

A smallest useful slice connects real inputs to an understandable result. For a snack-shop total, the useful behavior is adding two prices represented in whole cents. A screen, database and audio service would add boundaries before you have checked the central calculation.

The example represents a drink as 125 cents and a snack as 75 cents. main calls add(125,75); add binds a = 125 and b = 75, then returns 200. That means 200 cents, not 200 items. Carry the unit in your explanation even though the type i32 describes an integer rather than a currency unit.

The function name does not convert units. Passing 1 and 75 because the drink costs 1.25 dollars mixes dollars and cents and predicts 76, a plausible-looking but wrong amount. Establish one unit at the boundary instead of hoping arithmetic will repair inconsistent inputs.

Worked reasoning and supplied artifact

fnc add(a: i32, b: i32) -> i32 {
    return a + b;
}
fnc main() -> i32 {
    return add(125, 75);
}

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(125, 75);
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

Replace the prices with 150 and 90 cents. Predict 240 cents and explain why neither input requires a host service in this exercise.

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.

Prediction or guided notes

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.

Your drafts remain here. Continue whenever you are ready.

PART IV

Independent practice

Project context: Snack-shop calculator. Build a small, understandable change around instructions and observable results.

Create a minimal total for a 225-cent ticket and a 50-cent fee. Include main and add, identify the unit in a comment, and provide a second case with a zero fee. Do not design the payment screen yet.

What to produce

Two tiny functions, a unit statement, and cases (225,50) → 275 and (225,0) → 225.

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.

Your .ws practice draft

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?

Original learning-path task and reference

In a racing checkpoint editor, demonstrate instructions and observable results. Create the smallest .ws integration that demonstrates the section contract. 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.

A 125-cent item and a 75-cent item produce 200. What unit does 200 have?CentsDollars because the function is called addNo unit can be documented for an integer

Explain a normal or boundary case

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.

Build one useful calculation before an interface
A smallest useful slice connects real inputs to an understandable result. For a snack-shop total, the useful behavior is adding two prices represented in whole cents. A screen, database and audio service would add boundaries before you have checked the central calculation.
Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Write one reason to keep the first calculator free of UI dependencies.

Your recap

This marks your personal practice record only. It is not a certification or an official workspace assessment.