pub async fn round_trip_preserves_the_whole_log<F: SyncFixture>(
open: impl AsyncFn() -> F,
) -> Result<RuleOutcome, Violation>Expand description
SY-28, and SY-27 beneath it: a round trip preserves the whole log. Once
the two sides have pushed and pulled to quiescence, each holds the same
set of EventIds, each event with byte-identical type, tags, data and
metadata, and the recorded time it was pushed with (VT-9).
The rule plays one side (SY-8). It pushes a log spread over both axes
a filter on Query’s surface cuts along, types and tags — two origins,
three event types, two regions, a confidential pricing slice in a
two-event group, an untagged event and one with metadata — pulls from
the start until the peer hands back an empty batch, and holds what came
back to what went: every identity, every byte. It compares no position
(SY-19): an identity is the origin’s, compared whole, and the origin
positions leave gaps, as a conformant origin may.
§Rejects
A peer that replicates a slice: one that withholds from its
counterpart the events a type or tag filter matches, among the types
and tags the rule’s own log carries — the scoped hub or filtered spoke
ADR-0027 kept off the 1.0 port. It stores and acknowledges every
push truthfully, so no other rule sees it. tests/wrong_scopes.rs
carries it with three filters, by tag, by type, and by type and tag.
§Does not reject
An identity the rule never pushed: on a far side that holds more, the rule’s side would hold it too once it had pulled, and the two sets would still agree. Nor a peer that hands an event back twice, byte-identical: redelivery is SY-11’s, and the model family judges it. Nor a filter that matches none of the rule’s events, such as one on a tag its log never carries: the rule sees only what it pushed.
§Errors
A Violation of SY-28 if the peer refuses the push or a pull, keeps
handing back groups past the suite’s pull bound, withholds a pushed
event, hands one back changed, or hands one identity back as two
different events.