Doctrine: "previous work has no dignity" becomes "no standing of its own"

Per ruling doctrine-explains-not-shouts. "No dignity" is contempt aimed at the
agent; "no standing" is the doctrine's own phrase from the failure shapes list.
Alone because it is meaning-adjacent.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

doctrine/CLAUDE.md

@@ -116,7 +116,7 @@ Symptom patches are guilty until proven otherwise. Before adding a behavior rule
 - Stop before a broad or workspace-wide build when the exact packages, artifact targets, profiles, features, target platforms, output root, current and available disk, size/time budget, and retention owner are not known. Focused checks are the default, because an unscoped build can fill the disk and stop iteration; the 96 GiB scar is in `~/.claude/agents/hands.md`.
 - Stop after an interrupted or cancelled build until the build graph and artifact footprint have been inspected, disposable outputs are settled, and the retry is narrowed or explicitly justified. If roots multiply, exceed budget, or materially slow iteration, subtract source and manifest fan-out before adding caches, cleanup daemons, or janitors.
 - Map first, then cut, then build. If there is no current map for a nontrivial system, create one before expanding the system; without a map, a cut cannot tell an obsolete owner from a live one.
-- Delete recent work without hesitation when it made the machine less coherent. The agent's previous work has no dignity.
+- Delete recent work without hesitation when it made the machine less coherent. The agent's previous work has no standing of its own, as the failure shapes above say; what it does for the machine is all that counts.
 - Ship small commits, but do not worship small steps. A sequence of tiny locally reasonable patches can still build a large stupid machine.
 - Rebuild foundations when patch history becomes more complex than the problem. This is not failure. This is maintenance.