Final project — Operations reporting utility

PART I

Warm-up

Reconnect with a useful idea before starting build the professional 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

Deliver an evidence-backed operations reporting design

An operations report must explain where every claim came from. A complete reporting design states source data scope, transformation rules, numerical assumptions, UI behavior, optional notifications and retained artifacts. It also specifies denial, empty results, stale results, capacity pressure and unknown outcomes. Public review remains personal self-study, not private certification.

Final design uses team-A authorized rows, explicit stock threshold, projected fields, one coherent snapshot, native result owner, bounded temporary artifacts and optional sound. Test data includes stocks 0,4,5,9 and threshold 5; no native host is supplied.

Build one audit trail from supplied rows to the final artifact. Each transition needs an owner and a justified result. Mark paper calculations, conceptual API usage and absent host guarantees clearly, then choose boundary cases that could actually falsify the design. Worked case: Expected selected stocks are 0 and 4. Build the final artifact from those rows, carry threshold and snapshot metadata, and label every calculation as predicted. Add denied scope, empty success, timeout, stale fallback, quota pressure and late-owner cases to establish the design’s breadth honestly.

Compare the tempting alternative: A long source file or a complete set of lesson URLs cannot substitute for the case evidence. A final report should say precisely which behavior was reasoned through and which implementation remains unavailable.

Worked reasoning and supplied artifact

// Paper trace / supplied exercise-host contract; no execution claimed.
// Final design uses team-A authorized rows, explicit stock threshold, projected fields, one coherent snapshot, native result owner, bounded temporary artifacts and optional sound. Test data includes stocks 0,4,5,9 and threshold 5; no native host is supplied.
// Expected selected stocks are 0 and 4. Build the final artifact from those rows, carry threshold and snapshot metadata, and label every calculation as predicted. Add denied scope, empty success, timeout, stale fallback, quota pressure and late-owner cases to establish the design’s breadth honestly.

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: Operations reporting utility. Build a small, understandable change around build the professional final project.

Assemble the report specification, data derivation, dependency/capability table, lifetime graph and seven acceptance ledgers. Explain one repaired defect and list the remaining parser/host validation gaps.

What to produce

A complete reviewable design packet with seven distinct cases and explicit execution limits.

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

• Deliver an evidence-backed operations reporting design
• Assemble the report specification, data derivation, dependency/capability table, lifetime graph and seven acceptance ledgers. Explain one repaired defect and list the remaining parser/host validation gaps.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Write the strongest supported conclusion and one unresolved implementation question.

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