Group Property From One Member

What goes wrong

A property of a whole group — 'all loaded', a 'from' price, 'all read' — is computed from a single member's state instead of from all of them. The other members' state is hidden or contradicted.

Example

A screen fires three requests but the loading flag comes only from the first; the spinner disappears while two lists are still empty.

Not to be confused with

All members are current — not a mix of observations from different times (Mixed Snapshot Result) and not a stale cache.

Discovered by

@sks24git GitHub

Field notes · 8

@sks24git2026-11-04

When two copies of a result merge, the higher-ranked copy wins, and a flag only the other copy carried is dropped. If the flag decides whether the run counts, a lower copy can flip the outcome.

When merging duplicates, OR their deciding flags. Ranking and authority are separate fields.
Test the merge where the weaker copy holds the flag. That case breaks.

@sks24git2026-11-04beat 1 review round

A progress page folds several parallel workers into one stage, but decides that stage only from the workers still running. When the one that already finished drops out, the page steps back from reviewing to preparing.

Derive progress from all that happened, not only what runs now. A finished worker still moved the job.
Drop workers that died at start from the summary. Their stamps tick steps nobody does.

@sks24git2026-11-04

A progress line that once named which worker it described lost its label, but the server still picked whichever worker had a record. The line now jumps backwards and says a part stopped while the whole is still running.

Hide a detail by merging, not by unlabeling. An unlabeled per-part value still moves like a part.
Ship a payload change with old readers in mind. An open page parses it with old code.

@sks24git2026-11-04beat 4 review rounds

A "ready" signal from one service let a wait be skipped before calling a second service, after one good probe there. The first real call can still land on a replica of the second that refuses it.

Trust a readiness signal only for the system that sent it. Another system has its own replicas.
One good probe proves one replica. Not the pool behind the load balancer.

@sks24git2026-10-29beat 3 review rounds

A price was picked from the first job of a pair, but the pair's result came from the second job, which had run a cheaper kind of check. The customer paid the expensive rate for the cheap result.

Price the result of record, not the job that started it. A retry or a fallback can change what was delivered.

@sks24git2026-10-09beat 1 review round

A cost check looked at only the first of two paired measurements, so a pair with one half still pending passed as settled. The report then showed a finished total with no mark that part of it was missing.

Check every half of a pair. A guard on one side reads the unfinished side as zero.
Reuse the rule that already counts it. A second copy drifts from the first.

@sks24git2026-09-12beat 3 review rounds

A page had two clocks for "finished": one worker's own end, and the pair's. A section lit by the pair sat beside a headline, a pulse and a timeline read from one row, all three saying the job was over.

Name the source of every sentence on a screen. Two sources make two truths that cannot share a page.
Draw the state table before the first line. Otherwise review returns one cell per round.

@sks24git2026-09-12beat 2 review rounds

One page described two workers from data gathered for one: the end came from the first worker's row and was applied to both. The second worker stops, and the page narrates it in the present tense.

One slot, one source of truth. Every question about a thing is answered from that thing's own record.
Fix the invariant, not the cell. Patch one state and review hands you its neighbours.