Answer A-282 and A-283: a step bound is created once; a template state's max-mib reaches its bucket
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
This commit is contained in:
@@ -389,3 +389,9 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
later start that finds it runs no switch, so the deliveries §716 writes never become records at a start. A revert's
|
||||
restore brings back the state from before G without the key, so delivering G again switches again, still safe to run
|
||||
twice by the record's key.
|
||||
- **A-282** (A-115, §544; principles 3 and 7) An ask's step bound key is created once: `stepBounds.Arm` creates it
|
||||
only if absent, and a second waiter that finds it already there takes it as armed and waits on the same key; it is
|
||||
never deleted to be made again.
|
||||
- **A-283** (A-277, ADR 0595; principle 7) The holder of the seat `mesh-broker` makes a template `state` bucket with
|
||||
the `max-mib` its requirement declares, the default cap where none is declared, as the grants part does for a
|
||||
state section; one cap rule for every state bucket.
|
||||
|
||||
Reference in New Issue
Block a user