From fc71db68eff7f4dc90b939a792bfc1202e3a8263 Mon Sep 17 00:00:00 2001 From: pingqiu Date: Sat, 2 May 2026 18:46:53 -0700 Subject: [PATCH] docs(p15): record G9A RF3 ACK semantics --- sw-block/design/v3-phase-15-g9a-ack-reintegration-mini-plan.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/sw-block/design/v3-phase-15-g9a-ack-reintegration-mini-plan.md b/sw-block/design/v3-phase-15-g9a-ack-reintegration-mini-plan.md index 4f71b18ab..916ffcb96 100644 --- a/sw-block/design/v3-phase-15-g9a-ack-reintegration-mini-plan.md +++ b/sw-block/design/v3-phase-15-g9a-ack-reintegration-mini-plan.md @@ -60,6 +60,7 @@ Rule: recovery progress is not a substitute for synchronous ACK eligibility. | `da8a321` | authority reintegration oracle: returned/high-evidence replica with `ReadyForPrimary=false` is skipped as failover target until a progress-ready fact exists. | | `6d4a0e7` | `/status` maps engine `ModeRecovering` to `ReplicationRole=recovering`, distinct from `not_ready` and `replica_ready` (not yet emitted). | | `f1117ce` | component oracle: best-effort foreground writes succeed while replica is down, then production probe/recovery path catches the lagging replica back up to byte-equal. | +| `cfffc7d` | RF>2 ACK oracle: `sync-quorum` RF=3 tolerates one recovering peer but fails when both secondaries are recovering. | ### 3.2 Forward-carry tests @@ -127,6 +128,7 @@ Last verified by sw on 2026-05-02: green. | `da8a321` | authority returned-replica progress-ready oracle | | `6d4a0e7` | status `recovering` role | | `f1117ce` | component best-effort still recovers lagging peer | +| `cfffc7d` | RF=3 sync-quorum compatibility | ### 6.4 Forward-carry register