XIP-80: Atomic membership #135
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
codabrink
approved these changes
Jan 28, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add XIP-80 to define AtomicMembershipExtension and InstallationLimit message for per-inbox installation limits in groups
Introduce XIP-80 spec documenting an
AtomicMembershipExtensionwith flag bits for atomic behavior and installation selection, a new sync group messageInstallationLimitwithinstallation_limitandfrozen_installations, and client functionsenable_atomic,disable_atomic, andis_atomic. Include scenarios, backward compatibility note, security considerations, agent guidance, and rationale in XIPs/xip-80-atomic-membership.md.📍Where to Start
Start with the XIP definition in XIPs/xip-80-atomic-membership.md, focusing on the
AtomicMembershipExtensionandInstallationLimitsections.Macroscope summarized c6a1015.