Answer A-208: the indexer writes the edges; every branch takes in as the trunk does

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 456a1eae45
commit af25c1424f
1 changed files with 6 additions and 0 deletions
@@ -115,3 +115,9 @@ the principle that settles it, cited as "design 47 G A-n".
  catalog seat's `revision` of the candidate against the branch's newest (the serving parts' entries and fingerprints,
  found by holder from the seat list; the acting rules `step`, `on` and `bound` and the credentials the entries
  declare), and the grants part's `grants-for` (the permissions); no other verb.
+- **A-208** (ADR 0656, §558, §605, §16, §293, §600, §18, §104, §44-§46, A-93, A-190; principle 7) The indexer writes a
+  catalog entry's edges of kinds 1 to 6, as the catalog graph is its own; the long form of `invokes` is read by the
+  second reader release's `InvokeFields`, which G merges. Every watched branch's take-in uses the trunk's machinery,
+  per branch: its own pending revision (holding only that branch) and its own groups. `stepsVia` is open while the
+  entry's fingerprint is still in the branch's newest revision; `messageVia` while a pending entry names the merge or
+  a take-in of that commit runs.