The compounding session
Year one: privacy list off a blog. Year two: “startup fix” someone linked on Reddit. Each change alone defensible; the combination is unmeasured, and nobody remembers provenance when Explorer renders strangely. The failure mode isn't technical; it's ledgerless administration.
The loan discipline
- Principal recorded: before-image value (see the write pattern);
- Interest visible: effect, even if subjective — logged with the change note;
- Redemption path exercised: restore path actually run once during trial, so draining a tweak is proven mechanical, not aspirational.
Batching beats drip
Gather a session's changes, review them on one screen, apply as a single operation with per-value journaling, undo as a unit. Twenty sessionless edits weren't tuning; it was sedimentation. Preview evaluators get this at its strictest: each preset is one journaled batch, restore one click, all defaults documented.
ProofTune ProjectEngineering notes — every claim here names the bytes a real tool touches. Verify first, install second.