Errata
Things we got wrong. Reported by you, fixed in public.

Corrections, in public

Arqly teaches distributed systems through animated scenes and a simulator, and both make claims about how real systems behave. Some of those claims are wrong. This page is where they get corrected, with the original report and what we did about it, so a learner can see what changed rather than find a page that quietly reads differently than it did last month.

Every scene has a flag icon in its header. Use it whenever you spot a factual error, a misleading diagram, a typo, or a citation we missed — including one you are only fairly sure about. Reports land in a queue; the ones we accept are published here with a status of acknowledged, fixed, or won't fix, and the reasoning in each case. We'd rather be right than look right.

Scenes cite their primary sources — the paper, RFC, design doc or talk the load-bearing claim rests on — so a disagreement can be settled against the source rather than against us. Where the simulator is the thing making the claim, what it models and what it does not is written down separately.

What counts as an error

  • A factual claim that is wrong, or that is only true of one version, one configuration or one vendor and is stated as general.
  • A diagram that implies an ordering, a boundary or a failure mode the real system does not have.
  • A predict question whose "correct" answer is defensible only under an assumption the scene never states.
  • A missing citation — a load-bearing claim with no source you could go and check.
  • A simulator number that does not match what the engine actually computes for that diagram.
No corrections published yet.

First learner to spot something wrong gets credited here.