Answer A-58: an owner change is its own change value

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 22:45:57 +01:00
parent ac217628a1
commit 5b54cfdad1
1 changed files with 4 additions and 0 deletions
@@ -223,3 +223,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `resolved` and `toolchain` from the step's result (`dependencies`, §673), `branch` the watched branch of the catalog
  revision whose entry the build came from, and `source` that revision, both kept on the build's reservation from the
  candidate it built.
+- **A-58** (§540, §685, §8; principle 8, one word per thing) An owner change is said as `condition-changed` with a new
+  `change` value `owner`, added to the seat `mesh-conditions`' enum in mesh-contracts; `words` stays for a change of the
+  text. `seed-waits` waits on the operator through the finding's own `waiting-on`, which the indexer sets and the keeper
+  copies, with no rule of the keeper's for that kind.