Module project — Temporary asset workflow

PART I

Warm-up

Reconnect with a useful idea before starting specify bounded storage, cleanup, and shared-service 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

Design a shared temporary asset workflow

Shared resources require scoped owners and permissions. A shared temporary service serves several consumers with separate identities, quotas and lifetimes. Sharing a storage backend does not merge resource authority. A host contract must validate handles, prevent cross-owner effects and say how aggregate pressure interacts with per-owner promises.

Project resources: team-A asset source is durable; preview P84 is 12 MB temporary; intermediate I84 peaks at 20 MB; two owners may share P84. Service quota is 80 MB with 40 MB already active. Preview expires for new leases after 15 minutes.

Draw owner→resource edges and trace one operation through identity, scope, quota and lifetime checks. Separate releasing one consumer’s reference from deleting an object still needed by others. Unknown sharing semantics must remain explicit requirements, not guessed reference-count or cancellation APIs. Worked case: Generation peak needs 40+20+12=72 MB if intermediate and output overlap, leaving 8 MB. The durable source is outside cleanup scope. Shared preview deletion waits for valid owners to release or leases to expire, while logical expiry blocks new leases. Cleanup failure remains an explicit state.

Compare the tempting alternative: Counting only the final preview, deleting the durable source, or releasing a shared object on first close each violates a different contract.

Worked reasoning and supplied artifact

// Paper trace / supplied exercise-host contract; no execution claimed.
// Project resources: team-A asset source is durable; preview P84 is 12 MB temporary; intermediate I84 peaks at 20 MB; two owners may share P84. Service quota is 80 MB with 40 MB already active. Preview expires for new leases after 15 minutes.
// Generation peak needs 40+20+12=72 MB if intermediate and output overlap, leaving 8 MB. The durable source is outside cleanup scope. Shared preview deletion waits for valid owners to release or leases to expire, while logical expiry blocks new leases. Cleanup failure remains an explicit state.

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: Temporary asset workflow. Build a small, understandable change around specify bounded storage, cleanup, and shared-service boundaries.

Produce budget, identity, permission, expiry and cleanup specifications with cases for normal use, second owner, capacity rejection, crash and late cleanup acknowledgment.

What to produce

A resource graph, peak calculation and five lifetime/failure ledgers.

• 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 wdb;
domain Inventory {
    const lowStock = wdb.query({
        from: products,
        select: [id, name, stock],
        where: [[ stock < 10 ]],
        order: { by: stock, direction: ascending }
    });
}

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.

• Design a shared temporary asset workflow
• Produce budget, identity, permission, expiry and cleanup specifications with cases for normal use, second owner, capacity rejection, crash and late cleanup acknowledgment.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Name the resource that must never enter temporary cleanup scope.

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