Rehearse the riskiest integration — Change one requirement

PART I

Warm-up

Reconnect with a useful idea before starting rehearse the riskiest integration. 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

Revise the rehearsal after adding a capability requirement

An integration rehearsal isolates a consequential assumption with disposable inputs, independent expectations and an observation plan. This public site supplies no .ws runtime or native test harness, so the result is a concrete reproducible rehearsal artifact. It must never claim that a paper trace measured host behavior or mutate live user resources to create failure evidence.

The first inventory rehearsal assumes read permission. A new policy restricts kit records by caller. Sample revised matrix runs the same disposable rope/lamp/flask data under authorized and denied callers. The authorized expectation remains the filtered rows; the denied expectation is safe refusal with no record disclosure. Data correctness alone no longer covers the new contract.

Do not create a second dataset with no rows and call that a denied-read test. That would conflate empty authorized data with refused access. Keep the same known records so the authority change is the controlled variable.

Worked reasoning and supplied artifact

// Worked contract artifact:
// The first inventory rehearsal assumes read permission. A new policy restricts kit records by caller. Sample revised matrix runs the same disposable rope/lamp/flask data under authorized and denied callers. The authorized expectation remains the filtered rows; the denied expectation is safe refusal with no record disclosure. Data correctness alone no longer covers the new contract.

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

Create paired caller cases with identical data and identify the one changed precondition.

• 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: Independent WillowScript application. Build a small, understandable change around rehearse the riskiest integration.

Revise the venue-slot rehearsal for a caller permitted to view one venue but denied another existing venue. Supply both records and separate filter correctness from resource authorization.

What to produce

A permission-aware rehearsal matrix with real existing-resource denial conditions and no leaked rows.

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

• Revise the rehearsal after adding a capability requirement
• Create paired caller cases with identical data and identify the one changed precondition.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Create paired caller cases with identical data and identify the one changed precondition.

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