PART I
Warm-up
Reconnect with a useful idea before starting build the master final project. 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
Decompose the final application into reviewable contracts
The final Fast Track application integrates a bounded user goal, reusable rules, proposed native services and explicit host boundaries. Public practice remains open and self-directed; its self-checks are separate from private examinations. A strong final artifact includes complete sample reasoning, meaningful independent cases and honest evidence statuses rather than a list of API names or a personal completion tick.
The worked expedition-kit application has three responsibilities: orientation window, low-stock review and a locally reasoned remainder calculation. Sample decomposition lists UI host for presentation, WDB design plus kit collection for reads, and a pure helper remaining(total,packed) for arithmetic. At total 12 and packed 5, the helper predicts 7 items. Each boundary names inputs, permission and evidence separately.
Do not let Application act as a fictional all-purpose built-in that supplies every resource. WMATH/WDB/WUIX remain conceptual services and host inputs remain explicit. The final design should be decomposed enough that a missing query host does not invalidate an inspectable arithmetic explanation.
Worked reasoning and supplied artifact
// Worked contract artifact:
// The worked expedition-kit application has three responsibilities: orientation window, low-stock review and a locally reasoned remainder calculation. Sample decomposition lists UI host for presentation, WDB design plus kit collection for reads, and a pure helper remaining(total,packed) for arithmetic. At total 12 and packed 5, the helper predicts 7 items. Each boundary names inputs, permission and evidence separately.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
// Worked contract artifact:This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// The worked expedition-kit application has three responsibilities: orientation window, low-stock review and a locally reasoned remainder calculation. Sample decomposition lists UI host for presentation, WDB design plus kit collection for reads, and a pure helper remaining(total,packed) for arithmetic. At total 12 and packed 5, the helper predicts 7 items. Each boundary names inputs, permission and evidence separately.This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
Try the guided change
Build a responsibility/service/input/evidence table and trace remaining(12,5) independently.
- 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: Independent WillowScript application. Build a small, understandable change around build the master final project.
Decompose a tournament organizer into fixed orientation, venue availability review and a pure remaining-slots helper. Give each contract an input, result, host requirement and current evidence status.
What to produce
A three-responsibility architecture table and one fully traced pure calculation.
- 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?
The worked expedition-kit application has three responsibilities: orientation window, low-stock review and a locally reasoned remainder calculation. Sample decomposition lists UI host for presentation, WDB design plus kit collection for reads, and a pure helper remaining(total,packed) for arithmetic. At total 12 and packed 5, the helper predicts 7 items. Each boundary names inputs, permission and evidence separately.
Do not let Application act as a fictional all-purpose built-in that supplies every resource. WMATH/WDB/WUIX remain conceptual services and host inputs remain explicit. The final design should be decomposed enough that a missing query host does not invalidate an inspectable arithmetic explanation.
Original learning-path task and reference
Use your Willow knowledge to implement the .ws host integration, explaining which work remains native and which belongs in the script. In a classroom scheduling assistant, demonstrate build the master final project. Read the source-grounded example and predict its observable behavior before making changes. Include .ws source and a host-resource contract; compare at least one normal case and one edge case.
import wuix.widget;
import app;
domain Workspace {
const application = Application({
name: "Workspace",
window: { title: "Dashboard", size: [1280, 800] },
events: {
"app.ready": fnc() -> void { console.log("Ready"); }
}
});
}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.
- Decompose the final application into reviewable contracts
- Build a responsibility/service/input/evidence table and trace remaining(12,5) independently.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Build a responsibility/service/input/evidence table and trace remaining(12,5) independently.
This marks your personal practice record only. It is not a certification or an official workspace assessment.