Review consistency, work quotas, and safe background transformations — Boundary detective

PART I

Warm-up

Reconnect with a useful idea before starting review consistency, work quotas, and safe background transformations. 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

Check the exact row boundary

A reporting service needs admission limits for active jobs, rows and intermediate storage. State whether limits apply per job, per owner or globally. Keep progress counters separate from committed results, so a refused or interrupted workload cannot look like a partially successful final report.

Exercise host permits 2 active report jobs per mod, 1000 rows per job and 64 MiB total intermediate memory. JobA reserves 24 MiB and jobB reserves 32 MiB. A third jobC needs 16 MiB. Quotas and counters are explicit exercise contracts, not asserted WDB runtime behavior.

Supplied case: Jobs request 999, 1000 and 1001 rows under an inclusive 1000-row limit.

Worked reasoning: 999 and 1000 fit the row domain;1001 requires refusal or a documented bounded continuation. The requested count is not necessarily the number actually scanned, so the host must also define scan/work accounting if that can exceed output rows.

Contrast and diagnosis: Limiting displayed rows alone may leave unbounded query work behind the scenes.

Worked reasoning and supplied artifact

// Disposable exercise fixture / host-contract notes; not executable API syntax.
// Supplied input: Jobs request 999, 1000 and 1001 rows under an inclusive 1000-row limit.
// Worked prediction: 999 and 1000 fit the row domain;1001 requires refusal or a documented bounded continuation. The requested count is not necessarily the number actually scanned, so the host must also define scan/work accounting if that can exceed output rows.
// Rejected alternative: Limiting displayed rows alone may leave unbounded query work behind the scenes.

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: Concurrent reporting design. Build a small, understandable change around review consistency, work quotas, and safe background transformations.

Prepare requested-output and scanned-row columns for a selective filter; state which work quota the host must measure.

What to produce

Prepare requested-output and scanned-row columns for a selective filter; state which work quota the host must measure. 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.

• Check the exact row boundary
• 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 “Check the exact row boundary” 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.