[Question] Is memberlist correct for my usage

I'm currently looking for a consensus protocol to fit the following use case:

3 nodes make up a cluster.
Each node owns several resources identified in a hash map that would like similar to:
```
node1 {
'asset1',
'asset2',
'asset3'
},
node 2{ ... }
```

If node 1 owns assets 1-3 it gossips that information with node 2 and they both know who owns what. Each node is responsible for their own hash map state and each node learn's about the other's via gossip.

What I need to also happen is the ability for 'asset1' to be removed from node 1. I think this is not possible with a RAFT since the log is immutable.

This issue does not name a file, test, or entry point; begin by reading memberlist's gossip and state-management documentation and comparing the described per-node asset ownership model with Raft. Done would be a maintainer-confirmed answer about whether memberlist supports this usage, or a clearly scoped implementation request if it does not.

Written by the indexing model from the issue text.