Propose a host-neutral application contract — Change one requirement

PART I

Warm-up

Reconnect with a useful idea before starting propose a host-neutral application contract. 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

Change a data requirement without silently changing authority

A host-neutral application contract describes user goals, supplied data, services, permissions, lifetime and evidence before choosing environment-specific integrations. The source’s Application constructor and app.ready callback are illustrative host inputs, not builtins supplied by this school. A Willow learner can reuse precise state reasoning while keeping proposed .ws and conceptual native services distinct from implemented .w.

The planner initially displays fixed kit guidance. A revision requests a live stock summary. Sample change record: new resource = host-supplied kit inventory; new field contract = item identifier/name/available count; new capability = read permitted kit records; unchanged = orientation purpose and existing window contract. A successful fixed-text draft does not establish any of these data prerequisites.

Do not infer that an Application window can read all host data. Even a source-named WDB import would not supply the collection or permission. The revision must specify a denied-read outcome and avoid presenting unavailable data as a verified zero count.

Worked reasoning and supplied artifact

// Worked contract artifact:
// The planner initially displays fixed kit guidance. A revision requests a live stock summary. Sample change record: new resource = host-supplied kit inventory; new field contract = item identifier/name/available count; new capability = read permitted kit records; unchanged = orientation purpose and existing window contract. A successful fixed-text draft does not establish any of these data prerequisites.

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

Build a before/after contract table including new data, service and permission obligations.

• 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: Independent WillowScript application. Build a small, understandable change around propose a host-neutral application contract.

Revise a fixed tournament schedule application to request venue availability. Specify the supplied dataset, necessary fields, authorized scope and denied-resource behavior.

What to produce

A feature-delta table with concrete input schema and a separate resource authority requirement.

• 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;
import app;
domain Workspace {
    const application = Application({
        name: "Workspace",
        window: { title: "Dashboard", size: [1280, 800] },
        events: {
            "app.ready": fnc() -> void { console.log("Ready"); }
        }
    });
}

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.

• Change a data requirement without silently changing authority
• Build a before/after contract table including new data, service and permission obligations.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Build a before/after contract table including new data, service and permission obligations.

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