- having a token owner override the engine of their token . Token-specific engines cant write to collection-associated storage, but can write to token storage and power all views.
- Lets a user modify a token minted on a collection running a marketplace engine to further customize their work
- Let's membership-like NFT collections get "forked" by the user base : users can opt-in to install a new engine of their own as a way of forking community functionality, can always opt-back in to the original collection
i think this is likely the way to go and is one half of the "fork everything" vibe
the other half is a bit more technically complex, but it would be migrating a token to a different collection.
both mechanics allow for interesting soft and hard forking, portable state across forks, and other p compelling vibes. all abstract atm