Answer A-36: mesh-sdk's calls words and the TS follower, as built

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
2026-11-11 22:06:49 +01:00
parent 2b731e1141
commit 9d57887357
1 changed files with 4 additions and 0 deletions
@@ -131,3 +131,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `acts` with when it was said, and ended there on `owed.ended`, so `stalled` reads the unanswered ones.
  `approval-carried` and `approval-carried-open` are design lines (§542, §592), not left out: they are built, with the
  `pull-merged` and `pull-closed` consumes that clear the finding.
+- **A-36** (§622, §643, A-21, A-22; principle 7) As built in mesh-sdk a59ccad8: the Go package's `calls` are the four
+  words its calls need (`ledger-upkeep-calls`, `sent-objects-calls`, `put-sessions`, `finding-calls`), the npm package's
+  `finding-calls` alone; the npm package makes no session, so its `state.put` refuses a value over one chunk, naming
+  it. A-22 holds for TypeScript too: the TS follower keeps no plain-field `Finding` of its own beside the writer.