Answer A-409: a consumed seat event matches by name and filters on the seat's subject; the revision's id names its branch
This commit is contained in:
@@ -973,3 +973,11 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
alone and its durable consumer took the event once, so a restart lost it; principles 1 and 3, §369, §372) The builder
|
||||
reads at its start the last `versions-filled` the seat's stream keeps (it is kept with no age limit, §372) by a direct
|
||||
read of the last message on its subject, and takes it as heard; the event heard later sets it as before.
|
||||
- **A-409** (live 2026-11-14: the assigner's and the builder's durable consumers filter only
|
||||
`mesh.mod.mesh-catalog.event.catalog-revision`, so neither hears a catalog revision after its first view; the seat
|
||||
definition says the event `catalog-revision` with the subject `catalog-revision.<branch>`, and the grants part, finding
|
||||
no match for the consumed `mesh-catalog.catalog-revision`, fell back to a module's event without a word; principles 1
|
||||
and 3) A consumed seat event matches the seat's event of that name whatever its subject's further tokens, and its filter
|
||||
is the seat event's subject with each `<...>` token as `*` (a trailing one also as the rest); a consume naming a seat
|
||||
that says no such event is refused aloud by the grants part, never turned into a module's event. The indexer's
|
||||
`catalog-revision` duplicate id names the branch, and it is published with the bus's acknowledgement.
|
||||
|
||||
Reference in New Issue
Block a user