Answer A-361 and A-362: call words obey the cycle rule; the start seat list holds mesh-delivery
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
This commit is contained in:
@@ -741,3 +741,8 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
- **A-360** (completes A-354; principles 1 and 3) "Its current form" is the first view and its changes: the indexer
|
||||
also says each change of `modules` on its views family (`mesh-delivery-indexer.views.modules`, in its `emits`) when a
|
||||
new trunk revision changes it, so grants hears a newly merged module without asking again.
|
||||
- **A-361** (clarifies A-357, ADR 0614 §3; principle 7) "Exactly as from `invokes`" includes the cycle rule: a package's
|
||||
seat call words count among the invokes of every module built against it when the graph leaves out the edges that lie
|
||||
on a cycle, so a call word's edge on a cycle is left out like an invoked verb's.
|
||||
- **A-362** (completes A-353; principles 3 and 7) The seat list a runner starts with (mesh-sdk's bootstrapped list)
|
||||
holds `mesh-delivery` beside `mesh-catalog`, so `mesh-delivery.source` is admitted before the seat list is read.
|
||||
|
||||
Reference in New Issue
Block a user