Plan try, recover, and raise boundaries — Flash-check repair

PART I

Warm-up

Reconnect with a useful idea before starting plan try, recover, and raise boundaries. 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

Repair a catch-all success response

Recover only when the workflow can preserve its promise. try, recover and raise describe error handling in the shared vocabulary, but host operation signatures and error payloads must be supplied. Recovery is a decision about state and responsibility: which failure can be handled locally, which must be reported upward, and which effects have already happened?

A draft says: if any operation fails, recover by setting status Saved. The operation may fail with InvalidInput, PermissionDenied, or UnknownCommitOutcome. No success evidence accompanies these failures.

Use a before-operation-after ledger. Mark the last durable change before a failure and identify the evidence available to the handler. Retrying without knowing whether an operation committed can duplicate effects; swallowing an error cannot turn incomplete work into success. Worked case: Recovery must classify each case: request corrected input, report denied access, or reconcile uncertainty. Saved requires confirmed persistence. A common outer boundary may display safe errors, but it cannot invent completion evidence.

Compare the tempting alternative: Using one optimistic message for all errors conceals both lost work and possible duplicates. The shared vocabulary is recover, not an invented JavaScript catch substitution.

Worked reasoning and supplied artifact

// Paper trace / supplied exercise-host contract; no execution claimed.
// A draft says: if any operation fails, recover by setting status Saved. The operation may fail with InvalidInput, PermissionDenied, or UnknownCommitOutcome. No success evidence accompanies these failures.
// Recovery must classify each case: request corrected input, report denied access, or reconcile uncertainty. Saved requires confirmed persistence. A common outer boundary may display safe errors, but it cannot invent completion evidence.

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 plan try, recover, and raise boundaries.

Replace the catch-all policy with three rows, preserving the draft in every case and naming the next permitted action.

What to produce

A failure-class response table and a separate confirmed-success criterion.

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

• Repair a catch-all success response
• Replace the catch-all policy with three rows, preserving the draft in every case and naming the next permitted action.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Choose an accurate status for PermissionDenied.

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