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

Separate visibility from permissions

Being able to name an API does not mean the script is allowed to use every resource behind it. Exposure asks which API is visible to the script. Capability permission asks which operations and resources the host authorizes for this particular execution.

1. 1

   Separate visibility from permissions — Discover and trace

   Make a prediction before touching the example.

   Open practice
   →
2. 2

   Separate visibility from permissions — Build the smallest useful slice

   Change one useful behavior while keeping the contract small.

   Open practice
   →
3. 3

   Separate visibility from permissions — Change one requirement

   Translate one new mod requirement into a deliberate change.

   Open practice
   →
4. 4

   Separate visibility from permissions — Boundary detective

   Find a case the simplest success path does not cover.

   Open practice
   →
5. 5

   Separate visibility from permissions — Flash-check repair

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

   Open practice
   →
6. 6

   Separate visibility from permissions — Connect the previous skills

   Connect this idea with a previously learned responsibility.

   Open practice
   →
7. 7

   Separate visibility from permissions — Review and demonstrate

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

   Open practice
   →