Repository navigation

Clarify confirm/replicatedConfirmation any-N semantics in the sharding docs - #723

Draft

kriszyp wants to merge 10 commits into

mainfrom

clarify-replicated-confirmation-semantics

Draft

Clarify confirm/replicatedConfirmation any-N semantics in the sharding docs#723
kriszyp wants to merge 10 commits into
mainfrom
clarify-replicated-confirmation-semantics

Commits on Oct 9, 2026
- Clarify replicatedConfirmation/confirm= any-N semantics in sharding docs
  
  kriszyp
  and
  claude
  committed
  0ee02e5
- Fix overclaims in the confirmation-semantics note per review
  
  kriszyp
  and
  claude
  committed
  ba90237
- Drop the invalidation-entry overclaim for setResidencyById / already-excluded peers
  
  kriszyp
  and
  claude
  committed
  b091967
- Qualify the replicateTo placement claim and nudge skimmers to the caveat
  
  kriszyp
  and
  claude
  committed
  1240f84
- Drop the v4 "distinct" claim and cover count-form X-Replicate-To too
  
  kriszyp
  and
  claude
  committed
  a6b0e76
- Consolidate the confirmation caveat into one place per doc, add failure modes
  
  kriszyp
  and
  claude
  committed
  797130b
- Version-badge the v5 dedup claim, fix post-commit framing and v4 off-by-one
  
  kriszyp
  and
  claude
  committed
  1634a26
- Fix VersionBadge rendering, dangling cross-reference, and delete case
  
  kriszyp
  and
  claude
  committed
  ea41406
- Note the integer requirement, the Pro-only gate, the v4 ack race, and term drift
  
  kriszyp
  and
  claude
  committed
  e5d35c3
- Stop asserting what an invalid confirmation count does
  
  kriszyp
  and
  claude
  committed
  6d513c8