Write resource and permission acceptance cases — Alternative solution challenge

PART I

Warm-up

Reconnect with a useful idea before starting write resource and permission acceptance cases. 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

Deliver the acceptance-case matrix

An acceptance case starts from a written requirement and supplied inputs, then predicts a visible outcome and preserved state. Use cases that isolate one rule at a time before combining them. The public school offers manual learning checks; these cases are a test design for a future host, not an official Advanced certification.

Exercise automation host: each mod may run 2 jobs, total reserved memory may not exceed 96 MiB, and reports may read PublicData only. Export requires a separate explicit grant. Current jobA reserves 40 MiB and jobB reserves 32 MiB. These are disposable fixtures, not live jobs or policy changes.

Supplied case: Final review needs normal, count-only, memory-only, exact-fit, denied-resource and denied-export cases.

Worked reasoning: Keep distinct columns for requested actions, passing/failing predicates, visible status and preserved side effects. A real host integration can later fill observed results; the public lesson should leave those unclaimed.

Contrast and diagnosis: A table of six success messages is not six independent boundary tests.

Worked reasoning and supplied artifact

// Disposable exercise fixture / host-contract notes; not executable API syntax.
// Supplied input: Final review needs normal, count-only, memory-only, exact-fit, denied-resource and denied-export cases.
// Worked prediction: Keep distinct columns for requested actions, passing/failing predicates, visible status and preserved side effects. A real host integration can later fill observed results; the public lesson should leave those unclaimed.
// Rejected alternative: A table of six success messages is not six independent boundary tests.

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: Bounded automation workspace. Build a small, understandable change around write resource and permission acceptance cases.

Submit six cases with computed totals and authorization decisions, plus one host-accounting question. Mark evidence as predicted until actually observed.

What to produce

Submit six cases with computed totals and authorization decisions, plus one host-accounting question. Mark evidence as predicted until actually observed. 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 tmp;
const cache = tmp.create({
    name: "report-cache",
    storage: "ssd",
    maxSize: "2GB",
    lifetime: { duration: "30m", refreshOnAccess: true },
    cleanup: { automatic: true, onCrashRecovery: true }
});

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.

• Deliver the acceptance-case matrix
• 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 “Deliver the acceptance-case matrix” 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.