Compose playback controls, device recovery contracts, and event cleanup — Boundary detective

PART I

Warm-up

Reconnect with a useful idea before starting compose playback controls, device recovery contracts, and event cleanup. 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

Validate volume at its exact limits

Proposed WAUDIO describes native audio integration, including MP3 and WAV rather than MP4 support. Loading, configuration, permission and playback are separate outcomes. Every device or control behavior in these exercises is a supplied host contract; no guessed audio methods or real playback are used.

Exercise audio host accepts volume numeric0..1 inclusive. Invalid values are rejected without changing the current volume0.6; there is no automatic clamping. Inputs are0,1,1.2 and-0.1.

Worked reasoning: Zero and one are accepted boundary values.1.2 and-0.1 are rejected and leave0.6 unchanged in independent tests. Zero is valid muted output, not a missing parameter.

Failed alternative: Using a falsy-default check changes explicit0 to0.6 and violates the users requested mute.

Worked reasoning and supplied artifact

Independent initial volume0.6
Input0 ->accepted volume0
Input1 ->accepted volume1
Input1.2 ->reject,preserve0.6
Input-0.1 ->reject,preserve0.6

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: Media operations console. Build a small, understandable change around compose playback controls, device recovery contracts, and event cleanup.

Classify0,0.25,1 and2 with prior volume0.8. Include a test distinguishing omitted input from explicit zero.

What to produce

A range/default/preserved-state volume table.

• 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 wdb;
domain Inventory {
    const lowStock = wdb.query({
        from: products,
        select: [id, name, stock],
        where: [[ stock < 10 ]],
        order: { by: stock, direction: ascending }
    });
}

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.

• Validate volume at its exact limits
• Classify0,0.25,1 and2 with prior volume0.8. Include a test distinguishing omitted input from explicit zero.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Distinguish absence from the meaningful lower-bound value zero.

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