Read lck and ulck exposure policy — Discover and trace

PART I

Warm-up

Reconnect with a useful idea before starting read lck and ulck exposure policy. 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

Read locked exposure as an explicit surface list

The proposed lck/ulck exposure policy controls which host APIs a script can see. Read it as a surface-selection decision, separate from the capability checks on each resource request. This source does not supply a concrete executable manifest schema here, so use explicit policy tables rather than inventing configuration syntax or transferring native linkage assumptions.

The worked policy is locked by default, exposing only a navigation request surface for workshop. Sample surface table: navigation entry visible; internal account administration hidden; capability table separately permits workshop and denies staff-dashboard. The same extension can therefore see one operation while still being unable to reach an unauthorized target.

Locked exposure does not mean no useful script API can ever be provided. The host deliberately exposes the intended narrow entry. Do not write a fictional lck block claiming parser verification; the policy table is the artifact.

Worked reasoning and supplied artifact

// Worked contract artifact:
// The worked policy is locked by default, exposing only a navigation request surface for workshop. Sample surface table: navigation entry visible; internal account administration hidden; capability table separately permits workshop and denies staff-dashboard. The same extension can therefore see one operation while still being unable to reach an unauthorized target.

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

Draw one surface table and one resource-capability table for the worked extension.

• 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: Safe extension design. Build a small, understandable change around read lck and ulck exposure policy.

Specify a locked-default host for a map preview mod, exposing a preview request while hiding account administration. Include a permitted map and a denied map resource.

What to produce

Two explicit tables: visible API surface and resource authorization, labelled as policy design.

• 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;
const button = widget.Button({
    text: "Continue",
    events: {
        click: fnc() -> void {
            navigator.open("dashboard");
        }
    }
});

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.

• Read locked exposure as an explicit surface list
• Draw one surface table and one resource-capability table for the worked extension.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Draw one surface table and one resource-capability table for the worked extension.

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