Design 47 H2: H-A-436, the settle bound is a key with a TTL
This commit is contained in:
@@ -553,3 +553,9 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
|
||||
consumer's info on the bus (the probe is the read; the builder keeps no timer and polls nothing); the mesh's health
|
||||
probe raises the condition, so no finding of the builder's own. Every module declares how its health is checked
|
||||
(ADR 0240); tools-are-how-a-module-is-spoken-to; P-NATS-native.
|
||||
- **H-A-436 (the settle bound is a key with a TTL, its expiry heard, 01:38)** H-A-424 (1), I4. The indexer holds no timer
|
||||
(ADR 0437 §8), so the reserved-settle bound is a key of the state `heard`, `settling.<revision>`, written with the
|
||||
key-ttl reserved-settle when the first version-reserved of a revision arrives, and its expiry is heard through the
|
||||
indexer's watch of `heard` (the bus's expiry marker); the re-pin revision is written at that expiry or at the first
|
||||
pipeline-started or step-ended of the pipeline, whichever comes first. A context deadline is a timer the test does not
|
||||
see and breaks the same rule. P-NATS-native.
|
||||
|
||||
Reference in New Issue
Block a user