PART I
Warm-up
Reconnect with a useful idea before starting explain, improve, and resubmit. 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
Rehearse a failed assumption during resubmission
A resubmission should acknowledge failed assumptions and narrow the claim accordingly. If a supplied host cannot present at the expected target, the right response is to revise the target contract or identify the missing integration, not to keep claiming the screen was shown.
Suppose the original brief assumed main, but a future host review reports the only supplied target is workshop. The sample resubmission card says: failed assumption = main exists; new supplied fact = workshop target; source revision = mount workshop; content unchanged; evidence still needed = actual presentation at workshop. This is a hypothetical host report for contract reasoning, not a report that this site ran a host.
Do not retry arbitrary target names until one appears to work without a documented contract. Also avoid changing the text to hide a host-boundary issue. A precise resubmission tells the reviewer what new fact justified the edit and which outcome remains pending.
Worked reasoning and supplied artifact
import wuix.widget.button;
import wuix.layout;
domain Login {
const screen = {
layout: { type: "column", padding: [24,32], gap: 16 },
components: [{ type: "text", value: "Welcome to the workshop." }]
};
fnc show() -> void {
wuix.mount("workshop", screen);
}
}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
import wuix.widget.button;Name the external module this script asks to use. Importing a name does not supply a host resource or grant its capability permissions.
import wuix.layout;Name the external module this script asks to use. Importing a name does not supply a host resource or grant its capability permissions.
domain Login {Group related declarations under this named boundary. Read the nested declarations as the contents of that group.
const screen = {Name a value that this example keeps stable. Inspect the right-hand side for the value or configuration being bound.
layout: { type: "column", padding: [24,32], gap: 16 },Read this key/value within its containing object. State which parent owns it and the narrow visible behavior it configures.
components: [{ type: "text", value: "Welcome to the workshop." }]Read this key/value within its containing object. State which parent owns it and the narrow visible behavior it configures.
};Close the nested block or value begun earlier. Match it to its opening boundary to keep the structure readable.
fnc show() -> void {Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
wuix.mount("workshop", screen);Ask the supplied native UI service to mount the declared screen at the named host target. Confirm the target exists in the exercise contract.
}Close the nested block or value begun earlier. Match it to its opening boundary to keep the structure readable.
}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 assumption-change record and separate the newly supplied target fact from the unobserved mount outcome.
- 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: Accessible welcome screen. Build a small, understandable change around explain, improve, and resubmit.
Rehearse a project resubmission where the supplied host target changes from main to editorWelcome. Produce the minimal edit and a current evidence-status card.
What to produce
A target-only revision, explicit new contract input and a pending actual-presentation check.
- 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?
Suppose the original brief assumed main, but a future host review reports the only supplied target is workshop. The sample resubmission card says: failed assumption = main exists; new supplied fact = workshop target; source revision = mount workshop; content unchanged; evidence still needed = actual presentation at workshop. This is a hypothetical host report for contract reasoning, not a report that this site ran a host.
Do not retry arbitrary target names until one appears to work without a documented contract. Also avoid changing the text to hide a host-boundary issue. A precise resubmission tells the reviewer what new fact justified the edit and which outcome remains pending.
Original learning-path task and reference
In a research data workstation, demonstrate explain, improve, and resubmit. Add normal, boundary, and invalid-input cases and explain expected behavior. Include .ws source and a host-resource contract; compare at least one normal case and one edge case.
import wuix.widget.button;
import wuix.layout;
domain Login {
const screen = {
layout: { type: "column", padding: [24, 32], gap: 16 },
components: [{ type: "text", value: "Welcome back" }]
};
fnc show() -> void {
wuix.mount("main", screen);
}
}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.
- Rehearse a failed assumption during resubmission
- A resubmission should acknowledge failed assumptions and narrow the claim accordingly. If a supplied host cannot present at the expected target, the right response is to revise the target contract or identify the missing integration, not to keep claiming the screen was shown.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Write one sentence explaining the difference between a new assumption and a supplied host fact.
This marks your personal practice record only. It is not a certification or an official workspace assessment.