What this trust is (and isn’t)
Common Trust for Music exists to steward shared infrastructure in the public interest.
That means it holds and looks after assets — digital, financial, and organisational — so they can support local music ecosystems over the long term.
The Trust is not:
- a company trying to maximise profit
- a platform that owns users, audiences, or data
- a gatekeeper deciding what music “matters”
- a hierarchy issuing instructions to local scenes
It is also not a substitute for local initiative.
Local music ecosystems remain autonomous.
The Trust exists to support coordination without capture.
What “held in trust” actually means
When something is held in trust, it is not owned in the usual sense.
Assets held by Common Trust for Music:
- cannot be sold for private gain
- cannot be enclosed behind paywalls or exclusivity
- cannot be quietly repurposed away from the Trust’s stated purpose
They are held on behalf of:
- local music ecosystems
- current and future participants
- the wider public interest in cultural life
Trustees are stewards, not owners.
Their role is to protect the purpose, not exploit the assets.
Who makes decisions — and how
No single person or group has unchecked authority.
Decision-making is shared and structured to prevent capture.
In practice this means:
- Trustees are responsible for stewardship and oversight
- Day-to-day decisions are delegated where appropriate
- Material decisions must follow defined processes
Material decisions include changes that affect:
- access to systems
- use of shared data
- visibility or ranking
- financial flows
- governance rules themselves
Those affected by a decision must have a way to:
- understand it
- question it
- contest it
Silence is not treated as consent.
How changes are proposed
Change begins with a proposal.
A proposal must:
- describe what is being changed
- explain why the change is being suggested
- outline expected benefits
- acknowledge potential risks and downsides
Proposals are shared openly with those affected.
This allows:
- feedback
- alternatives
- improvement before decisions are finalised
Changes are not rushed through by default.
Speed must be justified, not assumed.
How disagreement is handled
Disagreement is expected.
The Trust treats disagreement as:
- a signal that more explanation is needed
- a reason to slow down, not push harder
- a normal part of shared stewardship
When disagreement arises:
- reasons must be stated, not implied
- trade-offs must be made visible
- minority concerns must be recorded, not ignored
Consensus is preferred where possible.
When consensus isn’t possible, decisions must still meet legitimacy thresholds.
How slowing down works when legitimacy is contested
The Trust includes a formal mechanism for slowing change when necessary.
If a defined minority of affected participants believe that:
- a change moves too fast
- impacts haven’t been properly considered
- or legitimacy is in question
they may trigger a slowdown process.
When this happens:
- irreversible changes are paused
- further justification is required
- impact analysis must be shared
- counter-proposals must be considered
This is not a veto.
It is a way to rebalance power and ensure care.
What happens if the Trust stops serving its purpose
The Trust exists to serve local music ecosystems — not itself.
If the Trust:
- no longer supports that purpose
- begins to concentrate power
- becomes extractive or unaccountable
then continuation is not assumed.
In such cases:
- participants retain the right to leave
- forks are legitimate
- dissolution is preferable to capture
Failure must be visible and reversible, not silent.
In summary
The Trust works by:
- holding assets so they can’t be captured
- sharing power rather than concentrating it
- designing for disagreement and exit
- treating governance as infrastructure
The goal is not perfection.
It is to make abuse difficult and accountability unavoidable.