The tapestry protocol (of which the Grapevine is a subset) is independent of nostr, with the exception of a collection of TIPs that direct now tapestry and grapevine data (like attestations) is stored and retrieved from nostr.

So there are a variety of lists that I’d envision might go through the following progression:

1. The dev makes one list that everyone uses. Meaning that the dev decides what items belong on the list and what don’t.

2. Users are enabled to manage their own lists, meaning Alice decides what items go on her list and what don’t. Her list is stored using standard nostr primitives like NIP-51.

3. The Grapevine enables Alice to delegate management of the list to her Grapevine, meaning that the Grapevine is empowered to decide what items go on the list and what don’t. This will require the Grapevine-managed list to be written out using NIP-51 and/or whatever other nostr primitives we decide to use.

I hope I am addressing the point you’re making about nostr primitives — let me know if I’ve misunderstood! 😁