Organize related declarations with domain — Change one requirement

PART I

Warm-up

Reconnect with a useful idea before starting organize related declarations with domain. 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

Adapt organization for a second consumer

A domain groups related declarations under a meaningful boundary. The shared domain vocabulary expresses organization. Group declarations because they share a coherent responsibility and contract, not because they happen to be called from the same screen. A namespace is not automatically a resource permission boundary, an ownership transfer or a runtime isolation guarantee.

A desktop preview and a batch report both need the same total rule. Currently the helper is nested in a screen-specific design whose other declarations mount native UI. The batch contract has no display resource.

Draw the declarations and their dependencies. Follow one call across a domain boundary and write the input and result contract on that edge. If two domains depend on each other, inspect whether a shared rule or an explicit orchestration layer would make the direction understandable. Worked case: Move or expose the shared rule through a UI-independent Pricing boundary, then let both consumers depend on that contract. The batch report needs the rule without acquiring a requirement to mount the preview screen.

Compare the tempting alternative: Copying the screen-specific module wholesale into batch processing couples an arithmetic task to an unavailable native UI host.

Worked reasoning and supplied artifact

// Paper trace / supplied exercise-host contract; no execution claimed.
// A desktop preview and a batch report both need the same total rule. Currently the helper is nested in a screen-specific design whose other declarations mount native UI. The batch contract has no display resource.
// Move or expose the shared rule through a UI-independent Pricing boundary, then let both consumers depend on that contract. The batch report needs the rule without acquiring a requirement to mount the preview screen.

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: Shared pricing rules. Build a small, understandable change around organize related declarations with domain.

Draw before/after dependency graphs and trace one input subtotal=25, fee=5 through both consumers. Keep result equality distinct from display behavior.

What to produce

A dependency migration graph and two consumer traces predicting 30.

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

fnc add(a: i32, b: i32) -> i32 {
    return a + b;
}
fnc main() -> i32 {
    return add(2, 3);
}

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.

• Adapt organization for a second consumer
• Draw before/after dependency graphs and trace one input subtotal=25, fee=5 through both consumers. Keep result equality distinct from display behavior.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Name the dependency removed from the batch workflow.

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