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

Define crash-recovery evidence

A recovery plan begins by defining the work that must survive failure. Distinguish committed data, in-progress changes and replaceable output. A backup is useful only when its scope, consistency and restoration procedure are understood.

1. 1

   Define crash-recovery evidence — Discover and trace

   Make a prediction before touching the example.

   Open practice
   →
2. 2

   Define crash-recovery evidence — Build the smallest useful slice

   Change one useful behavior while keeping the contract small.

   Open practice
   →
3. 3

   Define crash-recovery evidence — Change one requirement

   Translate one new mod requirement into a deliberate change.

   Open practice
   →
4. 4

   Define crash-recovery evidence — Boundary detective

   Find a case the simplest success path does not cover.

   Open practice
   →
5. 5

   Define crash-recovery evidence — Flash-check repair

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

   Open practice
   →
6. 6

   Define crash-recovery evidence — Connect the previous skills

   Connect this idea with a previously learned responsibility.

   Open practice
   →
7. 7

   Define crash-recovery evidence — Review and demonstrate

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

   Open practice
   →