PART I
Warm-up
Reconnect with a useful idea before starting rehearse the riskiest integration. 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
Build a deterministic small dataset for a rehearsal
An integration rehearsal isolates a consequential assumption with disposable inputs, independent expectations and an observation plan. This public site supplies no .ws runtime or native test harness, so the result is a concrete reproducible rehearsal artifact. It must never claim that a paper trace measured host behavior or mutate live user resources to create failure evidence.
A low-stock rehearsal uses three disposable rows: rope stock 2, lamp stock 9, flask stock 10. The intended stock<10 rule retains rope and lamp, excluding flask at the boundary. Sample expected artifact is two rows ordered by stock: rope 2, lamp 9. The expectation is derived before a real host run so it can reveal an incorrect filter or ordering.
Do not use a live inventory dataset or accept whatever a future query returns as the answer. A known tiny input isolates the rule and avoids unexplained data changes. Query DSL and field symbols remain proposed host contracts, not executed facts.
Worked reasoning and supplied artifact
// Worked contract artifact:
// A low-stock rehearsal uses three disposable rows: rope stock 2, lamp stock 9, flask stock 10. The intended stock<10 rule retains rope and lamp, excluding flask at the boundary. Sample expected artifact is two rows ordered by stock: rope 2, lamp 9. The expectation is derived before a real host run so it can reveal an incorrect filter or ordering.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.
// A low-stock rehearsal uses three disposable rows: rope stock 2, lamp stock 9, flask stock 10. The intended stock<10 rule retains rope and lamp, excluding flask at the boundary. Sample expected artifact is two rows ordered by stock: rope 2, lamp 9. The expectation is derived before a real host run so it can reveal an incorrect filter or ordering.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
Reduce the three rows by filtering first, then ordering the retained rows.
- 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 rehearse the riskiest integration.
Prepare a rehearsal dataset of four tournament resources with available-slot counts 0, 4, 5 and 8 under a rule slots<5. Write the exact selected/order expectation and identify the equality boundary.
What to produce
A disposable four-row dataset, expected retained rows 0/4 in ascending order and a boundary explanation.
- 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?
A low-stock rehearsal uses three disposable rows: rope stock 2, lamp stock 9, flask stock 10. The intended stock<10 rule retains rope and lamp, excluding flask at the boundary. Sample expected artifact is two rows ordered by stock: rope 2, lamp 9. The expectation is derived before a real host run so it can reveal an incorrect filter or ordering.
Do not use a live inventory dataset or accept whatever a future query returns as the answer. A known tiny input isolates the rule and avoids unexplained data changes. Query DSL and field symbols remain proposed host contracts, not executed facts.
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 rehearse the riskiest integration. 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.
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.
- Build a deterministic small dataset for a rehearsal
- Reduce the three rows by filtering first, then ordering the retained rows.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Reduce the three rows by filtering first, then ordering the retained rows.
This marks your personal practice record only. It is not a certification or an official workspace assessment.
