Answer A-76: the reservation's fingerprint, the registry seat, the fault's class

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:04:18 +01:00
parent 8e87bdc148
commit e9c927d448
1 changed files with 4 additions and 0 deletions
@@ -287,3 +287,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  already shows a delivery: its `DeliveryLine` gains `pipelines`, one row per module with its steps, `no run` where the
  runner's list answers none. A runner verb's old callers list does not refuse a module: from G no verb names its
  callers (§610), so the class's default holds.
+- **A-76** (§588, §568, A-73; principle 7) A reservation keeps the fingerprint of the catalog entry it was made from
+  (`versions.Source` gains it), so publish again reads that entry; the registry seat for an artifact is found from its
+  package ecosystem as the builder's seat hearing already maps it. A transport fault's class (`no responders`, `name
+  lookup`, `connection`, `deadline`) is the one the existing retake reads from the call's error (ADR 0664, ADR 0668).