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

Design stable public module boundaries

An integration is a set of relationships, not merely a long import list. For each service, say what the script asks for, which input it supplies, which result it expects and which permission/lifetime boundary applies.

1. 1

   Design stable public module boundaries — Discover and trace

   Make a prediction before touching the example.

   Open practice
   →
2. 2

   Design stable public module boundaries — Build the smallest useful slice

   Change one useful behavior while keeping the contract small.

   Open practice
   →
3. 3

   Design stable public module boundaries — Change one requirement

   Translate one new mod requirement into a deliberate change.

   Open practice
   →
4. 4

   Design stable public module boundaries — Boundary detective

   Find a case the simplest success path does not cover.

   Open practice
   →
5. 5

   Design stable public module boundaries — Flash-check repair

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

   Open practice
   →
6. 6

   Design stable public module boundaries — Connect the previous skills

   Connect this idea with a previously learned responsibility.

   Open practice
   →
7. 7

   Design stable public module boundaries — Review and demonstrate

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

   Open practice
   →
8. 8

   Design stable public module boundaries — Alternative solution challenge

   Turn the section work into one reviewable mod feature.

   Open practice
   →