Build the Intermediate final project — Review and demonstrate

PART I

Warm-up

Reconnect with a useful idea before starting build the intermediate 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

Review the final design against adversarial timing

A final project needs failure behavior as well as a success path. Build a small coherent system before adding breadth. The utility must say what happens when inputs are invalid, resources are denied, results arrive late or an operation has unknown outcome. A complete paper specification can explain those cases while honestly marking missing runtime support.

Review schedule: ready at t=1, draft load t=3, two submit deliveries t=4 and t=5, window close t=6, host confirmation t=8. The contract permits one operation per stable request identity.

Use stable identities for owners and operations, a narrow dependency inventory, and a state ledger for each effect. Validate the claim at the layer that owns it; source organization cannot establish resource permission, and a visible success label cannot establish durable completion. Worked case: At t=1 input is not ready. At t=3 the action can enable. The first submit marks the identity Pending before initiation; the second is suppressed. Close ends UI ownership; confirmation records the service outcome without updating the closed window.

Compare the tempting alternative: A happy-path-only demonstration misses four distinct risks: premature action, duplicate effect, lost operation identity and late cross-owner updates.

Worked reasoning and supplied artifact

// Paper trace / supplied exercise-host contract; no execution claimed.
// Review schedule: ready at t=1, draft load t=3, two submit deliveries t=4 and t=5, window close t=6, host confirmation t=8. The contract permits one operation per stable request identity.
// At t=1 input is not ready. At t=3 the action can enable. The first submit marks the identity Pending before initiation; the second is suppressed. Close ends UI ownership; confirmation records the service outcome without updating the closed window.

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.

Try the guided change

Reconstruct the supplied worked case first: list its inputs, intermediate decisions and final artifact. Compare each row with the explanation and identify exactly where the rejected alternative fails. Then use the changed inputs in Part IV for independent work.

• 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: Event-driven team utility. Build a small, understandable change around build the intermediate final project.

Create a complete time/state/effect ledger and state the required host guarantees separately from your application decisions.

What to produce

An eight-timepoint review trace and a host-versus-application responsibility list.

• 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.

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"); }
        }
    });
}

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.

• Review the final design against adversarial timing
• Create a complete time/state/effect ledger and state the required host guarantees separately from your application decisions.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Name the state written before initiating the first operation.

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