Continuity as a filesystem problem

Build lab (Module 6, L6.7): a new session reads; it does not remember. Session 1 finishes 4 of 6 units of "add rate limiting" and is killed. Resumed from a fluent prose summary, session 2 redoes 3 finished units and never does the metrics unit; resumed from state (an append-only progress log, a task list with proof pointers and the commits) it picks T5 with 0 redone and 0 violations. Verify before acting catches a planted "done" with a missing proof file; a stub proof still passes, because cross-check proves existence, not adequacy. In-memory log, task list and repo only; no real files or git.

This Harness Engineering lesson is part of a paid plan. Sign in with a plan that includes this course to read it.