Why asset capture is a risk
When shared tools and resources work well, they tend to be captured.
Domains get sold.
Databases become proprietary.
Codebases are enclosed.
Creative work is locked behind platforms.
This often happens gradually and without bad intent — but the effect is the same: the people who rely on the infrastructure lose agency over it.
Common Trust for Music exists to prevent that outcome.
Why these assets are held in common
Assets are held in common so they:
- cannot be sold off for private gain
- cannot be enclosed behind paywalls or exclusivity
- cannot be quietly repurposed away from their stated purpose
Holding assets in trust ensures they remain:
- reusable by local music ecosystems
- adaptable to different contexts
- available to future participants
Stewardship replaces ownership.
Use replaces control.
Domains and digital identity
The Trust holds key domain names and related digital identifiers.
These domains:
- provide stable public entry points
- prevent fragmentation or speculative resale
- ensure continuity beyond any individual or organisation
Domains are not branding assets to be monetised.
They are public-facing infrastructure.
Data and schemas
The Trust stewards shared data that supports local music ecosystems, such as:
- artist and venue listings
- event information
- ecosystem mapping
- participation and engagement data
This data is held to:
- improve discovery
- support coordination
- strengthen local scenes
Data is not treated as a proprietary asset.
Key principles:
- contributors retain rights over their own data
- data is structured using open, documented schemas
- data can be exported in usable formats
Design and creative assets
Design work created for Trust-related projects may include:
- websites
- publications
- visual systems
- templates and layouts
These assets are held so they can:
- be reused by other local ecosystems
- be adapted to local needs
- reduce duplication of effort
Design is treated as shared infrastructure, not brand lock-in.
Code and tooling
The Trust stewards codebases that support:
- artist and event discovery
- ticketing and participation
- data management
- ecosystem tooling
Code is held to:
- enable reuse and improvement
- prevent enclosure
- allow forks where appropriate
Core principles:
- code must be auditable
- forks must be legally and technically feasible
- no one is forced to use a single implementation
Rights of contributors
Contributors are not required to surrender ownership of their work.
Accordingly:
- individuals retain rights to their own contributions
- the Trust holds only the rights needed to steward shared use
- contributors must be credited where appropriate
Contribution does not imply loss of autonomy.
Portability and exit guarantees
The Trust treats exit as a safeguard, not a threat.
Accordingly:
- participants can leave without disproportionate loss
- data can be exported
- tools can be replaced
- forks are legitimate
The Trust does not rely on lock-in to remain relevant.
It relies on continued usefulness.
In summary
Assets are held in common so that:
- infrastructure remains available
- power remains distributed
- local ecosystems retain agency
- success does not turn into capture