docs: introduce CLAW acronym (Commits as Ledger of All Work)

docs/architecture.md

@@ -212,9 +212,10 @@ sync-branch: beads-sync    # Separate branch for beads commits
 
 **Why sync-branch?** When multiple agents share a beads database, using a dedicated sync branch prevents beads commits from interleaving with code commits on feature branches.
 
-#### Beads as Data Plane
+#### Beads as Data Plane (CLAW)
 
-Gas Town uses Beads for persistence. We've combined the data plane and control plane:
+Gas Town uses Beads for persistence - **C**ommits as **L**edger of **A**ll **W**ork.
+We've combined the data plane and control plane:
 - Traditional systems separate "what's stored" from "what to do next"
 - We store both in beads, so agent state survives crashes
 

docs/beads-data-plane.md

@@ -1,4 +1,4 @@
-# Beads as Data Plane
+# Beads as Data Plane (CLAW)
 
 > **Status**: Design documentation
 > **See also**: [pinned-beads-design.md](pinned-beads-design.md), [propulsion-principle.md](propulsion-principle.md)
@@ -6,6 +6,11 @@
 ## Overview
 
 Gas Town agents coordinate through **Beads** - a git-backed issue tracker.
+
+**CLAW**: **C**ommits as **L**edger of **A**ll **W**ork. Git commits are the persistence
+mechanism. Every state change becomes a commit, giving us atomic updates, full history,
+and distributed sync for free.
+
 We store agent state (work assignments, mail, molecules, hooks) as beads issues.
 
 ## How We Use It