Build the Advanced final project — Open knowledge review

PART I

Warm-up

Reconnect with a useful idea before starting build the advanced final project. 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

Review the project for contradictory contracts

A final project should produce a small coherent design whose behavior another learner can trace. Choose explicit bounds and refusal paths rather than combining every conceptual library at once. This public project is open practice; it does not run a private exam, certify code or require a fabricated runtime.

Project brief: a read-only low-stock report for approved PublicProducts, threshold 5, one report at a time, 32 MiB memory limit and 20 MiB cache quota. Fixture A stock 0, B stock 4, C stock 5. Native UI shows status and results; audio is optional. Export and mutation are out of scope.

Supplied case: One note says cache failure blocks report publication; another says every completed transform always reports ready.

Worked reasoning: Resolve the contradiction by naming the publication precondition. If a valid cache is required, transform complete/cache failed is not ready. Use one authoritative state table for UI, resource and failure behavior.

Contrast and diagnosis: Keeping both rules makes tests ambiguous and lets implementation choose whichever passes.

Worked reasoning and supplied artifact

// Disposable exercise fixture / host-contract notes; not executable API syntax.
// Supplied input: One note says cache failure blocks report publication; another says every completed transform always reports ready.
// Worked prediction: Resolve the contradiction by naming the publication precondition. If a valid cache is required, transform complete/cache failed is not ready. Use one authoritative state table for UI, resource and failure behavior.
// Rejected alternative: Keeping both rules makes tests ambiguous and lets implementation choose whichever passes.

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 build the advanced final project.

Write a four-state table: working, transform complete/cache pending, cache committed and cache failed. Give a single readiness decision for each.

What to produce

Write a four-state table: working, transform complete/cache pending, cache committed and cache failed. Give a single readiness decision for each. 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.

• Review the project for contradictory contracts
• 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 “Review the project for contradictory contracts” 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.