Partition behavior and authority activities
Partition behavior and authority activities
Prediction activities
Predict whether adding a third replica removes the theorem’s constraint. It can improve fault tolerance, but a partition may still separate the parties needed to decide which ownership state is authoritative.
Also predict whether the 24 buffered records made the live dashboard current throughout the outage. They repair history later; they could not provide timely remote observations while the link was absent.
Failure review
Exercise these failures as observable scenarios rather than labels. Interrupt coordination, repeat timed-out writes, serve a stale derived value, replay delayed telemetry, and recover the service. For each run, preserve timestamps, decisions, audit evidence, and the condition that blocks release when convergence is unproven.
Split-state drill
Break the link, write on both sides, restart a node, repeat old work, change a clock, and reconnect under load. Check which reads are stale, which writes were refused, how conflicts are found, and how delayed samples are marked. Save a trace that another reviewer can replay.
Use this split-state check:
- Name each record class.
- Name its one owner.
- State what may wait.
- State what may write.
- State what must stop.
- Cut the link once.
- Write on both sides.
- Repeat one old write.
- Restart one store once.
- Join the two sides.
- Mark each stale read.
- Prove the replay order.
- Reopen when rules change.
Technical boundaries. The 24 buffered records repair history later; they do not provide timely remote observations while the link is absent. Adding a third replica may still leave a partition separating the parties needed to decide authoritative ownership state.