Coordinate recovery manifests, eviction, and active handles — Build the smallest useful slice

PART I

Warm-up

Reconnect with a useful idea before starting coordinate recovery manifests, eviction, and active handles. 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

Build an observation checklist

A recovery rehearsal is useful when an observer can tell which state survived, what was refused and which resources were retained. Design fault points and expected outcomes before implementation so the evidence cannot merely repeat whatever the candidate happened to do.

Exercise workload: generate report R from input I at revision 30; output C is 60 MiB under a 100 MiB store budget. Fault points are before generation, halfway through C, after validation and after durable publication. No actual fault injection, benchmark or host execution is supplied by this site.

Supplied case: Fault injection is planned after validation but before durable publication. C is complete; no publication record is durable.

Worked reasoning: Observe complete candidate bytes, preserved input, absent published revision and truthful pending/interrupted UI. These observations test the boundary rather than relying on a process exit code.

Contrast and diagnosis: A zero exit code from a launcher cannot substitute for the durable state the exercise is about.

Worked reasoning and supplied artifact

// Disposable exercise fixture / host-contract notes; not executable API syntax.
// Supplied input: Fault injection is planned after validation but before durable publication. C is complete; no publication record is durable.
// Worked prediction: Observe complete candidate bytes, preserved input, absent published revision and truthful pending/interrupted UI. These observations test the boundary rather than relying on a process exit code.
// Rejected alternative: A zero exit code from a launcher cannot substitute for the durable state the exercise is about.

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: Recovery rehearsal workspace. Build a small, understandable change around coordinate recovery manifests, eviction, and active handles.

Write four expected observations for the pre-publication fault and specify where a real host would collect each one.

What to produce

Write four expected observations for the pre-publication fault and specify where a real host would collect each one. Include input → intermediate decision/state → predicted outcome, with any required host rule stated explicitly.

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

• Build an observation checklist
• Explain the decision for the supplied case, then independently work the changed fixture.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

In one or two sentences, name the decisive rule in “Build an observation checklist” and predict the outcome of one changed input from your independent fixture. State which host behavior still needs real verification.

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