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

Separate exposed API from capability permission

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 exposed API from capability permission — Discover and trace

   Make a prediction before touching the example.

   Open practice
   →
2. 2

   Separate exposed API from capability permission — Build the smallest useful slice

   Change one useful behavior while keeping the contract small.

   Open practice
   →
3. 3

   Separate exposed API from capability permission — Change one requirement

   Translate one new mod requirement into a deliberate change.

   Open practice
   →
4. 4

   Separate exposed API from capability permission — Boundary detective

   Find a case the simplest success path does not cover.

   Open practice
   →
5. 5

   Separate exposed API from capability permission — Flash-check repair

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

   Open practice
   →
6. 6

   Separate exposed API from capability permission — Connect the previous skills

   Connect this idea with a previously learned responsibility.

   Open practice
   →
7. 7

   Separate exposed API from capability permission — Review and demonstrate

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

   Open practice
   →