Separate symbolic and numerical work — Build the smallest useful slice

PART I

Warm-up

Reconnect with a useful idea before starting separate symbolic and numerical work. 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.

Recall note

A rough note is enough. You can revise it after the example.

PART II

Instruction & guided example

Do not mistake a decimal approximation for an identity

An engineer compares sqrt(2) with the decimal 1.414. The source proposes symbolic and numerical work but supplies no running solver.

Squaring the decimal yields 1.999396, which is close to 2 but unequal. The symbolic quantity sqrt(2) retains an exact relationship; its displayed decimal rounds it. For a UI tolerance of 0.001, the difference from 2 after squaring is 0.000604 and fits that supplied tolerance. Equality and tolerance are distinct tests.

Use the supplied case as a paper design exercise. WillowScript and these library integrations are proposed and unimplemented here; no interpreter or native host has checked the example. Preserve the source API spellings, label new policies as exercise-host contracts, and distinguish a predicted result from measured execution.

Worked reasoning and supplied artifact

// PAPER FIXTURE — Do not mistake a decimal approximation for an identity
// Manual worked artifact; comments below are not executable source.
// INPUT / CONTRACT: An engineer compares sqrt(2) with the decimal 1.414. The source proposes symbolic and
// numerical work but supplies no running solver.
// DERIVATION / EXPECTED ARTIFACT: Squaring the decimal yields 1.999396, which is close to 2 but unequal.
// The symbolic quantity sqrt(2) retains an exact relationship; its displayed decimal rounds it. For a UI
// tolerance of 0.001, the difference from 2 after squaring is 0.000604 and fits that supplied tolerance.
// Equality and tolerance are distinct tests.

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.

Walk through the example, one line at a time

// PAPER FIXTURE — Do not mistake a decimal approximation for an identity
This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// Manual worked artifact; comments below are not executable source.
This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// INPUT / CONTRACT: An engineer compares sqrt(2) with the decimal 1.414. The source proposes symbolic and
This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// numerical work but supplies no running solver.
This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// DERIVATION / EXPECTED ARTIFACT: Squaring the decimal yields 1.999396, which is close to 2 but unequal.
This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// The symbolic quantity sqrt(2) retains an exact relationship; its displayed decimal rounds it. For a UI
This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// tolerance of 0.001, the difference from 2 after squaring is 0.000604 and fits that supplied tolerance.
This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// Equality and tolerance are distinct tests.
This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.

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.

Prediction or guided notes

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.

Your drafts remain here. Continue whenever you are ready.

PART IV

Independent practice

Project context: Estimator specification. Build a small, understandable change around separate symbolic and numerical work.

Write an exact-versus-approximate evidence note using 1.41 and 1.414, their squares, and the same tolerance.

What to produce

Write an exact-versus-approximate evidence note using 1.41 and 1.414, their squares, and the same tolerance.

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.

Your .ws practice draft

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.

Need a hint?

Rounding can make a useful approximation without creating an exact identity. Start by writing the distinct intermediate states or arithmetic before changing the source.

Yes because the display rounds it is the tempting incorrect conclusion in this case. Rounding can make a useful approximation without creating an exact identity.

Original learning-path task and reference

In a museum exhibit console, demonstrate separate symbolic and numerical work. Create the smallest .ws integration that demonstrates the section contract. Include .ws source and a host-resource contract; compare at least one normal case and one edge case.

import math;
domain Calculation {
    fnc sample() -> void {
        vary x: i32 = 2;
        vary value = [[ (x * 5) + 20 ]];
    }
}

Where the original task needs a host API that is not supplied here, write the contract and predictions. Do not invent a runtime result.

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.

Does 1.414 squared equal exactly 2?No; it is 1.999396Yes because the display rounds it

Explain a normal or boundary case

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.

Do not mistake a decimal approximation for an identity
An engineer compares sqrt(2) with the decimal 1.414. The source proposes symbolic and numerical work but supplies no running solver.
Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Explain why “Yes because the display rounds it” fails for the supplied case, then give one changed input that would require revisiting your conclusion.

Your recap

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