Exercise 1: The Parallel Between This Chapter's Claim and backup1's Own Claim — Possible Solution ==================================================================== WHAT backup1's CENTRAL CLAIM WAS ------------------------------ Per backup1's own Chapter 1, "a backup job reporting 'success' confirms exactly one thing: data was copied somewhere. It confirms nothing about whether that copy is complete, uncorrupted, or genuinely restorable into a working state." Existing and working were treated as two separate claims, verified by two separate means - only a real test restore proves the second. WHAT THIS CHAPTER'S OWN CLAIM SAYS ------------------------------ Per this chapter, "'we wrote it down' confirms only that words exist in a document somewhere. It confirms nothing about whether those words are complete, accurate, still current, or genuinely followable by someone who isn't already the expert who wrote them." The same structure: existing and working are treated as two separate claims. WHY THE SAME LOGICAL STRUCTURE APPLIES TO BOTH ------------------------------ In both cases, the artifact in question (a backup file, a written document) can be produced correctly - genuinely, honestly created - while still failing at its actual purpose once someone depends on it. A backup can copy data perfectly while still being unrestorable due to a missing dependency; a document can be written accurately by its author while still being unfollowable by someone without that author's own background knowledge. Neither failure shows up by inspecting the artifact itself - both only show up when someone actually tries to use it for real. WHY ONLY A REAL TEST PROVES THE SECOND CLAIM, IN BOTH CASES ------------------------------ backup1 established that only an actual restore attempt - not a completion status - proves a backup works. This chapter (per its own tip-box) makes the identical argument: only someone genuinely unfamiliar with the system successfully following the document proves it actually works, not the fact that it was written and reviewed by its own author. WHY THIS ISN'T JUST A STYLISTIC ECHO ------------------------------ Both arguments rest on the same underlying principle: an artifact's own internal correctness (data copied correctly; words written clearly by someone who understands the system) doesn't guarantee it achieves its actual purpose for someone who depends on it under different conditions than the person who created it. WHY THIS WORKS AS AN ANSWER ------------------------------ It states both chapters' own central claims side by side, explains the shared underlying structure (an artifact can be correctly produced yet still fail its actual purpose), and explains why only a genuine, independent test - not the artifact's own existence - proves either one actually works.