Answer A-169: one key form for every holder of pins

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 19f969b2db
commit a2f2e5b98d
1 changed files with 4 additions and 0 deletions
@@ -635,3 +635,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-168** (E §33, design 46 approval mark §5; principle 3) For a marked wait on a module the runner does not serve,
  the marks are the union of the newest entry of every followed branch; where the runner serves the module, its
  served entry is added to that union. A mark is never lost.
+- **A-169** (§579; principles 2 and 7) A pins state keys a revision by the revision object's own name (the assigner's
+  `trunk.<n>`, the indexer's `<branch>.<revision>`), value `{records, missing?}`, and holds two more keys in the same
+  form in every holder of pins: `made`, written once by create-only when the state is first used, and
+  `pins-stated`, the `at` of the applied event; pins count only once a `pins-stated` later than `made` is applied.