Some Lubinik ideas exist as pressure tests before they exist as code.
The music addon is one of those. A musician or band site has familiar generic needs: pages, biography, homepage sections, contact, blog, maybe a few custom sections. The parent theme can already handle a lot of that.
But the music-specific layer is different. Releases, tracks, demos, live dates, videos, members, press items, and downloadable assets all have their own shape. Some bands may have official releases. Others may only have rehearsal demos they still want to share. The addon should not assume that every musician has a polished discography.
That is the kind of detail that tells me an addon might be useful. The domain has its own editorial reality.
Shelter, but bigger
The multi-refuge idea is another pressure test.
The current Shelter addon is built for a shelter site. A multi-refuge version asks a different question: what if the site needs to represent several organizations, each with its own animals, forms, listings, permissions, wish lists, and contact details?
That could become an extension of Shelter, a separate Shelter Network addon, or a future version with a stronger organization entity. The point is not to decide too early. The point is to use the idea to reveal what the architecture would need.
Future ideas are useful because they make assumptions visible. They show where the core is ready, where an addon should stay focused, and where a new layer might eventually make sense.
