Answer A-15: the branch follower's not-found, as built
mesh/check being carried to b6556a4bcfac on 269d226a8d14 | from 60e99f38759b
mesh/delivery merged: source.main moved to novox/hq@269d226a8d14
mesh/check being carried to b6556a4bcfac on 269d226a8d14 | from 60e99f38759b
mesh/delivery merged: source.main moved to novox/hq@269d226a8d14
Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
This commit is contained in:
@@ -58,3 +58,6 @@ names the principle that settles it, and is cited as "design 47 G A-n".
|
||||
- **A-14** (§580; principles 7 and 8) A finding that told several findings of one kind on one id apart by a `ref` puts that
|
||||
part into its id (`<id>.<ref>`, each escaped as §73 escapes a name); a kind stays a fixed word of its bundle's list. The
|
||||
key's scope and id and the subject's scope and id are set equal, as before.
|
||||
- **A-15** (§614; principle 3) In the branch follower an `entry` the holder refuses is `not-found`; a transport error leaves
|
||||
it `asked` and is asked again; each part writes `entry-not-found` from the follower's changes. As built in mesh-delivery
|
||||
ab616fa6.
|
||||
|
||||
Reference in New Issue
Block a user