WillowScript (.ws) is a proposed, not-yet-implemented language. Examples and library integrations here are illustrative design exercises, not verified runnable programs.

Specify bounded storage, cleanup, and shared-service boundaries

Temporary data is not simply “data we hope will disappear.” Decide who owns it, why it exists, how large it may grow, how long it remains useful and what happens when cleanup cannot complete. These choices are part of the feature contract.

1. 1

   Specify bounded storage, cleanup, and shared-service boundaries — Discover and trace

   Make a prediction before touching the example.

   Open practice
   →
2. 2

   Specify bounded storage, cleanup, and shared-service boundaries — Build the smallest useful slice

   Change one useful behavior while keeping the contract small.

   Open practice
   →
3. 3

   Specify bounded storage, cleanup, and shared-service boundaries — Change one requirement

   Translate one new mod requirement into a deliberate change.

   Open practice
   →
4. 4

   Specify bounded storage, cleanup, and shared-service boundaries — Boundary detective

   Find a case the simplest success path does not cover.

   Open practice
   →
5. 5

   Specify bounded storage, cleanup, and shared-service boundaries — Flash-check repair

   Use a plausible mistake to show that you understand the mechanism.

   Open practice
   →
6. 6

   Specify bounded storage, cleanup, and shared-service boundaries — Connect the previous skills

   Connect this idea with a previously learned responsibility.

   Open practice
   →
7. 7

   Specify bounded storage, cleanup, and shared-service boundaries — Review and demonstrate

   Collect a useful learning record without pretending the code was executed.

   Open practice
   →
8. 8

   Module project — Temporary asset workflow

   Turn the section work into one reviewable mod feature.

   Open practice
   →