Unit 9 Persistence Test

Close the program. Start it again. Load the data.

Record the evidence that proves the new process recovered state from disk rather than from memory.

Then choose one failure:

• missing file;
• wrong path;
• malformed JSON/CSV;
• unexpected field/value; or
• failed write.

Explain which layer failed: path resolution, file I/O, parsing, validation, or application logic.

End by naming one message or fallback your program provides so the user is not forced to interpret a raw failure without context.