Module project — Safe extension design

PART I

Warm-up

Reconnect with a useful idea before starting choose a failure response for a workflow. 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

Design the safe extension end to end

Choose a response from the failure’s consequences. A useful failure response preserves valid work and tells the user what is known. Retry, fall back, reject, and ask for a new input serve different purposes. Choose them from the operation’s contract, not merely from the desire to show a green success message.

Final exercise: a mod exposes previewReport and submitReport for team A. Only summary data is readable. Observer may preview but not submit. A submit can confirm, reject before write, or time out with unknown outcome. The composing window can close at any time.

Write a response table containing failure class, known state, permitted next action, and user-visible message. Unknown outcome is its own state. It is unsafe to collapse it into either confirmed success or confirmed failure without checking evidence. Worked case: A sound design checks exposure, resource scope and current action grant, then binds submission to a stable operation identity. Confirmed submit transfers durable ownership to the service. Denied requests have no write; uncertain requests preserve identity for reconciliation; a closed window cannot receive late UI updates.

Compare the tempting alternative: One generic “success/failure” flag cannot represent denied, confirmed, unknown, and owner-closed states. Adding more UI controls cannot substitute for the host boundaries those states require.

Worked reasoning and supplied artifact

// Paper trace / supplied exercise-host contract; no execution claimed.
// Final exercise: a mod exposes previewReport and submitReport for team A. Only summary data is readable. Observer may preview but not submit. A submit can confirm, reject before write, or time out with unknown outcome. The composing window can close at any time.
// A sound design checks exposure, resource scope and current action grant, then binds submission to a stable operation identity. Confirmed submit transfers durable ownership to the service. Denied requests have no write; uncertain requests preserve identity for reconciliation; a closed window cannot receive late UI updates.

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: Safe extension design. Build a small, understandable change around choose a failure response for a workflow.

Produce a compact specification and five traces: allowed preview, denied observer submit, confirmed submit, timeout then close, and late confirmation after close. Include exact public messages and explicitly unresolved host APIs.

What to produce

An operation inventory, grant matrix, state machine, five acceptance ledgers and source-versus-host status notes.

• 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;
const button = widget.Button({
    text: "Continue",
    events: {
        click: fnc() -> void {
            navigator.open("dashboard");
        }
    }
});

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.

• Design the safe extension end to end
• Produce a compact specification and five traces: allowed preview, denied observer submit, confirmed submit, timeout then close, and late confirmation after close. Include exact public messages and explicitly unresolved host APIs.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

State the single most important host guarantee still missing from your design.

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