Post-v1. Rendezvous v1 remains one active process with bounded in-memory state and one advertised mediator endpoint.
Trigger
Start this work when the 99.5% single-active objective is insufficient, planned maintenance must preserve listings, or a region needs multiple active mediator endpoints.
Outcome
Design and implement shared TTL/CAS state, deterministic attempt-to-mediator routing, fencing/ownership, failover semantics, and multi-node consistency before making any HA, active-active, or multi-region claim.
Acceptance criteria
State ownership and split-brain behavior are specified and adversarially tested.
HTTP and UDP for one attempt route to compatible authoritative state.
Failover preserves documented safety and privacy invariants.
Multi-node capacity, restart, partition, and recovery evidence is versioned.
Deployment and rollback docs make the supported topology explicit.
Parent: #1
Identified by: #23
## Classification
Post-v1. Rendezvous v1 remains one active process with bounded in-memory state and one advertised mediator endpoint.
## Trigger
Start this work when the 99.5% single-active objective is insufficient, planned maintenance must preserve listings, or a region needs multiple active mediator endpoints.
## Outcome
Design and implement shared TTL/CAS state, deterministic attempt-to-mediator routing, fencing/ownership, failover semantics, and multi-node consistency before making any HA, active-active, or multi-region claim.
## Acceptance criteria
- State ownership and split-brain behavior are specified and adversarially tested.
- HTTP and UDP for one attempt route to compatible authoritative state.
- Failover preserves documented safety and privacy invariants.
- Multi-node capacity, restart, partition, and recovery evidence is versioned.
- Deployment and rollback docs make the supported topology explicit.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Parent: #1
Identified by: #23
Classification
Post-v1. Rendezvous v1 remains one active process with bounded in-memory state and one advertised mediator endpoint.
Trigger
Start this work when the 99.5% single-active objective is insufficient, planned maintenance must preserve listings, or a region needs multiple active mediator endpoints.
Outcome
Design and implement shared TTL/CAS state, deterministic attempt-to-mediator routing, fencing/ownership, failover semantics, and multi-node consistency before making any HA, active-active, or multi-region claim.
Acceptance criteria