Write the utility acceptance contract — Review and demonstrate

PART I

Warm-up

Reconnect with a useful idea before starting write the utility acceptance contract. 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 contract coverage with a counterexample

An acceptance contract makes a feature claim falsifiable. A feature description becomes reviewable when it names supplied inputs, required effects, visible outcomes and failure boundaries. Separate what source vocabulary expresses, what an exercise host must guarantee, and what a paper trace merely predicts. Public practice can be completed manually; it does not certify code execution.

A review packet has normal submit, empty-title rejection and audio fallback cases. It has no observer submit case or late response after close. The utility claims secure, lifecycle-safe submission.

For each requirement, choose an ordinary case and a case that would expose a plausible wrong implementation. Name the expected artifact or state change and the evidence that would establish it. A list of attractive screens is not a substitute for observable behavior. Worked case: The existing cases support input handling and optional notification, but do not exercise authorization or owner lifetime. Add an observer’s denied direct request and a response for a closed composer. Each targets a different plausible failure.

Compare the tempting alternative: Counting three cases as “enough” without relating them to claims treats quantity as coverage and leaves important promises unexamined.

Worked reasoning and supplied artifact

// Paper trace / supplied exercise-host contract; no execution claimed.
// A review packet has normal submit, empty-title rejection and audio fallback cases. It has no observer submit case or late response after close. The utility claims secure, lifecycle-safe submission.
// The existing cases support input handling and optional notification, but do not exercise authorization or owner lifetime. Add an observer’s denied direct request and a response for a closed composer. Each targets a different plausible failure.

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 write the utility acceptance contract.

Build a claim-to-case map and add two discriminating traces. Mark which claims remain paper predictions without a host.

What to produce

A coverage matrix with authorization and lifetime counterexamples.

• 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 contract coverage with a counterexample
• Build a claim-to-case map and add two discriminating traces. Mark which claims remain paper predictions without a host.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Name one case that would falsify the lifecycle-safety claim.

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